Extended cardbus/PC card controller with split-bridge technology

An improved extended cardbus/PC card controller (20) incorporating proprietary Split-Bridge™ high speed serial communication technology for interconnecting a conventional parallel system bus via a high speed serial link with a remote peripheral device. The extend cardbus/PC card controller is adapted to interface the parallel system bus, which may be PCI, PCMCIA, integrated, or some other parallel I/O bus architecture, with peripheral devices via PC cards, and now optionally via a high speed serial link using the proprietary serial Split-Bridge™ technology. The serial Split-Bridge™ technology provides real time interconnection between the parallel system bus and the remote device which may also be based on a parallel system data bus architecture, over a serial link, which serial link appears to be transparent between the buses and thus facilitates high speed data transfer exceeding data rates of 1.0 GigaHertz.

Skip to: Description  ·  Claims  ·  References Cited  · Patent History  ·  Patent History
Description
CROSS REFERENCE TO RELATED APPLICATIONS

This application claims priority of provisional patent application serial No. 60/198,317 entitled Split-Bridge Systems, Applications and Methods of Use filed on Apr. 19, 2000, as well as co-pending and commonly assigned patent applications Ser. No. 09/130,057 filed Jun. 6, 1998, Ser. No. 09/130,058 filed Jun. 6, 1998, Ser. No. 08/679,131 now issued as U.S. Pat. No. 5,941,965; and co-pending patent application Ser. No. 09/559,678, entitled Modular Computer Based on Universal Connectivity Station, the teachings of each incorporated herein by reference.

FIELD OF THE INVENTION

The present invention is generally related to data processing systems, and more particularly to computer systems having at least one host processor and connectable to a plurality of peripherals devices including notebook computers, storage devices, displays, keyboards, mouse's and so forth.

BACKGROUND OF THE INVENTION

Computer systems today are powerful, but are rendered limited in adapting to changing computing environments. The PCI bus is pervasive in the industry, but as a parallel data bus is not easily bridged to other PCI based devices. Full bridges are known, such as used in traditional laptop computer/docking stations. However, separating the laptop computer from the docking station a significant distance has not been possible. Moreover, the processing power of computer systems has been resident within the traditional computer used by the user because the microprocessor had to be directly connected to and resident on the PCI motherboard. Thus, upgrading processing power usually meant significant costs and/or replacing the computer system.

PCI

The PCI bus is primarily a wide multiplexed address and data bus that provides support for everything from a single data word for every address to very long bursts of data words for a single address, with the implication being that burst data is intended for sequential addresses. Clearly the highest performance of the PCI bus comes from the bursts of data, however most PCI devices require reasonable performance for even the smallest single data word operations. Many PCI devices utilize only the single data mode for their transfers. In addition, starting with the implementation of the PCI 2.1 version of the specification, there has been at least pseudo isochronous behavior demanded from the bus placing limits on an individual device's utilization of the bus, thus virtually guaranteeing every device gets a dedicated segment of time on a very regular interval and within a relatively short time period. The fundamental reason behind such operation of the PCI bus is to enable such things as real time audio and video data streams to be mixed with other operations on the bus without introducing major conflicts or interruption of data output. Imagine spoken words being broken into small unconnected pieces and you get the picture. Prior to PCI 2.1 these artifacts could and did occur because devices could get on the bus and hold it for indefinite periods of time. Before modification of the spec for version 2.1, there really was no way to guarantee performance of devices on the bus, or to guarantee time slot intervals when devices would get on the bus. Purists may argue that PCI is still theoretically not an isochronous bus, but as in most things in PC engineering, it is close enough.

Traditional High Speed Serial

Typical high speed serial bus operation on the other hand allows the possibility of all sizes of data transfers across the bus like PCI, but it certainly favors the very long bursts of data unlike PCI. The typical operation of a serial bus includes an extensive header of information for every data transaction on the bus much like Ethernet, which requires on the order of 68 bytes of header of information for every data transaction regardless of length. In other words, every data transaction on Ethernet would have to include 68 bytes of data along with the header information just to approach 50% utilization of the bus. As it turns out Ethernet also requires some guaranteed dead time between operations to “mostly” prevent collisions from other Ethernet devices on the widely disperse bus, and that dead time further reduces the average performance.

The typical protocol for a serial bus is much the same as Ethernet with often much longer header information. Virtually all existing serial bus protocol implementations are very general and every block of data comes with everything needed to completely identify it. FiberChannel (FC) has such a robust protocol that virtually all other serial protocols can be transmitted across FC completely embedded within the FC protocol, sort of like including the complete family history along with object size, physical location within the room, room measurements, room number, street address, city, zip code, country, planet, galaxy, universe, . . . etc. and of course all the same information about the destination location as well, even if all you want to do is move the object to the other side of the same room. Small transfers across all of these protocols, while possible, are extremely expensive from a bandwidth point of view. Of course the possibility of isochronous operation on the more general serial bus is not very reasonable.

Recreating High Speed Serial for PCI

In creating the proprietary Split-Bridge™ technology, Mobility electronics of Phoenix, Ariz., the present applicant, actually had to go back to the drawing board and design a far simpler serial protocol to allow a marriage to the PCI bus, because none of the existing implementations could coexist without substantial loss of performance. For a detailed discussion of Applicant's proprietary Split-Bridge™ technology, cross reference is made to Applicant's co-pending commonly assigned patent applications identified as Ser. No. 09/130,057 and 09/130,058 both filed Jun. 6, 1998, the teachings of each incorporated herein by reference. The Split-Bridge™ technology approach is essentially custom fit for PCI and very extensible to all the other peripheral bus protocols under discussion like PCIx, and LDT™ of AMD corporation. Split-Bridge™ technology fundamentals are a natural for extending anything that exists within a computer. It basically uses a single-byte of overhead for 32 bits of data and address—actually less when you consider that byte enables, which are not really “overhead”, are included as well.

