US 6,292,844 B1Grant
Media storage device with embedded data filter for dynamically processing data during read and write operations
Issue Date:2001-09-18
•26 Claims
•5 Drawing Sheets
Abstract
A media storage device includes an embedded filter for manipulating universal clock based streams of data as they are written to or read from the media storage device. The media storage device will also manipulate streams of data which are not being written to or read from the media storage device. Preferably the embedded filter within the media storage device is an isochronous data pipe which will receive programmed instructions from an external controller and manipulate streams of data according to the programmed instructions in real time, coordinated with the universal clock. Alternatively, the isochronous data pipe includes fixed firmware for performing the appropriate manipulations. The media storage device is also preferably coupled to an IEEE 1394-1995 serial bus structure. As streams of data are received by the media storage device during a write operation, those streams of data can be manipulated into a different format by the embedded filter before they are stored on the media within the media storage device. As streams of data are being transmitted from the media storage device during a read operation, those streams of data can be manipulated into a different format by the embedded filter before they are transmitted onto the IEEE 1394-1995 serial bus structure. In both instances, the universal clock can be used to synchronize the data streams. The media storage device will also utilize the embedded filter to manipulate streams of data being transmitted between two other devices on the IEEE 1394-1995 serial bus structure.
Metadata
Assignees
- Sony Corporation
- Sony Electronics, Inc.
Inventors
- Scott Smyers
- Bruce Fairman
Application Information
Application Number:US 09/022,926
Filing Date:1998-02-12
Priority Date:1998-02-12
Art Unit:7
Classifications
IPC:
G06F 1300G06F 1314
Field of Search:
341 8937023239550044709229710 5710 22710 8
Patent Drawings (5 sheets)
Description
Field of the Invention
[0002] The present invention relates to the field of writing data to and reading data from a media storage device. More particularly, the present invention relates to the field of manipulating the data read from or written to a media storage device.
Background of the Invention
[0003] The IEEE 1394-1995 standard, “1394 Standard For A High Performance Serial Bus,” is an international standard for implementing an inexpensive high-speed serial bus architecture which supports both asynchronous and isochronous format data transfers. In addition, the IEEE 1394-1995 bus has a universal clock called the cycle timer. This clock is synchronized on all nodes. Isochronous data transfers are real-time transfers which take place based on the universal clock such that the time intervals between significant instances have the same duration at both the transmitting and receiving applications. Each packet of data transferred isochronously is transferred in its own time period. An example of an ideal application for the transfer of data isochronously would be from a video recorder to a television set. The video recorder records images and sounds and saves the data in discrete chunks or packets. The video recorder then transfers each packet, representing the image and sound recorded over a limited time period, during that time period, for display by the television set. The IEEE 1394-1995 standard bus architecture provides multiple independent channels for isochronous data transfer between applications. A six bit channel number is broadcast with the data to ensure reception by the appropriate application. This allows multiple applications to simultaneously transmit isochronous data across the bus structure. Asynchronous transfers are traditional reliable data transfer operations which take place as soon as arbitration is won and transfer a maximum amount of data from a source to a destination.
[0004] The IEEE 1394-1995 standard provides a high-speed serial bus for interconnecting digital devices thereby providing a universal I/O connection. The IEEE 1394-1995 standard defines a digital interface for the applications thereby eliminating the need for an application to convert digital data to analog data before it is transmitted across the bus. Correspondingly, a receiving application will receive digital data from the bus, not analog data, and will therefore not be required to convert analog data to digital data. The cable required by the IEEE 1394-1995 standard is very thin in size compared to other bulkier cables used to connect such devices in other connection schemes. Devices can be added and removed from an IEEE 1394-1995 bus while the bus is operational. If a device is so added or removed the bus will then automatically reconfigure itself for transmitting data between the then existing nodes. A node is considered a logical entity with a unique address on the bus structure. Each node provides in a standard address space, an identification ROM, a standardized set of control registers and in addition, its own address space.
[0005] The IEEE 1394-1995 standard defines a protocol as illustrated in FIG. 1. This protocol includes a serial bus management block 10 coupled to a transaction layer 12, a link layer 14 and a physical layer 16. The physical layer 16 provides the electrical and mechanical connection between a device and the IEEE 1394-1995 cable. The physical layer 16 also provides arbitration to ensure that all devices coupled to the IEEE 1394-1995 bus have arbitrated access to the bus as well as actual data transmission and reception. The link layer 14 provides data packet delivery service for both asynchronous and isochronous data packet transport. This supports both asynchronous data transport, using an acknowledgement protocol, and isochronous data transport, providing an un-acknowledged real-time guaranteed bandwidth protocol for just-in-time data delivery. The transaction layer 12 supports the commands necessary to complete asynchronous data transfers, including read, write and lock. The serial bus management block 10 contains an isochronous resource manager for managing isochronous data transfers. The serial bus management block 10 also provides overall configuration control of the serial bus in the form of optimizing arbitration timing, guarantee of adequate electrical power for all devices on the bus, assignment of the cycle master, assignment of isochronous channel and bandwidth resources and basic notification of errors.
[0006] A hard disk drive including an IEEE 1394-1995 serial bus interface is illustrated in FIG. 2. The hard disk drive 20 includes the IEEE 1394-1995 serial bus interface circuit 22 for interfacing to an IEEE 1394-1995 serial bus network. The interface circuit 22 is coupled to a buffer controller 24. The buffer controller 24 is coupled to a random access memory (RAM) 26 and to a read/write channel circuit 28. The read/write channel circuit 28 is coupled to the media 30 on which data is stored within the hard disk drive 20. The read/write channel circuit 28 controls the storage operations on the media 30, including reading data from the media 30 and writing data to the media 30.
[0007] During a write operation to the hard disk drive 20, a stream of data is received from a device coupled to the IEEE 1394-1995 serial bus structure by the IEEE 1394-1995 interface circuit 22. This stream of data is forwarded from the IEEE 1394-1995 interface circuit 22 to the buffer controller 24. The buffer controller 24 then stores this data temporarily in a buffer in the RAM 26. When the read/write channel circuit 28 is available, the buffer controller 24 reads the data from the RAM 26 and forwards it to the read/write channel circuit 28. The read/write channel circuit 28 then writes the data onto the media 30.
[0008] During a read operation from the hard disk drive 20, a stream of data is read from the media 30 by the read/write channel circuit 28. This stream of data is forwarded by the read/write channel circuit 28 to the buffer controller 24. The buffer controller 24 then stores this data temporarily in a buffer in the RAM 26. When the IEEE 1394-1995 serial bus interface circuit 22 is available, the buffer controller 24 reads the data from the RAM 26 and forwards it to the interface circuit 22. The IEEE 1394-1995 serial bus interface circuit 22 then formats the data according to the requirements of the IEEE 1394-1995 standard and transmits this data to the appropriate device or devices over the IEEE 1394-1995 serial bus.
[0009] A traditional hard disk drive 20, as described, records data and plays it back according to commands received from an external controller using a protocol such as the serial bus protocol (SBP). The external controller provides command data structures to the hard disk drive 20 which inform the hard disk drive 20 where on the media 30 the data is to be written, in the case of a write operation, or read from, in the case of a read operation. The function of the hard disk drive 20 during a read operation is to recreate the original, unmodified stream of data which was previously written on the media 30.
[0010] With the growing use of the IEEE 1394-1995 serial bus, personal computers are now being coupled together in IEEE 1394-1995 networks with devices which have not traditionally been coupled to personal computers. Examples of such devices are consumer electronic devices such as video cassette recorders, video camcorders, digital video disk players and compact disk players. Raw data from these consumer devices is not always directly usable by a personal computer. The typical solution to this problem is to write an application software program which will run on the personal computer and perform the necessary data manipulation to transform the data into a format which is useful to other applications being run by the personal computer.
[0011] What is needed is a filtering device which can be used to manipulate the data from a consumer device into a format required by a personal computer or other device. What is further needed is a filtering device which can also manipulate the data from a personal computer device into a format required by a consumer electronic device.
Summary of the Invention
[0012] A media storage device includes an embedded filter for manipulating universal clock based streams of data as they are written to or read from the media storage device. The media storage device will also manipulate streams of data which are not being written to or read from the media storage device. Preferably the embedded filter within the media storage device is an isochronous data pipe which will receive programmed instructions from an external controller and manipulate streams of data according to the programmed instructions in real time, coordinated with the universal clock. Alternatively, the isochronous data pipe includes fixed firmware for performing the appropriate manipulations. The media storage device is also preferably coupled to an IEEE 1394-1995 serial bus structure. As streams of data are received by the media storage device during a write operation, those streams of data can be manipulated into a different format by the embedded filter before they are stored on the media within the media storage device. As streams of data are being transmitted from the media storage device during a read operation, those streams of data can be manipulated into a different format by the embedded filter before they are transmitted onto the IEEE 1394-1995 serial bus structure. In both instances, the universal clock can be used to synchronize the data streams. The media storage device will also utilize the embedded filter to manipulate streams of data being transmitted between two other devices on the IEEE 1394-1995 serial bus structure.
Brief Description of the Drawings
[0013] FIG. 1 illustrates a protocol stack defined by the IEEE 1394-1995 standard.
[0014] FIG. 2 illustrates a block diagram of a media storage device of the prior art.
[0015] FIG. 3 illustrates a block diagram of a media storage device according to the present invention.
[0016] FIG. 4 illustrates a register file within the isochronous data pipe.
[0017] FIG. 5 illustrates a register file within the isochronous data pipe sequencer.
Detailed Description of the Preferred Embodiment
[0018] A media storage device of the present invention includes an embedded data filter for filtering data as it is either written to the media storage device or read from the media storage device. Preferably, this embedded data filter is an isochronous data pipe which is programmable and will manipulate streams of data and the universal clock into the proper format. The isochronous data pipe is preferably programmed for the appropriate manipulations by an external controller which is controlling the media storage device. Alternatively, the isochronous data pipe includes fixed firmware for performing the appropriate manipulations.
[0019] The media storage device with the embedded filter of the present invention takes advantage of the central role of the media storage device in the communication of data between consumer electronic devices and a personal computer within an IEEE 1394-1995 serial bus network. The embedded filter within the media storage device adds the ability to filter data inside the media storage device as it is being written to the media storage device or read from the media storage device. The media storage device with embedded filter can also be used to filter a stream of data, even if the data is not being written to or read from the media storage device.
[0020] Within the media storage device, the embedded filter will manipulate a stream of data into a proper format for the device to which the data is directed, under the control of the external controlling device. As an example, when storing communications from a consumer device which are to be used by a personal computer, the embedded filter within the media storage device will manipulate those communications from the received format into a proper format for the personal computer. When the communications are read by the personal computer from the media storage device, the communications will then be in the proper format for the personal computer. The personal computer will not have to perform any further manipulation of the communications in order to utilize them as necessary. If necessary, the communications can also be manipulated a second time by the embedded filter when they are read from the media storage device by the personal computer. In the same manner, communications from the personal computer to a consumer device can be manipulated into the proper format for the consumer device by the embedded filter.
[0021] A media storage device according to the present invention is illustrated in FIG. 3. The media storage device 44 includes an IEEE 1394-1995 serial bus interface circuit 32 for sending communications to and receiving communications from other devices coupled to the IEEE 1394-1995 serial bus network. The interface circuit 32 is coupled to an embedded filter 42. Preferably, the embedded filter 42 is an isochronous data pipe. The embedded filter 42 is coupled to a buffer controller 34. The buffer controller 34 is also coupled to a RAM 36 and to a read/write channel circuit 38. The read/write channel circuit 38 is coupled to media 40 on which data is stored within the media storage device 44. The read/write channel circuit 38 controls the storage operations on the media 40, including reading data from the media 40 and writing data to the media 40. An external controller 46 is coupled to the embedded filter 42 for controlling the manipulation of data streams and to the buffer controller 34 for controlling read and write operations to the media 40.
[0022] During a write operation to the media storage device 44, the IEEE 1394-1995 serial bus interface circuit 32 receives a stream of data from the IEEE 1394-1995 serial bus. The interface circuit 32 then forwards this data to the embedded filter 42. The embedded filter 42 modifies the data, byte by byte, as specified by the programmed instructions from the external controller 46, and forwards the modified data to the buffer controller 34. The buffer controller 34 then stores this modified data temporarily in a buffer in the RAM 36. When the read/write channel circuit 38 is available, the buffer controller 34 reads the data from the RAM 36 and forwards it to the read/write channel circuit 38. The read/write channel circuit 38 then writes the data onto the media 40. Because the embedded filter 42 is programmable, the data can be manipulated during a write operation, during a read operation or during both write and read operations.
[0023] During a read operation from the media storage device 44, a stream of data is read from the media 40 by the read/write channel circuit 38. This stream of data is forwarded by the read/write channel circuit 38 to the buffer controller 34. The buffer controller 34 then stores this data temporarily in a circular buffer in the RAM 36. When the IEEE 1394-1995 serial bus interface circuit 32 is available, the buffer controller 34 reads the data from the RAM 36 and forwards it to the embedded filter 42. If the embedded filter 42 is programmed to manipulate the data stream during a read operation, this manipulation is performed and the data is forwarded to the IEEE 1394-1995 serial bus interface circuit 32. The IEEE 1394-1995 serial bus interface circuit 32 then formats the data according to the requirements of the IEEE 1394-1995 standard and transmits this data to the appropriate device or devices over the IEEE 1394-1995 serial bus.
[0024] The embedded filter 42 within the media storage device 44 of the present invention can be used to manipulate a stream of data being written to or read from the media 40. The embedded filter 42 can also be used to manipulate a stream of data being transmitted between two devices on the IEEE 1394-1995 serial bus which is not being written to or read from the media 40. During such an operation, the stream of data is received by the interface circuit 32 and forwarded to the embedded filter 42. The embedded filter 42 then manipulates this data according to a preprogrammed function and forwards the data to the buffer controller 34. The buffer controller 34 then temporarily stores the data within a circular buffer within the RAM 36. The buffer controller 34 then reads this data from the RAM 36 and forwards it to the embedded filter 42. If the embedded filter 42 is also programmed to manipulate the data stream before it is retransmitted, then this manipulation is performed and the data is forwarded to the IEEE 1394-1995 serial bus interface circuit 32. The interface circuit 32 then retransmits the manipulated data onto the IEEE 1394-1995 serial bus structure.
[0025] The embedded filter 42 is preferably programmed by the external controller 46 to manipulate streams of data received by or to be transmitted by the media storage device 44. Alternatively, the embedded filter 42 includes fixed firmware for performing the appropriate manipulations. The embedded filter 42 can be programmed to manipulate streams of data on the way into the media storage device and on the way out of the media storage device. As an example of the utilization of the embedded filter 42 within an IEEE 1394-1995 serial bus network, streams of data being written to the media storage device from any device on the network can all be formatted into a first format when they are stored on the media 40. Then when data is read from the media 40 for transmission to a particular device, that data can be manipulated by the embedded filter 42 into an appropriate format for the particular device. Additionally, the embedded filter 42 can be used in special cases to manipulate streams of data from a first device to a second device on the IEEE 1394-1995 serial bus structure.
[0026] As described above, the embedded filter 42 is preferably an isochronous data pipe. A preferred embodiment of the isochronous data pipe 42 is taught in U.S. patent application Ser. No. 08/612,322, filed on Mar. 7, 1996 and entitled “ISOCHRONOUS DATA PIPE FOR MANAGING AND MANIPULATING A HIGH-SPEED STREAM OF ISOCHRONOUS DATA FLOWING BETWEEN AN APPLICATION AND A BUS STRUCTURE,” which is hereby incorporated by reference. The isochronous data pipe 42 is programmable and will execute a series of instructions on a stream of data in order to perform manipulations on the data as required to place the data in the appropriate format. The isochronous data pipe 42 can be programmed to manipulate both asynchronous and isochronous data.
[0027] For each quadlet of data transferred, the isochronous data pipe 42 executes a predetermined number of instructions to manipulate the data as necessary from the received format into the receiving format. When converting data, the isochronous data pipe 42 operates on each quadlet of data independently. The isochronous data pipe 42 performs a programmable number of instructions on each quadlet in order to manipulate the data, as necessary. The isochronous data pipe 42 also includes an independent, dedicated register file 48.
[0028] The isochronous data pipe 42 is controlled by an independent, dedicated register file, as illustrated in FIG. 4. This register file is programmed by the external controller 46 and used to manipulate the data flowing through the isochronous data pipe 42, as necessary. The register file 180 preferably includes 120 bytes of data, numbered hexadecimally 0 through 77. In FIG. 4, the register file 180 is illustrated in a table format with 30 horizontal rows, each including four bytes of data. An offset column 182 is included in FIG. 4, to show the offset of the beginning byte in each row from the address of the beginning of the register file 180. A read/write column 184 is also included to show whether the fields in each row can be either read from and written to or read from only.
[0029] The cycle time field cycle_time is a twenty bit field within bytes 0-2 of the register file 180. The cycle time field can be read from and written to. When the control event field, which will be discussed below, contains the cycle number value, the cycle time field holds the cycle time on which the channel mask field will be loaded from the pending channel mask field as described below.
[0030] The control field is a thirty-two bit field within bytes 4-7 of the register file 180. The control field can be read from and written to. The control field includes an event field, an output enable field, a stop on error field, a transmit enable field and a go field. The event field is a four bit field in bits 28-31 of the control register. The value in the event field defines the bus event for the isochronous data pipe 42 to use as a trigger. When this bus event occurs, the isochronous data pipe 42 transfers the value stored in the pending channel mask register pending_ch_mask to the current channel mask register ch_mask. The event field is encoded for the possible bus events as illustrated in Table I below.
[0031] Therefore, when a value equal to 0 is written to the event field by an external controller the isochronous data pipe will then immediately transfer the value in the channels pending register to the channel mask register. When the event field holds a value equal to 1, the isochronous data pipe transfers the value in the channels pending register to the channel mask register on the programmed cycle time, as described above.
[0032] The output enable field is a four bit field in bits 4-7 of the control field. When any of the bits in the output enable field are set to a logical high value, then the corresponding DMA channel will assure that the appropriate path is kept full.
[0033] The stop on error field is a one bit field in bit 3 of the control field. When the stop on error bit is set to a logical high value, the isochronous data pipe 42 will stop the current operation on the first error encountered by setting the value in the channel mask register to a logical low value. Possible errors when sending data include a data underrun or a missing cycle start packet. Possible errors when receiving data include a data overrun, a missing cycle start packet, a data CRC error, an error in packet format or a channel missing error.
[0034] The transmit enable field is a one bit field in bit 1 of the control field. When the transmit enable bit is set to a logical high value, the isochronous data pipe 42 will begin executing the output control store program. When the go bit is at a logical low value or the output control store program executes a return instruction, the transmit enable bit will be cleared.
[0035] The go field is a one bit field in bit 0 of the control field. The application sets the go bit to a logical high value to enable the isochronous data pipe to watch for an event. When the specified event condition is satisfied, the isochronous data pipe 42 transfers the contents of the pending channel mask register to the current channel mask register.
[0036] The status field is a thirty-two bit field within bytes 8-B of the register file 180. The status field can be read from and written to. The status field contains status information which reports the current state of the isochronous data pipe 42. The bits 0-7 of the status field correspond to the bits 0-7 of the control field and include an output field, a stop on error field, a transmit enable field and an active field. The value of these fields in the status register indicate the current operational state of the isochronous data pipe 42. The bits 8-27 of the status field are reserved. Within the status field, the active field is a one bit field in bit 0 of the status field, which indicates whether or not the isochronous data pipe is active. Preferably, if the active bit is equal to a logical high value, the isochronous data pipe is currently active and transferring data. If the active bit is equal to a logical low value, the isochronous data pipe is not currently active. The error field is a four bit field in bits 28-31 of the status field. When the isochronous data pipe 42 halts operation due to an error, the error field contains a value indicating the error condition. The error field is only valid when the active bit is equal to a logical low value. The possible values for the error field and the errors to which they correspond are listed in Table II below.
[0037] The pending channel mask high field pending_ch_mask_hi is a four byte field within bytes 20-23 of the register file 180. The pending channel mask low field pending_ch_mask_lo is a four byte field within bytes 24-27 of the register file 180. Together, the two pending channel mask fields pending_ch_mask_hi and pending_ch_mask_lo form an eight byte field containing the mask of isochronous channel numbers for the isochronous data pipe 42 to receive. The isochronous data pipe 42 transfers the contents of this field to the channel mask register when the programmed trigger event occurs. The bit assignment of the pending channel mask field is the same as the bit assignment of the channels available register defined in chapter eight of the IEEE 1394-1995 standard.
[0038] The current channel mask high field ch_mask_hi is a four byte field within bytes 28-2B of the register file 180. The current channel mask low field ch_mask_lo is a four byte field within bytes 2C-2F of the register file 180. Together, the two current channel mask fields ch_mask_hi and ch_mask_lo form an eight byte field containing the channel mask currently in operation, with each bit within the current channel mask fields representing an isochronous channel. The channel mask field is only loaded from the pending channel mask field when a trigger event occurs. The isochronous data pipe 42 ignores received isochronous channel numbers for which the corresponding bit in the current channel mask field is set to a logical low value.
[0039] The control store output field CS_output is a one byte field within byte 34 of the register file 180. The control store output field CS_output contains the control store address within the control store memory, to which the isochronous data pipe 42 dispatches when transmitting is enabled. The control store memory contains instructions used by the isochronous data pipe in performing its operations on a stream of data.
[0040] The control store cycle start address field CS_addr_CS is a one byte field within byte 37 of the register file 180. The control store address field CS_addr_CS contains the control store address to which the isochronous data pipe branches when the cycle start packet is received. The first quadlet available to the control store program is the first quadlet of the cycle start packet. The control store address fields CS_addr—0 through CS_addr—63 are each one byte fields within bytes 38 through 77 of the register file 180. These fields contain the control store address store where the isochronous data pipe is to branch upon receiving data on the isochronous channel matching the byte number of the control store address field. For example, the control store address field CS_addr—10 contains the address in the control store where the isochronous data pipe is to branch upon receiving data on the isochronous channel number 10. The isochronous data pipe ignores all isochronous channels for which the corresponding value in the control store address field is equal to FFh. After dispatching to a control store address specified within either the control store cycle start address field CS_addr_CS or one of the control store address fields CS_addr—0 through CS_addr—63, the isochronous data pipe executes from that control store address until it encounters a return instruction. When the isochronous data pipe encounters a return instruction, the isochronous data pipe either returns to the idle state if transmitting was not previously enabled, or it returns to the location in the transmit control store program where it was prior to the dispatch.
[0041] There are sixty-four potential isochronous channels 0-63. The control store address fields CS_addr—0 through CS_addr—63 each correspond to an isochronous channel and contain the address in the control store memory where the instructions for that isochronous channel begin. Accordingly, when the isochronous data pipe 42 receives data on a particular isochronous channel, the isochronous data pipe 42 branches to the address contained in the corresponding control store address field to obtain the instructions for manipulating the data for that channel. Isochronous channels for which the corresponding value in the control store address field is equal to FFh are ignored, as are channels corresponding to bits in the current channel mask register which are equal to zero.
[0042] A stream of isochronous data is made up of one or more isochronous channels. The isochronous data pipe 42 receives isochronous channels for which the corresponding bit in the current channel mask field is set to a logical high value. The isochronous data pipe 42 transmits isochronous data according to the control store program beginning at the control store address pointed to by the value in the control store output CS_output register.
[0043] The isochronous data pipe 42 is actually a programmable sequencer which can be programmed to perform operations on the received stream of data. The isochronous data pipe sequencer contains a register file as illustrated in FIG. 5. Within the register file 190, the immediate value register IMM is a thirty-four bit register with a register code of “0” which can only be a source register. The immediate value register IMM specifies that the thirty-four bit immediate field of the instruction contains the source data for the given operation.
[0044] The bus input register BUS_IN is a thirty-two bit register with a register code of “1” which can only be a source register. Accessing the bus input register BUS_IN as a source of an operation clocks one quadlet of data through the isochronous data pipe 42. Subsequent accesses to the bus input register BUS_IN access subsequent quadlets of data in the input data stream.
[0045] The bus output register BUS_OUT is a thirty-four bit register with a register code of “2” which can only be a destination register. Accessing the bus output register BUS_OUT as a destination of an operation clocks one quadlet of data through the isochronous data pipe 42. Subsequent accesses to the bus output register BUS_OUT clock subsequent quadlets of data in the output data stream.
[0046] The data registers D0-D7 are each thirty-four bit registers with a register code of “4”, “5”, “6”, “7”, “8”, “9”, “A” and “B”, respectively, which can be either a source or destination register. The data registers D0-D7 can be used as the source or destination register for any operation.
[0047] The data interface registers DATA—0-DATA—3 are each thirty-two bit registers with a register code of “10”, “11”, “12” and “13”, respectively, which can be either a source or destination register. Each of the data interface registers DATA—0-DATA—3 access a different DMA channel. Use of these registers is to be consistent with the programming of the output enable field DMA_out_en.
[0048] The isochronous data pipe 42 implements a stack made up of a linear list of eight one byte registers. The stack registers are only accessed during a branch to subroutine instruction and a return instruction. In the preferred embodiment of the present invention, the stack registers S0-S7, each have a respective register address 0-7. Alternatively, the actual number of stack registers will vary depending on the specific implementation. When the control store program is loaded, the stack pointer is automatically initialized to a value of zero, thereby pointing to the corresponding stack register S0.
[0049] When the isochronous data pipe 42 branches to a subroutine, the isochronous data pipe 42 stores the address of the next control store instruction into the current stack register, increments the value of the stack pointer, then branches to the control store instruction contained in the low order byte of the source field. When the isochronous data pipe 42 executes a return instruction, it decrements the stack pointer, then branches to the control store instruction contained in the current stack register. If the stack pointer is decremented when it contains a value equal to zero, the value of the stack pointer will remain at zero and the isochronous data pipe 42 will halt operation until it receives an isochronous data packet or cycle start packet. When the isochronous data pipe is executing an output control store program and a cycle start packet or enabled isochronous channel is received, the isochronous data pipe 42 will interrupt execution of the output control store program, save the address of the current instruction in the stack, decrement the stack pointer and then dispatch to the proper location to handle the received packet.
[0050] Each isochronous control store instruction includes an OpCode field, a source field, a destination field, an immediate value field, an immediate field and a reserved field. The OpCode field is a six bit field which describes an operation to perform. The source field src is a four bit field which specifies a register or immediate value which contains the source value for the specified operation. The destination field dest is a four bit field which specifies a destination register for the specified operation. The immediate value field imm_val is a one bit field which when set to a logical high value, specifies that one of the operands is contained in the immediate field. The immediate field imm is a thirty-four bit field which specifies an immediate value to use for an operation if the immediate value field imm_val is set to a logical high value. In the preferred embodiment of the present invention, the reserved field includes thirteen bits which are reserved for use in alternate embodiments of the isochronous data pipe 20.
[0051] The operation codes which are implemented by the preferred embodiment of the isochronous data pipe sequencer during manipulation of a data stream and can be included in the OpCode field are listed in Table III below. The isochronous data pipe 42 will store the results for any of these operations into any register which is capable of being a destination, as illustrated in FIG. 5, including the data registers D0-D7 and any DMA channel which is configured as a destination.
[0052] For most of the operations listed in Table III, there are included two mnemonic instructions. The mnemonic instruction which includes an “I” specifies the operation is to be conducted using the immediate value. The mnemonic instruction which does not include an “I” specifies the operation is to be conducted between the values in the source and destination registers.
[0053] When a MOVE operation is performed, the value in the register specified in the source field src is moved to the register specified in the destination field dest. If the register specified in the source field src is a thirty-four bit register and the register specified in the destination field dest is a thirty-two bit register, the high order two bits will be lost. If the register specified in the source field src is a thirty-two bit register and the register specified in the destination field dest is a thirty-four bit register, then the high order two bits will both be set to a logical low value.
[0054] When a MOVE Multiple operation is performed, a number of quadlets of data specified by a count value are moved from the register specified in the source field src to the register specified in the destination field dest. The count value is stored in the register designated in the immediate field of the instruction. Preferably, for the MOVE Multiple operation, the register specified in the source field src is one of the data interface registers DATA—0-DATA—3, which access a DMA channel, or the bus input register BUS_IN. Preferably, for this operation, the register specified in the destination field dest is one of the data interface registers DATA—0-DATA—3, which access a DMA channel, or the bus output register BUS_OUT.
[0055] During an AND operation, a logical AND operation is performed on the values in the source field src and the destination field dest and the result is stored in the register specified in the destination field dest. The ANDI form of this instruction uses the value in the immediate field instead of the value in the destination field as one of the operands and stores the result in the register specified in the destination field dest. If the register specified in the source field src is a thirty-four bit register and the register specified in the destination field dest is a thirty-two bit register, the high order two bits will be lost. If the register specified in the source field src is a thirty-two bit register and the register specified in the destination field dest is a thirty-four bit register, then the high order two bits will both be set to a logical low value. If both the registers specified in the source field src and the register specified in the destination field dest are thirty-four bit registers, then the AND operation is performed on all thirty-four bits.
[0056] During an OR operation, a logical OR operation is performed on the values in the registers specified by the source field src and the destination field dest and the result is stored in the register specified in the destination field dest. The ORI form of this instruction uses the value in the immediate field instead of the value in the destination field as one of the operands and stores the result in the register specified in the destination field dest. If the register specified in the source field src is a thirty-four bit register and the register specified in the destination field dest is a thirty-two bit register, the high order two bits will be lost. If the register specified in the source field src is a thirty-two bit register and the register specified in the destination field dest is a thirty-four bit register, then the high order two bits will both be set to a logical low value. If both the register specified in the source field src and the register specified in the destination field dest are thirty-four bit registers, then the OR operation is performed on all thirty-four bits.
[0057] When a SHIFT operation is performed, the value in the destination register dest is shifted by the number of bits specified by the value in the source register src and the result is stored in the register specified in the destination field dest. A positive shift value shifts the value in the destination register to the right towards the least significant bit and zeros are used to fill in the shifted bits on the left beginning with the most significant bit. A negative shift value shifts the value in the destination register to the left towards the most significant bit and zeros are used to fill in the shifted bits on the right beginning with the least significant bit. The SHIFTI form of this instruction shifts the value in the source register by the number of bits specified in the immediate field and stores the result in the register specified in the destination field. If the register specified in the source field src is a thirty-four bit register and the register specified in the destination field dest is a thirty-two bit register, the high order two bits will be lost. If the register specified in the source field src is a thirty-two bit register and the register specified in the destination field dest is a thirty-four bit register, then the high order two bits will both be set to a logical low value. If both the register specified in the source field src and the register specified in the destination field dest are thirty-four bit registers, then the shift operation is performed on only the low order thirty-two bits.
[0058] When a CMP operation is performed, the value in the source register src is subtracted from the value in the destination register dest. If the result of the CMP operation is equal to zero, the Z bit is set to a logical high value. If the result of the CMP operation is not equal to zero, the Z bit is set to a logical low value. The results of the CMP operation are not stored anywhere. The CMPI form of this instruction subtracts the immediate value from the value in the source register src, and sets the Z bit as specified above, according to the result. This instruction also does not store the result of the operation.
[0059] When an ADD operation is performed, the value in the source register src is added to the value in the destination register dest and the result is stored in the destination register dest. The ADDI form of this instruction adds the value in the source register src to the immediate value and stores the result in the destination register dest. If the register specified in the source field src is a thirty-four bit register and the register specified in the destination field dest is a thirty-two bit register, the high order two bits will be lost. If the register specified in the source field src is a thirty-two bit register and the register specified in the destination field dest is a thirty-four bit register, then the high order two bits will both be set to a logical low value. If both the register specified in the source field src and the register specified in the destination field dest are thirty-four bit registers, then the ADD operation is performed on only the low order thirty-two bits.
[0060] When a SUB operation is performed, the value in the destination register dest is subtracted from the value in the source register src and the result is stored in the destination register dest. The SUBI form of this instruction subtracts the immediate value from the value in the source register and the result is stored in the destination register dest. If the register specified in the source field src is a thirty-four bit register and the register specified in the destination field dest is a thirty-two bit register, the high order two bits will be lost. If the register specified in the source field src is a thirty-two bit register and the register specified in the destination field dest is a thirty-four bit register, then the high order two bits will both be set to a logical low value. If both the register specified in the source field src and the register specified in the destination field dest are thirty-four bit registers, then the SUB operation is performed on only the low order thirty-two bits.
[0061] When a MULT operation is performed, the value in the source register src is multiplied by the value in the destination register dest and the result is stored in the destination register dest. The MULTI form of this instruction multiplies the immediate value by the value in the source register src and the result is stored in the destination register dest. If the register specified in the source field src is a thirty-four bit register and the register specified in the destination field dest is a thirty-two bit register, the high order two bits will be lost. If the register specified in the source field src is a thirty-two bit register and the register specified in the destination field dest is a thirty-four bit register, then the high order two bits will both be set to a logical low value. If both the register specified in the source field src and the register specified in the destination field dest are thirty-four bit registers, then the MULT operation is performed on only the low order thirty-two bits.
[0062] When a BRANCH operation is performed, the isochronous data pipe 42 branches to the control store address contained in the low order byte of the source field src. The source field src can specify a register or an immediate value.
[0063] When a BRANCH ON ZERO operation is performed, the isochronous data pipe 42 branches to the control store address contained in the low order byte of the source field src if the result of the last arithmetic or move control store instruction was equal to zero. The source field src can specify a register or an immediate value.
[0064] When a BRANCH ON NOT ZERO operation is performed, the isochronous data pipe 42 branches to the control store address contained in the low order byte of the source field src if the result of the last arithmetic or move control store instruction was not equal to zero. The source field can specify a register or an immediate value.
[0065] When a BSR operation is performed, the address of the next control store instruction is pushed onto the stack and the isochronous data pipe 42 branches to the control store address contained in the low order byte of the source field src. The source field src can specify a register or an immediate value.
[0066] When a BSR ON ZERO operation is performed, if the result of the last arithmetic or move control store instruction was equal to zero, the address of the next control store instruction is pushed onto the stack and the isochronous data pipe 42 branches to the control store address contained in the low order byte of the source field src. The source field src can specify a register or an immediate value.
[0067] When a BSR ON NOT ZERO operation is performed, if the result of the last arithmetic or move control store instruction was not equal to zero, the address of the next control store instruction is pushed onto the stack and the isochronous data pipe 42 branches to the control store address contained in the low order byte of the source field src. The source field src can specify a register or an immediate value.
[0068] When a RETURN operation is performed, the last control store address is popped off of the stack and the isochronous data pipe 42 branches to that address.
[0069] The isochronous data pipe 42 of the preferred embodiment is programmed by a device before it can transfer and manipulate data. Once programmed and initialized, the control register is used to change the operational state of the isochronous data pipe 42. The current operational state is completely defined by the value in the current channel mask register and the information contained in the low order byte of the status register.
[0070] In order to change the state of the isochronous data pipe 42, a new channel mask value is programmed into the pending channel mask register and a new operational state into the control register. In the same register access to the control register, the go bit is also set and an event is programmed into the event field. When the programmed event occurs, the isochronous data pipe 42 transfers the value in the pending channel mask register to the current channel mask register. The isochronous data pipe 42 also transfers the information in the low order byte of the control register into the low order byte of the status register.
[0071] In order to stop the operation of the isochronous data pipe 42, a value of all zeros is programmed into the pending channel mask register and a logical low value into the transmit enable bit in the control register. As with any state change, the go bit is also set and an event is programmed into the event field of the control register. When the event occurs the value in the current channel mask register becomes zero and the transmit enable bit in the status register is pulled to a logical low value, thereby stopping the operation of the isochronous data pipe 42. When the operation of the isochronous data pipe 42 is stopped, the active bit in the status register is also pulled to a logical low value.
[0072] In order to activate the isochronous data pipe 42, a control store program is loaded and the proper control store offsets are programmed into the control store address register file. The pending channel mask register is then programmed with a bit mask of the channels which the isochronous data pipe 42 is to receive. If the isochronous data pipe 42 is not receiving data, the value in the pending channel mask register is programmed to zero. The go bit in the control register is set to a logical high value to indicate a state change. The transmit enable bit in the control register is set to a logical high value if the isochronous data pipe 42 is to transmit isochronous data. The stop on error bit in the control register is set to a logical high value if the isochronous data pipe 42 is to stop operation on any error. If the isochronous data pipe 42 is transmitting isochronous data, the output enable bits in the control register which correspond to the DMA channels involved in transmitting isochronous data are set to a logical high value. The event field in the control register is programmed to an event on which the isochronous data pipe 42 is to change state.
[0073] In an alternate embodiment of the media storage device 44 of the present invention, the isochronous data pipe 42 includes hard-coded, fixed firmware for manipulating data packets. In this embodiment, the isochronous data pipe will only manipulate communications into particular preprogrammed formats. The isochronous data pipe within the preferred embodiment of the present invention can be programmed by the external controller 46 and configured for manipulating data packets into any desired format. In the preferred embodiment, the appropriate conversion code is downloaded from the external controller 46 to the isochronous data pipe 42.
[0074] While the external controller 46 is preferably coupled directly to the media storage device 44, it should also be apparent that the external controller 46 can alternatively be coupled to the media storage device 44 through the IEEE 1394-1995 serial bus network.
[0075] The embedded filter 42 is included within the media storage device 44 in order to take advantage of the fact that most streams of data will be written to and read from the media storage device 44. Accordingly, the data being written to and read from the media storage device 44 can be manipulated by the embedded filter 42 without disrupting its flow. Data which is not being written to or read from the media storage device can also be manipulated by the embedded filter 42 as it is being transmitted from one device to another device on the IEEE 1394-1995 serial bus structure. During data operations involving the media storage device 44, the data can be manipulated as it is being written to the media 40 or after it has been read from the media 40 and before it is transmitted on the IEEE 1394-1995 serial bus. The data can also be manipulated both as it is being written to and read from the media 40.
[0076] The present invention has been described in terms of specific embodiments incorporating details to facilitate the understanding of principles of construction and operation of the invention. Such reference herein to specific embodiments and details thereof is not intended to limit the scope of the claims appended hereto. It will be apparent to those skilled in the art that modifications may be made in the embodiment chosen for illustration without departing from the spirit and scope of the invention. Specifically, it will be apparent to those skilled in the art that while the preferred embodiment of the present invention is used with an IEEE 1394-1995 serial bus structure, the present invention could also be implemented on any other appropriate bus structures. Additionally, it will be apparent to those skilled in the art that the register file and/or the instruction set and their details of operation as described herein can be substantially or completely altered in a specific implementation without departing from the intended spirit or scope of the present invention.
Claims
Certificate of Correction present
The claims shown below may not include correction changes. Use the corrected PDF for authoritative text.
We claim:
1. A filtering device embedded within a media storage device configured for coupling to other devices for receiving and transmitting streams of data directed to a destination device, the filtering device comprising:
a. a control circuit configured to receive instructions from an external controller for converting streams of data from a first format to a second format corresponding to the destination device; and
b. a manipulating circuit coupled to the control circuit for manipulating received streams of data in the first format to manipulated streams of data in the second format according to the instructions within the control circuit.
2. The filtering device as claimed in claim 1 wherein the media storage device is configured for coupling to an IEEE 1394-1995 serial bus structure.
3. The filtering device as claimed in claim 2 wherein the manipulating circuit will manipulate isochronous streams of data.
4. The filtering device as claimed in claim 2 wherein the manipulating circuit will manipulate both isochronous and asynchronous streams of data.
5. The filtering device as claimed in claim 4 wherein the instructions are programmed within firmware in the control circuit.
6. The filtering device as claimed in claim 4 wherein the instructions are stored in read-only memory in the control circuit.
7. A media storage device comprising:
a. an interface circuit for receiving a stream of data, thereby forming a received stream of data, and also for transmitting a manipulated stream of data in a format corresponding to a destination device; and
b. a filtering circuit coupled to the interface circuit for manipulating the received stream of data into a predetermined format according to programmed instructions received from an external controller, thereby forming the manipulated stream of data.
8. The media storage device as claimed in claim 7 further comprising media coupled to the filtering circuit on which one of the received stream of data and the manipulated stream of data is stored.
9. The media storage device as claimed in claim 8 further comprising a read/write channel circuit coupled to the filtering circuit and to the media for controlling read and write operations from and to the media.
10. The media storage device as claimed in claim 7 wherein the filtering circuit is an isochronous data pipe comprising:
a. a control store memory, wherein the programmed instructions are stored for manipulating the received stream of data into the manipulated stream of data; and
b. a manipulating circuit coupled to the control store memory for obtaining the programmed instructions, manipulating the received stream of data into the manipulated stream of data according to the programmed instructions, and providing the manipulated stream of data.
11. The media storage device as claimed in claim 10 wherein the programmed instructions are stored within the control store memory by the external controller.
12. The media storage device as claimed in claim 7 wherein the interface circuit is coupled to an IEEE 1394-1995 serial bus structure.
13. The media storage device as claimed in claim 12 wherein the filtering circuit manipulates both isochronous and asynchronous streams of data.
14. A method of writing data to a media storage device comprising:
a. receiving a received packet of data to be written to the media storage device;
b. manipulating the received packet of data according to programmed instructions programmed by an external controller, thereby forming a manipulated packet of data, wherein the manipulated packet of data has a different form than the received packet of data; and
c. storing the manipulated packet of data onto a media within the media storage device.
15. The method as claimed in claim 14 wherein the received packet of data is received from an IEEE 1394-1995 serial bus structure.
16. The method as claimed in claim 15 wherein the step of manipulating is performed by an isochronous data pipe.
17. A method of reading data from a media storage device comprising:
a. reading a previously stored packet of data from a media within the media storage device; and
b. manipulating the previously stored packet of data according to programmed instructions programmed by an external controller thereby forming a manipulated packet of data, wherein the manipulated packet of data has a different form than the previously stored packet of data.
18. The method as claimed in claim 17 further comprising transmitting the manipulated packet of data to another device.
19. The method as claimed in claim 18 wherein transmitting includes transmitting the manipulated packet of data onto an IEEE 1394-1995 serial bus structure.
20. The filtering device as claimed in claim 1 wherein the control circuit includes a control store memory wherein the instructions are stored.
21. The filtering device as claimed in claim 20 wherein the instructions are stored at a memory address within the control store memory corresponding to a channel number for the stream of data if the stream of data is an isochronous stream of data and at a memory address corresponding to asynchronous data if the stream of data is an asynchronous stream of data.
22. The media storage device as claimed in claim 11 wherein the programmed instructions are stored at a memory address within the control store memory corresponding to a channel number for the stream of data if the stream of data is an isochronous stream of data and at a memory address corresponding to asynchronous data if the stream of data is an asynchronous stream of data.
23. The method as claimed in claim 14 further comprising determining a channel number for the received packet of data, wherein the programmed instructions are obtained from a memory address corresponding to the channel number.
24. The method as claimed in claim 14 wherein the programmed instructions are stored at a memory address corresponding to a channel number for the received packet of data if the received packet of data is an isochronous packet of data and at a memory address corresponding to asynchronous data if the received packet of data is an asynchronous packet of data.
25. The method as claimed in claim 17 further comprising determining a channel number for the previously stored packet of data, wherein the programmed instructions are obtained from a memory address corresponding to the channel number.
26. The method as claimed in claim 17 wherein the programmed instructions are stored at a memory address corresponding to a channel number for the previously stored packet of data if the previously stored packet of data is an isochronous packet of data and at a memory address corresponding to asynchronous data if the previously stored packet of data is an asynchronous packet of data.
Patent Citations (64)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4298932 | 1981-11-01 | Sams | Applicant |
| US4410983 | 1983-10-01 | Cope | Applicant |
| US4493021 | 1985-01-01 | Agrawal et al. | Applicant |
| US4972470 | 1990-11-01 | Farago | Examiner |
| US4998245 | 1991-03-01 | Tanaka et al. | Applicant |
| US5008819 | 1991-04-01 | Gorbatenko | Applicant |
| US5233683 | 1993-08-01 | Sasaki | Examiner |
| US5313617 | 1994-05-01 | Nakano et al. | Examiner |
| US5359713 | 1994-10-01 | Moran et al. | Applicant |
| US5369773 | 1994-11-01 | Hammerstrom | Applicant |
| US5432650 | 1995-07-01 | Nunomura et al. | Applicant |
| US5473362 | 1995-12-01 | Fitzgerald et al. | Applicant |
| US5506846 | 1996-04-01 | Edem et al. | Applicant |
| US5509126 | 1996-04-01 | Oprescu et al. | Applicant |
| US5535208 | 1996-07-01 | Kawakami et al. | Applicant |
| US5544324 | 1996-08-01 | Edem et al. | Applicant |
| US5548587 | 1996-08-01 | Bailey et al. | Applicant |
| US5550802 | 1996-08-01 | Worsley et al. | Applicant |
| US5559796 | 1996-09-01 | Edem et al. | Applicant |
| US5559967 | 1996-09-01 | Oprescu et al. | Applicant |
| US5586264 | 1996-12-01 | Belknap et al. | Applicant |
| US5594734 | 1997-01-01 | Worsley et al. | Applicant |
| US5602853 | 1997-02-01 | Ben-Michael et al. | Applicant |
| US5603058 | 1997-02-01 | Belknap et al. | Applicant |
| US5615382 | 1997-03-01 | Gavin et al. | Applicant |
| US5617419 | 1997-04-01 | Christensen et al. | Applicant |
| US5640392 | 1997-06-01 | Hayashi | Applicant |
| US5640592 | 1997-06-01 | Rao | Examiner |
| US5647057 | 1997-07-01 | Roden et al. | Applicant |
| US5652584 | 1997-07-01 | Yoon | Examiner |
| US5659780 | 1997-08-01 | Wu | Applicant |
| US5664124 | 1997-09-01 | Katz et al. | Applicant |
| US5671441 | 1997-09-01 | Glassen et al. | Applicant |
| US5687174 | 1997-11-01 | Edem et al. | Applicant |
| US5689678 | 1997-11-01 | Stallmo et al. | Applicant |
| US5692211 | 1997-11-01 | Gulick et al. | Applicant |
| US5699503 | 1997-12-01 | Bolosky et al. | Applicant |
| US5704052 | 1997-12-01 | Wu et al. | Applicant |
| US5761430 | 1998-06-01 | Gross et al. | Applicant |
| US5764972 | 1998-06-01 | Crouse et al. | Applicant |
| US5781599 | 1998-07-01 | Shiga | Applicant |
| US5781615 | 1998-07-01 | Bales et al. | Applicant |
| US5790886 | 1998-08-01 | Allen | Applicant |
| US5812883 | 1998-09-01 | Rao | Examiner |
| US5815678 | 1998-09-01 | Hoffman et al. | Applicant |
| US5835694 | 1998-11-01 | Hodges | Applicant |
| US5835726 | 1998-11-01 | Shwed et al. | Examiner |
| US5884103 | 1999-03-01 | Terho et al. | Examiner |
| US5887145 | 1999-03-01 | Harrari et al. | Examiner |
| US5893148 | 1999-04-01 | Genduso et al. | Applicant |
| US5928331 | 1999-07-01 | Bushmitch | Applicant |
| US5946298 | 1999-08-01 | Okuyama | Examiner |
| US5960036 | 1999-09-01 | Johnson et al. | Applicant |
| US5970236 | 1999-10-01 | Galloway et al. | Examiner |
| US5987126 | 1999-11-01 | Okuyama et al. | Applicant |
| US5991520 | 1999-11-01 | Smyers et al. | Applicant |
| US6064676 | 2000-05-01 | Slattery et al. | Applicant |
| US6085270 | 2000-07-01 | Gutlick | Applicant |
| EP428111A2 | 1991-05-01 | Applicant | |
| EP499394A1 | 1992-08-01 | Applicant | |
| EP588046A1 | 1994-03-01 | Applicant | |
| EP696853A2 | 1996-02-01 | Applicant | |
| JP5-165687 | 1993-07-01 | Applicant | |
| JP409128156 | 1997-05-01 | Examiner |
Non-Patent Literature (13)
- “The Parallel Protocol Engine” Matthias Kaiserswerth, IEEE/ACM Transactions on Networking, Dec. 1993, New York, pp. 650-663.Applicant
- “The Programmable Protocol VLSI Engine (PROVE)” A.S. Krishnakumar, W.C. Fischer, and Krishan Sabnani, IEEE Transactions on Communications, Aug. 1994, New York, pp. 2630-2642.Applicant
- “A Bus on a Diet-The Serial Bus Alternative” Michael Teener, CompCon92, Feb. 24-28, 1992, pp. 316-321.Applicant
- “Local Area Network Protocol for Autonomous Control of Attached Devices” Software Patent Institute, 1995, 1996.Applicant
- “Architecture for High Performance Transparent Bridges” Software Patent Institute, 1995, 1996.Applicant
- “Access to High-Speed LAN via Wireless Media” Software Patent Institute, 1995, 1996.Applicant
- “Asynchronous Transfer Mode” Julia L. Heeter, Dec. 12, 1995.Applicant
- “The SerialSoft IEEE 1394 Developer Tool” Skipstone.Applicant
- “Data link driver program design for the IBM token ring network PC adapter” Gee-Swee Poo and Wilson Ang, Computer Communications, 1989, London, Great Britain, pp. 266-272.Applicant
- “Fiber Channel (FCS)/ATM interworking: A design solution” A. Anzaloni, M. De Sanctis, F. Avaltroni, G. Rulli, L. Proietti and G. Lombardi, Ericsson Fatme R&D Division, Nov. 1993, pp. 1127-1133.Applicant
- “Data Exchange Adapter for Micro Channel/370” Software Patent Institute, 1995, 1996.Applicant
- American National Standards Institute X3T10 Technical Committee, Information Technology—Serial Bus Protcol (SBP-2), Project 1155D, Revision 1e, Nov. 9, 1996.Applicant
- IEEE, “1394 Standard for a High Performance Serial Bus,” 1995, USA.Applicant