Armed with the far simpler protocol, all of the attributes of the PCI bus are preserved and made transparent across a high speed serial link at much higher effective bandwidth than any existing serial protocol. The net result is the liberation of a widely used general purpose bus, and the new found ability to separate what were previously considered fundamental inseparable parts of a computer into separate locations. When the most technical reviewers grasp the magnitude of the invention, then the wheels start to turn and the discussions that follow open up a new wealth of opportunities. It now becomes reasonable to explore some of the old fundamentals, like peer-to-peer communication between computers that has been part of the basic PCI specification from the beginning, but never really feasible because of the physical limits of the bus prior to Split-Bridge™ technology. The simplified single-byte overhead also enables very efficient high speed communication between two computers and could easily be extended beyond PCI.

The proprietary Split-Bridge™ technology is clearly not “just another high speed link” and distinguishing features that make it different represent novel approaches to solving some long troublesome system architecture issues.

First of all is the splitting of a PCI bridge into two separate and distinct pieces. Conceptually, a PCI bridge was never intended to be resident in two separate modules or chips and no mechanism existed to allow the sharing of setup information across two separate and distinct devices. A PCI bridge requires a number of programmable registers that supply information to both ports of a typical device. For the purpose of the following discussion, the two ports are defined into a north and south segment of the complete bridge.

The north segment is typically the configuration port of choice and the south side merely takes the information from the registers on the north side and operates accordingly. The problem exists when the north and south portions are physically and spatially separated and none of the register information is available to the south side because all the registers are in the north chip. A typical system solution conceived by the applicant prior to the invention of Split-Bridge™ technology would have been to merely create a separate set of registers in the south chip for configuration of that port. However, merely creating a separate set of registers in the south port would still leave the set up of those registers to the initialization code of the operating system and hence would have required a change to the system software.

Split-Bridge™ technology, on the other hand, chose to make the physical splitting of the bridge into two separate and spaced devices “transparent” to the system software (in other words, no knowledge to the system software that two devices were in fact behaving as one bridge chip). In order to make the operations transparent, all accesses to the configuration space were encoded, serialized, and “echoed” across the serial link to a second set of relevant registers in the south side. Such transparent echo between halves of a PCI bridge or any other bus bridge is an innovation that significantly enhances the operation of the technology.

Secondly, the actual protocol in the Split-Bridge™ technology is quite unique and different from the typical state of the art for serial bus operations. Typically transfers are “packetized” into block transfers of variable length. The problem as it relates to PCI is that the complete length of a given transfer must be known before a transfer can start so the proper packet header may be sent.

Earlier attempts to accomplish anything similar to Split-Bridge™ technology failed because the PCI bus does not inherently know from one transaction to the next when, or if, a transfer will end or how long a block or burst of information will take. In essence the protocol for the parallel PCI bus (and all other parallel, and or real time busses for that matter) is incompatible with existing protocols for serial buses.

An innovative solution to the problem was to invent a protocol for the serial bus that more or less mimics the protocol on the PCI. With such an invention it is now possible to substantially improve the performance and real time operation here to for not possible with any existing serial bus protocol.

The 8 bit to 10 bit encoding of the data on the bus is not new, but follows existing published works. However, the direct sending of 32 bits of information along with the 4 bits of control or byte enables, along with an additional 4 bits of extension represents a 40 bit for every 36 bits of existing PCI data, address, and control or a flat 10% overhead regardless of the transfer size or duration, and this approach is new and revolutionary. Extending the 4 bit extension to 12 or more bits and include other functionality such as error correction or retransmit functionality is also within the scope of the Split-Bridge™ technology.

New Applications of the Split-Bridge™ Technology

Basic Split-Bridge™ technology was created for the purpose of allowing a low cost, high speed universal dock solution for all laptop computers and it has accomplished that task very well. By taking advantage of the standard and pervasive nature of the PCI bus in many other applications in computing, dramatic improvements in the price performance for other machines can be realized as well. The present invention is rendered possible due to the attributes of applicant's proprietary Split-Bridge™ technology.

SUMMARY OF THE INVENTION

The present invention achieves technical advantages as an improved extended cardbus/PC card controller incorporating the proprietary serial high speed Split-Bridge™ technology providing serial communications between a parallel system bus and a remote peripheral device. The improved controller includes the conventional system frontside controls, I/O controls, a cardbus translator having PC card slots adapted to receive a PCMCIA card or cards, and one end of the split bridge serial communication link comprising the proprietary serial Split-Bridge™ technology. The controller may further include super I/O circuitry for communicating remote I/O devices with the system bus as the super I/O devices become more readily available in the market.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates prior art computer systems depicted as a traditional performance desk top computer shown at 10, and a portable computing device 12, such as a notebook or laptop computer, mechanically coupled to mechanical docking station 14;

FIG. 2 is a block diagram of a prior art bridge 16 used to couple two system computing buses, such as used between the portable computing device 12 and the mechanical docking station 14 shown in FIG. 1;

FIG. 3 illustrates the proprietary Split-Bridge™ technology serial communication technology of the applicant enabling high speed serial communications within the modular computer system of the present invention;

FIG. 4 is a diagram of a conventional cardbus/PC controller; and

FIG. 5 is a block diagram of an improved extended cardbus/PC card controller having an integrated serial Split-Bridge™ interface according to the preferred embodiment of the present invention.

 DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

Referring to FIG. 3, there is depicted the proprietary Split-Bridge™ technology serial communications technology of the present applicant, discussed in great detail in commonly assigned U.S. patent applications Ser. No. 09/130,057 filed Jun. 6, 1998, and Ser. No. 09/130,058 also filed Jun. 6, 1998 the teachings of which are incorporated herein by reference.

Applicant's Split-Bridge™ technology revolutionizes the status quo for computer systems. The Split-Bridge™ technology does not require the need for custom hardware or custom software to achieve full performance serial communication between devices, including devices having parallel data buses including the PCI bus. In fact, for each device in a modular computer system, the Split-Bridge™ technology appears just like a standard PCI bridge, and all software operating systems and device drivers already take such standard devices into consideration. By utilizing standard buses within each device operating within the modular computer system, each device does not require any additional support from the Operating System (OS) software. The modular computing system has simple elegance, allowing the PCI bus which is so pervasive in the computer industry, that possible applications of the initial PCI form of Split-Bridge™ technology are all most limitless.

Originally implemented in PCI, there is nothing fundamental that ties the Split-Bridge™ technology to PCI, and thus, the Split-Bridge™ technology can migrate as bus architectures grow and migrate. The 64 bit PCI is compatible with the Split-Bridge™ technology, as is future PCIx and/or LDT™ that are currently under consideration in the industry and which are straight forward transitions of the Split-Bridge™ technology. Implementations with other protocols or other possible and natural evolutions of the Split-Bridge™ technology.

Referring to FIG. 5, there is depicted generally at 20 an improved card/bus controller according to the preferred embodiment of the present invention. Cardbus controller 20 is seen to have conventional system front side control circuitry 22, input/output (I/O) control circuitry 24 a cardbus translator circuitry 26 adapted to couple to and communicably interface with one or more PC cards inserted into respective slots 28, and being improved to include a serial Split-Bridge™ interface generally show at 30. The serial Split-Bridge™ interface portion 30 is adapted to serially communicate data and control signals between the parallel system bus 32 via a duplex serial link 34 to a remote peripheral device (not shown) converting the parallel data to outgoing serial data and converting incoming serial data to parallel data.

The proprietary Split-Bridge™ technology, when employed in the extended cardbus/PC card controller 20, significantly expands the interconnectivity of a standard communications network by allowing devices accessing the parallel systems bus 32 to communicate with a variety of external devices via PC cards, an extended cardbus, or advantageously via a serial link when employing the high speed serial Split-Bridge™ technology according to the present invention.

All of the electronics comprising the controller 20 can be embodied in discrete circuitry, in an application specific integrated circuit (ASIC), or combination thereof, to provide the multi-function interface capability between the parallel system bus 32 and remote peripheral devices. By employing a serial Split-Bridge™ technology interface 30 in a controller 30 with commercially available custom electronic control circuitry since much of such as Cardbus, the controller 20 can communicate with either Cardbus or PCMCIA, or via the serial link Split-Bridge™ remote PCI devices. Since much of the PCI interface electronics are commonly used by the respective interfaces, the integrating of the circuitry 30 is very economical.

The present invention 20 facilitates the evolution of information transfer to offer high speed serial link connectivity exceeding data rates of 1.0 GHZ for use with PCI, Cardbus, integrated, or other parallel I/O bus architectures. Moreover, conventional digital signal processors, such as those manufactured by Texas Instruments Incorporated of Dallas, Tex., (DSPs) being employed on extended Cardbus/PC card controllers are well adapted to interface with and incorporate the serial Split-Bridge™ technology interface. Integrating commercially available Cardbus/PC card controller electronics with the proprietary serial Split-Bridge™ technology significantly improves performance and available features of the device 30 with nominal additional cost associated therewith. In fact, the price versus performance improvement of the present invention shown in FIG. 4 is a quantum leap over existing price-performance points.

The Split-Bridge™ serial interface electronics 30 can be designed into a custom Application Specific Integrated Circuit (ASIC) along with other electronics, moreover, multiple interfaces 30 can be employed on to a single controller 20 and multiplexed to interface with multiple internal or external devices and users. Accordingly, limitation to integration of a single Split-Bridge™ interface is not to be inferred, but rather parallel buses and possibly future general serial buses, can be interfaced to other devices using the proprietary Split-Bridge™ serial technology.

In summary, the improved Cardbus/PC card controller 20 facilitates improved connectivity between a system parallel bus and remote peripheral devices, allowing data connectivity via either the proprietary serial Split-Bridge™ technology, or via the standard PC card slots such as those based on the PCMCIA standards. Existing electronics, including DSPs, are well adapted to interface with ASICs or other discrete/custom componentry comprising the interface and employing the serials Split-Bridge™ technology.

Though the invention has been described with respect to a specific preferred embodiment, many variations and modifications will become apparent to those skilled in the art upon reading the present application. It is therefore the intention that the appended claims be interpreted as broadly as possible in view of the prior art to include all such variations and modifications.

Claims

1. An interface comprising:

first electronics adapted to interface parallel data from a parallel data bus to a first bus; and
second electronics adapted configured to interface said parallel data from said parallel data bus into serial data adapted and configured to interface with a second remote bus, said second electronics configured to converting said parallel data into said serial data and, without inserting bus wait states, send said serial data to said second remote bus without requiring any external signal from said second remote bus.

2. The interface as specified in claim 1 wherein said second electronics comprises Split-Bridge™ split-bridge serial interface electronics.

3. The interface as specified in claim 1 wherein said parallel data bus is based on PCI-type or PCMCIA-type interface standards.

4. The interface as specified in claim 1 wherein said serial data has a serial data rate exceeding 1.0 Giga bits/second.

5. The interface as specified in claim 1 wherein said first electronics comprises a digital signal processor (DSP).

6. The interface card as specified in claim 1 wherein said first electronics comprises Cardbus electronics.

7. The interface card as specified in claim 1 wherein said first electronics and said second electronics are adapted to concurrently support transfer of data to said respective first bus and said second buses remote bus, respectively.

8. A method of interfacing parallel data on a parallel system bus to a first bus and a second remote bus, comprising the steps of:

a) converting a first portion of the parallel data on the parallel system bus to parallel data adapted to communicate with said first bus; and
b) converting a second portion of the parallel data on the parallel system bus to high-speed serial data, which said serial data is sent, without inserting bus wait states, to the second remote bus without requiring or receiving a signal from said second remote bus before sending said serial data.

9. The method as specified in claim 8 further comprising the step of using a Split-Bridge™ split-bridge serial interface.

10. The method as specified in claim 8 wherein said parallel system bus is based on PCI-type or Cardbus-type bus standard.

11. The method as specified in claim 8 wherein said serial data is sent at a data rate exceeding 1.0 GHZ.

12. The method as specified in claim 8 wherein said step a) and said step b) are performed in a single electronic device.

13. The method as specified in claim 12 wherein said electronic device comprises a Digital Signal Processor (DSP).

14. The method as specified in claim 8 wherein a retry message is sent in advance of sending said serial data.

15. The method as specified in claim 8 wherein said step a) uses Cardbus electronics.

16. An interface comprising:

first electronics adapted to interface parallel data from a parallel data bus to a first bus; and
second electronics configured to interface said parallel data from said parallel data bus into serial data and configured to interface with a second remote bus, said second electronics configured to convert said parallel data into said serial data and, without additional bus wait states, send said serial data to said second remote bus, said second electronics configured to add tag data indicative of a transaction type to the serial data.

17. The interface as specified in claim 16 wherein said second electronics comprises split-bridge serial interface electronics.

18. The interface as specified in claim 16 wherein said parallel data bus is based on PCI-type or PCMCIA-type interface standards.

19. The interface as specified in claim 16 wherein said serial data has a serial data rate exceeding 1.0 Giga bits/second.

20. The interface as specified in claim 16 wherein said first electronics comprises a digital signal processor (DSP).

21. The interface card as specified in claim 16 wherein said first electronics comprises Cardbus electronics.

22. The interface card as specified in claim 16 wherein said first electronics and said second electronics are adapted to support transfer of data to said first bus and said second remote bus, respectively.

23. A method of interfacing parallel data on a parallel system bus to a first bus and a second remote bus, comprising:

a) converting a first portion of the parallel data on the parallel system bus to parallel data adapted to communicate with said first bus; and
b) converting a second portion of the parallel data on the parallel system bus to high-speed serial data, which said serial data is sent, without requiring bus wait states, to the second remote bus, said serial data including a tag indicative of a transaction type.

24. The method as specified in claim 23 further comprising the step of using a split-bridge serial interface.

25. The method as specified in claim 23 wherein said parallel system bus is based on PCI or Cardbus bus standard.

26. The method as specified in claim 23 wherein said serial data is sent at a data rate exceeding 1.0 GHZ.

27. The method as specified in claim 23 wherein said step a) and said step b) are performed in a single electronic device.

28. The method as specified in claim 27 wherein said electronic device comprises a Digital Signal Processor (DSP).

29. The method as specified in claim 23 wherein a retry message is sent in advance of sending said serial data.

30. The method as specified in claim 23 wherein said step a) uses Cardbus electronics.

31. An interface, comprising:

first electronics configured to interface parallel data from a parallel data bus to a first bus; and
second electronics configured to interface said parallel data from said parallel data bus into serial data and configured to interface with a second remote bus, said second electronics configured to add tag data indicative of a transaction type to the serial data.

32. The interface as specified in claim 31 wherein said parallel data bus is based on PCI standard.

33. The interface as specified in claim 31 wherein said second electronics further comprises a data register configured to store said parallel data.

34. The interface as specified in claim 33 wherein said second electronics is configured to mirror said data register parallel data to a register of another remote said interface.

35. The interface as specified in claim 31 wherein said second electronics is configured to add said tag data during a transaction.

36. The interface as specified in claim 35 wherein the second electronics is configured to proceed to a data cycle without delay.

Referenced Cited
U.S. Patent Documents
3800097 March 1974 Maruscak et al.
4112369 September 5, 1978 Forman et al.
4413319 November 1, 1983 Schultz et al.
4504927 March 12, 1985 Callan
4535421 August 13, 1985 Duwel et al.
4591660 May 27, 1986 Scordo
4787029 November 22, 1988 Khan
4882702 November 21, 1989 Struger et al.
4901308 February 13, 1990 Deschaine
4941845 July 17, 1990 Eppley et al.
4954949 September 4, 1990 Rubin
4959833 September 25, 1990 Mercola et al.
4961140 October 2, 1990 Pechanek et al.
4969830 November 13, 1990 Daly et al.
5006981 April 9, 1991 Beltz et al.
5038320 August 6, 1991 Heath et al.
5111423 May 5, 1992 Kopec, Jr. et al.
5134702 July 28, 1992 Charych et al.
5187645 February 16, 1993 Spalding et al.
5191653 March 2, 1993 Banks et al.
5191657 March 1993 Ludwig et al.
5237690 August 17, 1993 Bealkowski et al.
5274711 December 28, 1993 Rutledge et al.
5301349 April 5, 1994 Nakata et al.
5313589 May 17, 1994 Donaldson et al.
5325491 June 28, 1994 Fasig
5335326 August 2, 1994 Nguyen et al.
5335329 August 2, 1994 Cox et al.
5357621 October 18, 1994 Cox
5373149 December 13, 1994 Rasmussen
5377184 December 27, 1994 Beal et al.
5430847 July 4, 1995 Bradley et al.
5432916 July 11, 1995 Hahn et al.
5440698 August 8, 1995 Sindhu et al.
5446869 August 29, 1995 Padgett et al.
5452180 September 19, 1995 Register et al.
5457785 October 10, 1995 Kikinis et al.
5469545 November 21, 1995 Vanbuskirk et al.
5475818 December 12, 1995 Molyneaux et al.
5477415 December 19, 1995 Mitcham et al.
5483020 January 9, 1996 Hardie et al.
5488705 January 30, 1996 LaBarbera
5495569 February 27, 1996 Kotzur
5497498 March 5, 1996 Taylor
5507002 April 9, 1996 Heil
5517623 May 14, 1996 Farrell et al.
5522050 May 28, 1996 Amini et al.
5524252 June 4, 1996 Desai et al.
5530895 June 25, 1996 Enstrom
5540597 July 30, 1996 Budman et al.
5542055 July 30, 1996 Amini et al.
5548730 August 20, 1996 Young
5555510 September 10, 1996 Verseput et al.
5561806 October 1, 1996 Fitchett et al.
5572525 November 5, 1996 Shen et al.
5572688 November 5, 1996 Sytwu
5579489 November 26, 1996 Dornier et al.
5579491 November 26, 1996 Jeffries et al.
5586265 December 17, 1996 Beukema
5590377 December 31, 1996 Smith
5611053 March 11, 1997 Wu et al.
5632020 May 20, 1997 Gephardt et al.
5634080 May 27, 1997 Kikinis et al.
5655142 August 5, 1997 Gephardt et al.
5671421 September 23, 1997 Kardach et al.
5694556 December 2, 1997 Neal et al.
5696911 December 9, 1997 Fredriksson
5696949 December 9, 1997 Young
5701483 December 23, 1997 Pun
5724529 March 3, 1998 Smith et al.
5736968 April 7, 1998 Tsakiris
5748921 May 5, 1998 Lambrecht et al.
5764924 June 9, 1998 Hong
5774681 June 30, 1998 Kunishige
5781747 July 14, 1998 Smith et al.
5793995 August 11, 1998 Riley et al.
5793996 August 11, 1998 Childers et al.
5799207 August 25, 1998 Wang et al.
5802055 September 1, 1998 Krein et al.
5809262 September 15, 1998 Potter
5815677 September 29, 1998 Goodrum
5819053 October 6, 1998 Goodrum et al.
5832279 November 3, 1998 Rostoker et al.
5835741 November 10, 1998 Elkhoury et al.
5854908 December 29, 1998 Ogilvie et al.
5884027 March 16, 1999 Garbus et al.
5905870 May 18, 1999 Mangin et al.
5911055 June 8, 1999 Whiteman et al.
5913037 June 15, 1999 Spofford et al.
5941965 August 24, 1999 Moroz et al.
5948076 September 7, 1999 Anubolu et al.
5953511 September 14, 1999 Sescila et al.
5968144 October 19, 1999 Walker et al.
5991304 November 23, 1999 Abramson
5991839 November 23, 1999 Ninomiya
6003105 December 14, 1999 Vicard et al.
6026075 February 15, 2000 Linville et al.
6031821 February 29, 2000 Kalkunte et al.
6035333 March 7, 2000 Jeffries et al.
6044215 March 28, 2000 Charles et al.
6058144 May 2, 2000 Brown
6070214 May 30, 2000 Ahern
6084856 July 4, 2000 Simmons et al.
6085278 July 4, 2000 Gates et al.
6098103 August 1, 2000 Dreyer et al.
6101563 August 8, 2000 Fields, Jr. et al.
6115356 September 5, 2000 Kalkunte et al.
6141744 October 31, 2000 Wing So
6157967 December 5, 2000 Horst et al.
6167029 December 26, 2000 Ramakrishnan
6167120 December 26, 2000 Kikinis
6170022 January 2, 2001 Linville et al.
6201829 March 13, 2001 Schneider
6216185 April 10, 2001 Chu
6222825 April 24, 2001 Mangin et al.
6233639 May 15, 2001 Dell et al.
6237046 May 22, 2001 Ohmura et al.
6247086 June 12, 2001 Allingham
6247091 June 12, 2001 Lovett
6256691 July 3, 2001 Moroz et al.
6260092 July 10, 2001 Story et al.
6263385 July 17, 2001 Gulick et al.
6263397 July 17, 2001 Wu et al.
6275888 August 14, 2001 Porterfield
6295281 September 25, 2001 Itkowsky et al.
6333929 December 25, 2001 Drottar et al.
6366951 April 2, 2002 Schmidt
6381661 April 30, 2002 Messerly et al.
6385671 May 7, 2002 Hunsaker et al.
6401157 June 4, 2002 Nguyen et al.
6418492 July 9, 2002 Papa
6418494 July 9, 2002 Remigius
6421352 July 16, 2002 Manaka et al.
6425033 July 23, 2002 Conway et al.
6430635 August 6, 2002 Kwon et al.
6445711 September 3, 2002 Scheel et al.
6446192 September 3, 2002 Narasimhan et al.
6452927 September 17, 2002 Rich
6456590 September 24, 2002 Ren et al.
6457081 September 24, 2002 Gulick
6457091 September 24, 2002 Lange et al.
6473810 October 29, 2002 Patel et al.
6493745 December 10, 2002 Cherian
RE37980 February 4, 2003 Elkhoury et al.
6567876 May 20, 2003 Stufflebeam
6578101 June 10, 2003 Ahern
6581125 June 17, 2003 Lange et al.
6594719 July 15, 2003 Ahern et al.
6671737 December 30, 2003 Snowdon et al.
6715022 March 30, 2004 Ahern
6728822 April 27, 2004 Sugawara et al.
6778543 August 17, 2004 Frouin et al.
6788101 September 7, 2004 Rahman
6950440 September 27, 2005 Conway
7047326 May 16, 2006 Crosbie et al.
7269680 September 11, 2007 Ahern
7356634 April 8, 2008 Ahern
7657678 February 2, 2010 Ahern
20010011312 August 2, 2001 Chu
20010037423 November 1, 2001 Conway et al.
20020078289 June 20, 2002 Morrow
20020135536 September 26, 2002 Bruning
20040088452 May 6, 2004 Scott
20050036509 February 17, 2005 Acharya et al.
20050129385 June 16, 2005 Speasl et al.
20050174488 August 11, 2005 Chennakeshu
20060075166 April 6, 2006 Grassian
Foreign Patent Documents
1473292 February 2004 CN
19829212 January 2000 DE
0820021 January 1998 EP
820021 January 1998 EP
0844567 May 1998 EP
1374024 January 2004 EP
02-140852 May 1990 JP
3253960 November 1991 JP
3001429 February 1994 JP
06-028307 February 1994 JP
59184903 October 1994 JP
9081504 March 1997 JP
9097125 April 1997 JP
10049379 February 1998 JP
10124451 May 1998 JP
2003050661 February 2003 JP
2004531803 October 2004 JP
WO-9302420 February 1993 WO
WO-9700481 January 1997 WO
WO-0161512 August 2001 WO
WO-0161513 August 2001 WO
WO-02077785 October 2002 WO
Other references
  • IEEE Microprocessor and Microcomputer Standards Committee, P1394a Draft Standard for a High Performance Serial Bus (Amendment), Feb. 11, 2000, IEEE Computer Society, Draft 5.0, pp. i-v, 131-134, 140, and 144-150.
  • “Notice of allowance”, Appl. No. 11/300,131, (Dec. 4, 2009), 4 pages.
  • “Non Final Office Action”, U.S. Appl. No. 09/559,678, (Oct. 30, 2008), 8 pages.
  • “Non Final Office Action”, U.S. Appl. No. 09/559,678, (Mar. 27, 2008), 9 pages.
  • “Final Office Action”, U.S. Appl. No. 09/559,678, (Aug. 20, 2007), 8 pages.
  • “Non Final Office Action”, U.S. Appl. No. 09/559,678, (Nov. 24, 2006), 9 pages.
  • “Non Final Office Action”, U.S. Appl. No. 09/559,678, (May 2, 2006), 7 pages.
  • “Final Office Action”, U.S. Appl. No. 09/559,678, (Nov. 8, 2005), 7 pages.
  • “Non Final Office Action”, U.S. Appl. No. 09/559,678, (Mar. 8, 2008), 8 pages.
  • “Final Office Action”, U.S. Appl. No. 09/559,678, (Jun. 22, 2004), 7 pages.
  • “Non Final Office Action”, U.S. Appl. No. 09/559,678, (Sep. 17, 2005), 7 pages.
  • “Non Final Office Action”, U.S. Appl. No. 09/559,678, (Dec. 4, 2002), 9 pages.
  • “Non Final Office Action”, U.S. Appl. No. 11/513,806, (Mar. 12, 2007), 10 pages.
  • “Final Office Action”, U.S. Appl. No. 11/513,806, (Sep. 27, 2007), 8 pages.
  • “Advisory Action”, U.S. Appl. No. 11/513,806, PTOL 303, (Apr. 10, 2008), 4 pages.
  • “Non Final Office Action”, U.S. Appl. No. 11/513,806, (Oct. 2, 2008), 22 pages.
  • “Non Final Office Action”, U.S. Appl. No. 11/300,131, (Dec. 15, 2006), 13 pages.
  • “Final Office Action”, U.S. Appl. No. 11/300,131, (Aug. 20, 2007), 9 pages.
  • “Non Final Office Action”, U.S. Appl. No. 11/300,131, (Mar. 27, 2008), 12 pages.
  • “Non Final Office Action”, U.S. Appl. No. 11/300,131, (Nov. 12, 2008), 20 pages.
  • “Non Final Office Action”, U.S. Appl. No. 10/766,660, (May 15, 2006),17 pages.
  • “Final Office Action”, U.S. Appl. No. 10/766,660, (Dec. 4, 2006),17 pages.
  • “Non Final Office Action”, U.S. Appl. No. 09/130,057, (Jul. 21, 1999),27 pages.
  • “Notice of Allowance”, U.S. Appl. No. 09/130,057, (Feb. 25, 2000),12 pages.
  • “Non Final Office Action”, U.S. Appl. No. 10/782,082, (Jun. 9, 2006),17 pages.
  • “Final Office Action”, U.S. Appl. No. 10/782,082, (Mar. 6, 2007),14 pages.
  • “Advisory Action”, U.S. Appl. No. 10/782,082, (Jul. 9, 2007),3 pages.
  • “Non Final Office Action”, U.S. Appl. No. 10/782,082, (Nov. 9, 2007),12 Pages.
  • “Final Office Action”, U.S. Appl. No. 10/782,082, (Aug. 11, 2008),26 pages.
  • “Final Office Action”, U.S. Appl. No. 10/782,082, (Feb. 2, 2009),27 pages.
  • “Non Final Office Action”, U.S. Appl. No. 09/559,677, (Jun. 26, 2002),4 pages.
  • “Non Final Office Action”, U.S. Appl. No. 09/559,677, (Dec. 12, 2002),5 pages.
  • “Notice of Allowance”, U.S. Appl. No. 09/559,677, (Mar. 20, 2003),3 pages.
  • “PCI to PCI Bridge Architecture Specification”, Author—PCI Special Interest Group Revision 1.0, (Apr. 5, 1994),26 pages.
  • “PCI-to-PCI Bridge Architecture Specification”, PCI Local Bus; XP-002382184; Revision 1.1, (Dec. 18, 1998),148 pages.
  • “Non Final Office Action”, U.S. Appl. No. 09/819,053, (Apr. 22, 2004),12 pages.
  • “Final Office Action”, U.S. Appl. No. 09/819,053, (Jul. 12, 2005),46 pages.
  • “Non Final Office Action”, U.S. Appl. No. 09/819,053, (Mar. 2, 2006),14 pages.
  • “Notice of Allowance”, U.S. Appl. No. 09/819,053, (Jun. 15, 2007),13 pages.
  • “Patent Abstract of Japan vol. 2003, No. 6, Jun. 3, 2003 & JP 2003 050661”, Casio Computer Co., Ltd., (Feb. 21, 2003),1 page.
  • “International Search Report”, PCT/US2005/006089, (Jun. 12, 2005),4 pages.
  • Fulp, C. D., et al., “A Wireless Handheld System for Interactive Multimedia-Enhanced Instruction”, FIE 2002. 32nd Annual Frontiers In Education Conference, Boston, MA., Nov. 6-9, 2002, Frontiers In Education Conference, New York, NY: IEEE, US, vol. 1 of 3, Conf. 32, (Nov. 6, 2002),4 pages.
  • “Notice of Allowance”, U.S. Appl. No. 09/819,057, (Mar. 14, 2003),4 pages.
  • “Non Final Office Action”, U.S. Appl. No. 09/819,057, (Nov. 26, 2002),7 pages.
  • “Notice of Allowance”, U.S. Appl. No. 09/819,054, (Dec. 2, 2003),8 pages.
  • “Non Final Office Action”, U.S. Appl. No. 09/819,054, (Jan. 28, 2003),11 pages.
  • “Notice of Allowance”, U.S. Appl. No. 09/130,058, (Feb. 25, 2000),4 pages.
  • “Non Final Office Action”, U.S. Appl. No. 09/130,058, (Jul. 21, 1999),32 pages.
  • “Non Final Office Action”, U.S. Appl. No. 11/513,976, (Oct. 27, 2006),10 pages.
  • “Notice of Allowance”, U.S. Appl. No. 11/513,976, (Jan. 16, 2008),7 pages.
  • “Foreign Office Action”, Application Serial No. 2,445,711, (Mar. 18, 2009),2 pages.
  • “Notice of Allowance/Base Issue Fee”, U.S. Appl. No. 11/300,131, (Jun. 18, 2009),12 pages.
  • “Advisory Action”, U.S. Appl. No. 10/782,082, (Apr. 7, 2009),3 pages.
  • “Notice of Allowance”, U.S. Appl. No. 09/559,678, (Jun. 26, 2009),4 pages.
  • “International Search Report”, EP01925078, (Oct. 30, 2001),2 Pages.
  • “International Search Report”, PCT/US2001/12678, (Oct. 30, 2001),2 pages.
  • “European Search Report”, EP07000788, (Oct. 1, 2008),1 Pages.
  • “International Search Report”, PCT/US2001/12666, (Nov. 15, 2001),2 pages.
  • “Allowed Claims”, U.S. Appl. No. 09/559,678, (Jun. 26, 2009),9 pages.
  • “Allowed Claims”, U.S. Appl. No. 11/300,131, (Jun. 18, 2009),7 pages.
  • Gillett, Richard B., “Memory Channel Network for PCI”, IEEE 1996, (1996),7 pages.
  • Ekiz, H. et al., “Performance Analysis of a CAN/CAN Bridge”, IEEE 1996, describes a Bridge Process Model with Bridge Port A and Bridge Port B. The Bridge Port A connects to a LAN 1 Data Lin. Next, the Bridge Port B connects to a LAN 2 Data Link (see fig. 2).,(1996),8 pages.
  • Marsden, Philip “Interworking IEEE 802/FDDI LAN's Via the ISDN Frame Relay Bearer Service”, Proceedings of the IEEE, vol. 79, No. 2, Feb. 1991, describes ISDN MAC Bridge/Routers. The Bridge/Router connects directly to each other via 2Mbit/s ISDN interface (see fig. 6), (Feb. 1991),p. 223-229.
  • Gillett, Richard B., et al., “Using the Memory Channel Network”, IEEE 1997, (1997),p. 19-25.
  • Annamalai, Kay “Multi-ported PCI-to-PCI Bridge Chip”, IEEE 1997, (1997),p. 426-433.
  • Mora, F et al., “Design of a high performance PCI interface for an SCI network”, Computing & Control Engineering Journal, Dec. 1998., (Dec. 1998),p. 275-282.
  • Skaali, B et al., “A Prototype DAQ System for the Alice Experiment Based on SCI”, IEEE Transactions on Nuclear Science, vol. 45, Aug. 1998, (Aug. 1998), 1917-1922.
  • Mora, F et al., “Electronic Design of a High Performance Interface to the SCI Network”, IEEE 1998, (1998),p. 535-538.
  • Harper, Stephen “Update on PCMCIA Standard Activities: Cardbus and Beyond”, PCMCIA 1995, (1995),p. 136-144.
  • Bui, et al., “60x Bus-to-PCI Bridge”, IBM TDB May 1995, (May 1995),p. 401-402.
  • Anon, “Remote Memory Access Interface Between Two Personal Computers”, IBM Technical Disclosure Bulletin v 28 n Feb. 9, 1986, (1986),4110-4113.
  • Karl, Wolfgang et al., “SCI monitoring hardware and software: supporting performance evaluation and debugging”, Book Title: SCI: scalable coherent interface. Architecture and software for high-performance compute cluster,(1999),p. 417-432.
  • Poor, Alfred “The Expansion Bus.(ISA, PCI, and AGP)(Technology Information)”, PC Magazine, 194(1) Jan. 19, 1999, (Jan. 19, 1999),5 pages.
  • Surkan, Michael “NetFrame takes lead in reliability: ClusterSystem's hot-swappable PCI a”, PC Week, v14, n34, p60(1) Aug. 11, 1997, NetFRAME System' ClusterSystem 9008 Pentium Pro-based system) (Hardware Review)(Evaluation),(Aug. 11, 1997),4 pages.
  • Balatsos, A et al., “A bridge for a multiprocessor graphics system”, Proceedings of the 2002 IEEE Canadian Conference on Electrical and Computer Engineering, (2002),p. 646-650.
  • “MC68HC11A8—HCMOS Single-Chip Microcontroller”, Motorola, Inc. 1996, (1996),158 pages.
  • “Foreign Office Action”, Application Serial No. 2001-560830, (Mar. 19, 2009), 3 pages.
  • “Foreign Office Action”, Application Serial No. 2001-560831, (Mar. 19, 2009), 3 pages.
  • “Foreign Office Action”, Application Serial No. 2006-203273, (Jul. 21, 2009), 10 pages.
  • “Foreign Office Action”, Application Serial No. 2006-203293, (Jun. 26, 2009), 9 pages.
  • “Notice of Allowance”, U.S. Appl. No. 11/300,131, (Oct. 22, 2009), 4 pages.
  • “Notice of Allowance”, U.S. Appl. No. 09/559,678, (Oct. 26, 2009), 4 pages.
  • “PCI-to-PCI Bridge Architecture Specification”, Chapter 5—Buffer Management, Tables 5-1, (Dec. 18, 1998),pp. 69-92.
  • Brochure entitled “Card Station Expanding Your Portable World” Axonix Corporation 1994.
  • Anderson, et al “CardBus System Architecture” pp. 150-153, 194-201, 228-231, 322-325,1995.
  • Anderson, Don “PCMCIA System Architecture” 16-Bit PC Cards, 2nd Edition, pp. 146-167, 214-215, 218-225, 296-297, 1995.
  • Kitamura, et al “Design of the ISDN PC Card” NTT Human Interface Laboratory, Japan pp. 1169-1174, 1994.
  • Adaptec, “Hardware Istallation Guide” CardPark APA-4510, ISA-to-PCMCIA Card Adapter for Desktop PC's, pp. 1-7.
  • Adaptec, “SlimSCSI 1460 For Fast, Easy Connections to All SCSI Devices” 6 pages.
  • Edge: Work-Group Computing Report, Nov. 21, 1994 “PCMCIA: Adaptec targets mobile computing market with two new host adapters that relieve problem of system-to-system and peripheral connectivity” 2 pages.
  • “Notice of Allowance”, U.S. Appl. No. 09/559,678, (Jan. 29, 2010), 4 pages.
Patent History
Patent number: RE41494
Type: Grant
Filed: Jul 15, 2005
Date of Patent: Aug 10, 2010
Inventors: Frank W. Ahern (Payson, AZ), Doss Jeff (Scottsdale, AZ), Charles Mollo (Phoenix, AZ)
Primary Examiner: Glenn A Auve
Application Number: 11/183,298
Classifications
Current U.S. Class: Bus Expansion Or Extension (710/300); Bus Interface Architecture (710/305); Bus Bridge (710/306); Different Protocol (e.g., Pci To Isa) (710/315)
International Classification: G06F 13/00 (20060101);