The present invention relates generally to virtual machines, and more specifically to constructing host processor soft devices independent of the host processor operating system.
A host-based soft device is a hardware device that includes a host software component and a reduced functionality hardware component: respectively a host processor device driver and a “residual” fixed function device. The host processor device driver replaces portions of a fixed function device in a personal computing system (e.g., personal computers, personal digital assistants, etc.). Conventional fixed function devices incorporate one or more dedicated general and special purpose processors (e.g., a microcontroller, a digital signal processor, etc.) and a limited amount of dedicated random access memory (RAM) and read-only memory (ROM). In a host-based soft device, software that executes on one or more dedicated processors is replaced by a host processor device driver that uses main system memory. Typically, a host-based soft device is less expensive than the conventional fixed function devices because the “residual” fixed function device that requires fewer dedicated processors and smaller amounts of dedicated RAM and ROM. In addition, because the host processor is far more powerful than the dedicated processors and has access to more memory, a host-based soft device is often able to use more powerful algorithms, thereby improving performance, increasing efficiency and/or providing higher benchmark scores.
Despite the above advantages of host-based soft devices, their implementation has been limited almost entirely to Microsoft Windows operating systems due to the large market share of Windows family of operating systems, leaving other personal computer operating systems (e.g., BeOS) without available host-based soft devices. In addition, the development of a soft device for Windows has not been an easy process. Recent experience with Windows-based soft devices has shown the inability of Microsoft to develop a stable device driver model. For instance, during the year of 1999, soft modem vendors were simultaneously required to port device software to four different soft modem device drivers for each soft device: specifically, V×D for Windows 98, WDM 1.0 for Windows 98SE, NT for Windows NT 4.0 and WDM 2.0 for Beta releases of Windows 2000. In addition, Windows-based soft devices suffer from excessive latency in the host operating system because Windows operating systems lack real-time quality of service (QoS) guarantees.
Therefore, it would be advantageous to construct a host processor soft device that would be independent of the host processor operating system.
The present invention is illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings and in which like reference numerals refer to similar elements and in which:
Methods and apparatus for constructing host processor soft devices independent of the host processor operating system are described. In the following descriptions, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the present invention. It will be apparent, however, to one skilled in the art that the present invention can be practiced without these specific details.
Some portions of the detailed descriptions that follow are presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the means used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm is here, and generally, conceived to be a self-consistent sequence of steps leading to a desired result. The steps are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like.
It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the following discussions, it is appreciated that throughout the present invention, discussions utilizing terms such as “processing” or “computing” or “calculating” or “determining” or “displaying” or the like, may refer to the action and processes of a computer system, or similar electronic computing device, that manipulates and transforms data represented as physical (electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission or display devices.
The present invention also relates to apparatus for performing the operations herein. This apparatus may be specially constructed for the required purposes, or it may comprise a general purpose computer selectively activated or reconfigured by a computer program stored in the computer. Such a computer program may be stored in a computer readable storage medium, such as, but is not limited to, any type of disk including floppy disks, optical disks, CD-ROMs, and magnetic-optical disks, read-only memories (ROMs), random access memories (RAMs), EPROMs, EEPROMs, magnetic or optical cards, or any type of media suitable for storing electronic instructions, and each coupled to a computer system bus. Instructions are executable using one or more processing devices (e.g., processors, central processing units, etc.).
The algorithms and displays presented herein are not inherently related to any particular computer or other apparatus. Various general purpose machines may be used with programs in accordance with the teachings herein, or it may prove convenient to construct more specialized apparatus to perform the required method steps. The required structure for a variety of these machines will appear from the description below. In addition, the present invention is not described with reference to any particular programming language. It will be appreciated that a variety of programming languages may be used to implement the teachings of the invention as described herein.
In the following detailed description of the embodiments, reference is made to the accompanying drawings that show, by way of illustration, specific embodiments in which the invention may be practiced. In the drawings, like numerals describe substantially similar components throughout the several views. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention. Other embodiments may be utilized and structural, logical, and electrical changes may be made without departing from the scope of the present invention. Moreover, it is to be understood that the various embodiments of the invention, although different, are not necessarily mutually exclusive. For example, a particular feature, structure, or characteristic described in one embodiment may be included within other embodiments. The following detailed description is, therefore, not to be taken in a limiting sense, and the scope of the present invention is defined only by the appended claims, along with the full scope of equivalents to which such claims are entitled.
As described above, the VMM 112 presents to other software (i.e., “guest” software) the abstraction of one or more virtual machines (VMs).
The present invention provides a mechanism for constructing a host processor soft device independent of the host processor OS (host OS) in a virtual-machine environment.
Referring to
The soft device driver 208 can be implemented in the same manner as a host-based soft device driver would be implemented in a conventional host OS. However, while a host OS soft device driver operates in such a way as to export a standard device abstraction to the host OS, the soft device driver 208 implemented in the VMM 112 exports an emulation of a fixed function hardware device to VMs 102 and/or 114. The guest OS 106 or 114 then runs a standard device driver and attempts to read from, and write to, hardware registers of an emulated fixed function hardware device. The soft device driver 208 recognizes these attempts of the guest OS 106 or 114 to interact with hardware registers that may not exist and emulates the functionality of a fixed function hardware device.
In some embodiments (e.g., when the corresponding functionality is performed by the host processor), the soft device driver 208 emulates the functionality of a fixed function device by performing the requested computations without any notification to the residual fixed function device 204.
In other embodiments, the soft device driver may pass the read or write command without alteration to the residual fixed function device 204 to perform an operation requested by the guest OS 106 or 114.
In still other embodiments, the soft device driver 208 may perform some of the requested computations and may then perform one or a whole series of similar or completely different operations on the actual hardware registers of the residual fixed function device 204 in order to complete the task that the guest OS 106 or 114 requested.
In yet other embodiments, the residual fixed function device 204 is capable of directly accessing system memory. In one embodiment, the soft device driver 208 performs zero or more transformations on data received from guest OS 106 or 114 before directly transferring the data to system memory at a predefined location from which the residual fixed function device 204 will fetch the data in order to effect the operation requested by the guest OS 106 or 114. In another embodiment, the soft device driver 208 performs zero or more transformations on data directly transferred to system memory at a predefined location by the residual fixed function device 204, said transformed data then being transferred to the guest OS 106 or 114 in order to complete the requested operation.
Subsequently, when a request to use the soft device is received from a virtual machine coupled to the VMM (processing block 306), the soft device is made available for use by this virtual machine (processing block 308). In one embodiment, making the soft device available for use by the virtual machine includes exporting an emulation of a fixed function hardware device to this virtual machine, recognizing the attempts of the virtual machine to read and write to hardware registers of the emulated device, and emulating the functionality of a fixed function hardware device to perform the read and or write operation requested by the virtual machine. In one embodiment, this functionality is emulated by the soft device driver performing the requested computations without any notification to a hardware component of the soft device (i.e., a residual fixed function device). In an alternative embodiment, the functionality is emulated by the hardware component of the soft device which receives the read or write command from the soft device driver and executes this command to perform an operation requested by the virtual machine. In still another embodiment, the soft device driver performs some of the requested computations and then performs one or a whole series of similar or completely different operations on the actual hardware registers of the residual fixed function device in order to complete the task intended by the virtual machine. In yet another embodiment, the residual fixed function device 204 is capable of directly accessing system memory and transfers data to or from system memory at predefined locations, and the soft device driver manipulates data stored in memory according to the operation requested by the virtual machine. For instance, the soft device driver performs the write command received from the virtual machine by transforming the data in the memory appropriately and then transferring the requested data to the memory using the direct memory access (DMA) technique.
It should be noted that any combination of the above actions can be used by the soft device driver to emulate the functionality of a fixed function hardware device without loss of generality. In one embodiment, the virtual machine runs an arbitrary OS (e.g., Linux), for which no soft device drivers exist on the market. Accordingly, the VMM implementation of a soft device driver enables a soft device to be accessed from a wide variety of host OSes, including host OSes for which no appropriate soft device drivers exist on the market. In addition, such soft device drivers do not suffer from latency problems in the host OS because they are implemented beneath the host OS.
The VMM 112 ensures that the soft device is available for use by the virtual machine 406 when needed. In particular, the VMM 112 provides such communication between the virtual machines 406 and 408 as to make the soft device controlled by the dedicated virtual machine 408 available to the virtual machine 406. This communication is accomplished using a virtualized connectivity means 404 that represents a software version of such connectivity means as a local area network (LAN) (presented to each of VMs 406 and 408 as a virtual network interface card (NIC)), a serial communications link (presented to each of VMs 406 and 408 as a virtual serial port (e.g., COM 1)), a universal serial bus (USB) to USB bridge (presented to each of VMs 406 and 408 as a virtual USB “host controller” connected to a USB to USB bridge device), a peripheral component interconnect (PCI) bus, a USB connection (presented to VM 406 as a virtual USB “host controller” and to VM 408 as a virtual USB bus interface), etc. The virtual machine implementation of a soft device allows construction of a soft device that is not only OS independent but also VMM independent. That is, the soft device driver does not need to be written for use with a particular VMM. Again, such a soft device is immune to latency in the host OS because its driver is executed in a dedicated virtual machine.
In one embodiment, the dedicated virtual machine 408 includes reflection software 414 (e.g., a reflection application or driver) which links the software component 418 (e.g., a soft device driver) and the virtualized connectivity means together. For instance, the reflection software 414 may be configured to read from the serial port COM1 and write to the soft device driver, and vice versa. In alternative embodiments, a direct communication between the software component 418 and the virtualized connectivity means is provided, thereby obviating the need for the reflection software 414.
In one embodiment, the dedicated virtual machine 408 is configured to match the underlying host platform. In this embodiment, the dedicated virtual machine 408 may execute a conventional soft device driver that is written for the OS 416. For instance, the dedicated virtual machine may execute a soft modem driver under Windows NT 4.0. The virtual machine 406 may instead run an arbitrary OS for which no soft device driver need be or have been written. For instance, the virtual machine 406 may run Linux, Unix, BeOS, or any other OS. When the dedicated virtual machine 408 is configured to match the underlying host platform, the VMM 112 may present the dedicated virtual machine 408 to the virtual machine 406 as an external conventional fixed function device using a virtualized serial communications port (COML) or virtualized USB “host controller” or as an internal conventional fixed function device using a virtualized local bus (e.g., a PCI bus). These embodiments of the present invention will be described in greater detail below in conjunction with
In an alternative embodiment, the dedicated virtual machine 408 is configured to match an existing hardware device (e.g., a PCI card, a USB device, etc.), and may differ significantly from the host platform. In this embodiment which is described in more detail below in conjunction with
Subsequently, when a request to use the soft device is received from the main virtual machine (processing block 506), the soft device is made available for use by the main virtual machine (processing block 508).
In one embodiment, making the soft device available for use by the main virtual machine includes presenting the dedicated virtual machine to the main virtual machine as either an external or an internal conventional fixed function device and emulating communication between the dedicated virtual machine and the main virtual machine. This communication is emulated by providing a virtualized connectivity means, linking the virtualized connectivity means to the soft device driver, trapping all accesses by one of the two virtual machines to the virtualized connectivity means, and re-directing these accesses to the other of the two virtual machines. In one embodiment, the virtualized connectivity means is a virtualized serial communications link. Alternatively, the virtualized connectivity means is a virtualized USB to USB bridge or a virtualized local bus such as a PCI bus.
In another embodiment, making the soft device available for use by the main virtual machine includes emulating a virtual network that connects the dedicated virtual machine to the main virtual machine and to any other virtual machine coupled to the VMM using a virtualized LAN. The communication between the virtual machines is then emulated by trapping all accesses to the virtualized LAN and reflecting them to the appropriate virtual machine.
In yet another embodiment, making the soft device available for use by the main virtual machine includes configuring the dedicated virtual machine to match an existing hardware device, such as a PCI card, a USB device or any other standard PC peripheral device, and emulating communication between the dedicated virtual machine and the main virtual machine using, respectively, a virtualized PCI bus, a virtualized USB connection, or a virtualized bus, connection or link appropriate to the device.
The above three embodiments will now be described in more detail in conjunction with
In one embodiment, the VMM 112 presents the dedicated virtual machine 608 to the main virtual machine 606 as an external fixed function hardware device (e.g., a “hard” or standard modem) by providing a virtualized serial port 404 (e.g., COM 1), trapping all accesses by the main virtual machine 606 to this virtualized serial port and re-directing them to the dedicated virtual machine 608. Similarly, the VMM 112 may trap the proper set of I/O writes by the dedicated virtual machine 608 and redirect these writes to the main virtual machine 606 as to present them as data from the serial port. In one embodiment, the dedicated virtual machine 608 executes reflection software (e.g., an application or device driver) 614 to link the soft device driver 618 and the virtualized serial port 404 together. For instance, the reflection software 614 may read from the virtualized serial port 404 and write to the soft device driver 618 and vice versa. In one embodiment, the dedicated virtual machine 608 is assigned an Interrupt Request (IRQ) for the main virtual machine 606. The VMM 112 then traps a predefined software instruction or a trap, fault, exception or software interrupt that occurs under predefined conditions in the dedicated virtual machine 608 and reflects each such instruction or occurrence of a trap fault, exception or software interrupt when the predefined conditions hold as an interrupt of the appropriate IRQ to the virtualized Programmable Interrupt Controller (PIC) of the main virtual machine 606.
In another embodiment, the VMM 112 presents the dedicated virtual machine 608 to the main virtual machine 606 as an internal fixed function hardware device by providing a virtualized USB to USB bridge 404, presenting the virtualized USB to USB bridge 404 to each virtual machine 606 and 608 as a USB “host controller” connected to a USB to USB bridge device, trapping all accesses by the main virtual machine 606 to this virtualized USB host controller 404 and re-directing them to the dedicated virtual machine 608. In addition, the VMM 112 traps accesses by the dedicated virtual machine 608 to the USB host controller 404 and redirects these accesses to the main virtual machine 606 as to present them as data from the USB host controller.
In yet another embodiment, the VMM 112 presents the dedicated virtual machine 608 to the main virtual machine 606 as an internal fixed function hardware device or a PCI device by providing a virtualized local bus 404 (e.g., a PCI bus), and trapping and redirecting all accesses to this virtualized local bus 404 in the manner described above.
Referring to
Referring to
The VMM 112 emulates communication between the two virtual machines by trapping I/O accesses by the dedicated virtual machine 658 to the virtualized PCI bus or virtualized USB connection 654 and redirecting them to the main virtual machine 655, and vice versa.
As illustrated in
As opposed to other OSes (e.g., Windows OSes), RTOS 666 does not require a change to a soft device driver each time the PC OS such as Windows is modified. Instead, the dedicated virtual machine 658 that closely matches the PCI card, USB or other PC peripheral device can execute some or all of the software of the original fixed function hardware device. With availability of on chip co-processors (e.g., a digital signal processor (DSP)), the virtual machine may make direct use of on chip co-processors to provide an extended Instruction Set Architecture (ISA) that closely matches the ISA of the processor(s) on the original PCI card. As result, the soft device software that executes on the host processor need not to be different from the software which executes on the original fixed function device, thereby simplifying porting and speed of development of soft devices.
The present invention provides the software vendors with an option of constructing soft devices by reconfiguring a dedicated virtual machine, rather than rewriting soft device driver software. For instance, both approaches can be analyzed and the most efficient approach can be chosen based on the costs involved. For complex conventional fixed function hardware devices multiple virtual machines can be configured, with each VM running the RTOS used by one or more of the processors of the conventional fixed function hardware device and the VMM emulating communication between the processors on the conventional fixed function hardware device using any of a variety of well known techniques including the communication techniques described above. For example, a complex fixed function hardware device may have a serial link between two of its processors.
Memory 730 can be a hard disk, a floppy disk, random access memory (RAM), read only memory (ROM), flash memory, or any other type of machine medium readable by processor 720. Memory 730 can store instructions for performing the execution of the various method embodiments of the present invention such as methods 300 and 500 (
It is to be understood that the above description is intended to be illustrative, and not restrictive. Many other embodiments will be apparent to those of skill in the art upon reading and understanding the above description. The scope of the invention should, therefore, be determined with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled.
Number | Name | Date | Kind |
---|---|---|---|
3699532 | Schaffer et al. | Oct 1972 | A |
3996449 | Attanasio et al. | Dec 1976 | A |
4037214 | Birney et al. | Jul 1977 | A |
4162536 | Morley | Jul 1979 | A |
4207609 | Luiz et al. | Jun 1980 | A |
4276594 | Morley | Jun 1981 | A |
4278837 | Best | Jul 1981 | A |
4307447 | Provanzano et al. | Dec 1981 | A |
4319233 | Matsuoka et al. | Mar 1982 | A |
4319323 | Ermolovich et al. | Mar 1982 | A |
4366537 | Heller et al. | Dec 1982 | A |
4403283 | Myntti et al. | Sep 1983 | A |
4419724 | Branigin et al. | Dec 1983 | A |
4430709 | Schleupen et al. | Feb 1984 | A |
4521852 | Guttag | Jun 1985 | A |
4621318 | Maeda | Nov 1986 | A |
4759064 | Chaum | Jul 1988 | A |
4795893 | Ugon | Jan 1989 | A |
4802084 | Ikegaya et al. | Jan 1989 | A |
4825052 | Chemin et al. | Apr 1989 | A |
4907270 | Hazard | Mar 1990 | A |
4907272 | Hazard | Mar 1990 | A |
4910774 | Barakat | Mar 1990 | A |
4975836 | Hirosawa et al. | Dec 1990 | A |
5007082 | Cummins | Apr 1991 | A |
5022077 | Bealkowski et al. | Jun 1991 | A |
5075842 | Lai | Dec 1991 | A |
5187802 | Inoue et al. | Feb 1993 | A |
5230069 | Brelsford et al. | Jul 1993 | A |
5237616 | Abraham et al. | Aug 1993 | A |
5255379 | Melo | Oct 1993 | A |
5287363 | Wolf et al. | Feb 1994 | A |
5293424 | Hotley et al. | Mar 1994 | A |
5295251 | Wakui et al. | Mar 1994 | A |
5361375 | Ogi | Nov 1994 | A |
5421006 | Jablon et al. | May 1995 | A |
5434999 | Goire et al. | Jul 1995 | A |
5442645 | Ugon et al. | Aug 1995 | A |
5455909 | Blomgren et al. | Oct 1995 | A |
5459867 | Adams et al. | Oct 1995 | A |
5459869 | Spilo | Oct 1995 | A |
5469557 | Salt et al. | Nov 1995 | A |
5473692 | Davis | Dec 1995 | A |
5479509 | Ugon | Dec 1995 | A |
5506975 | Onodera | Apr 1996 | A |
5528231 | Patarin | Jun 1996 | A |
5533126 | Hazard et al. | Jul 1996 | A |
5555385 | Osisek | Sep 1996 | A |
5555414 | Hough et al. | Sep 1996 | A |
5560013 | Scalzi et al. | Sep 1996 | A |
5564040 | Kubals | Oct 1996 | A |
5566323 | Ugon | Oct 1996 | A |
5568552 | Davis | Oct 1996 | A |
5574936 | Ryba et al. | Nov 1996 | A |
5582717 | Di Santo | Dec 1996 | A |
5604805 | Brands | Feb 1997 | A |
5606617 | Brands | Feb 1997 | A |
5615263 | Takahashi | Mar 1997 | A |
5633929 | Kaliski, Jr. | May 1997 | A |
5657445 | Pearce | Aug 1997 | A |
5668971 | Neufeld | Sep 1997 | A |
5684948 | Johnson et al. | Nov 1997 | A |
5706469 | Kobayashi | Jan 1998 | A |
5717903 | Bonola | Feb 1998 | A |
5720609 | Pfefferle | Feb 1998 | A |
5721222 | Bernstein et al. | Feb 1998 | A |
5729760 | Poisner | Mar 1998 | A |
5740178 | Jacks et al. | Apr 1998 | A |
5752046 | Oprescu et al. | May 1998 | A |
5764969 | Kahle et al. | Jun 1998 | A |
5796835 | Saada | Aug 1998 | A |
5796845 | Serikawa et al. | Aug 1998 | A |
5805712 | Davis | Sep 1998 | A |
5809546 | Greenstein et al. | Sep 1998 | A |
5825875 | Ugon | Oct 1998 | A |
5825880 | Sudia et al. | Oct 1998 | A |
5835594 | Albrecht et al. | Nov 1998 | A |
5844986 | Davis | Dec 1998 | A |
5867577 | Patarin | Feb 1999 | A |
5890189 | Nozue et al. | Mar 1999 | A |
5900606 | Rigal | May 1999 | A |
5901225 | Ireton et al. | May 1999 | A |
5903752 | Dingwall et al. | May 1999 | A |
5919257 | Trostle | Jul 1999 | A |
5935242 | Madany et al. | Aug 1999 | A |
5935247 | Pai et al. | Aug 1999 | A |
5937063 | Davis | Aug 1999 | A |
5944821 | Angelo | Aug 1999 | A |
5956408 | Arnold | Sep 1999 | A |
5970147 | Davis et al. | Oct 1999 | A |
5978475 | Schneier et al. | Nov 1999 | A |
5978481 | Ganesan et al. | Nov 1999 | A |
5987557 | Ebrahim | Nov 1999 | A |
6014745 | Ashe | Jan 2000 | A |
6035374 | Panwar et al. | Mar 2000 | A |
6044478 | Green | Mar 2000 | A |
6058478 | Davis | May 2000 | A |
6061794 | Angelo | May 2000 | A |
6088262 | Nasu | Jul 2000 | A |
6092095 | Maytal | Jul 2000 | A |
6093213 | Favor et al. | Jul 2000 | A |
6108644 | Goldschlag et al. | Aug 2000 | A |
6115816 | Davis | Sep 2000 | A |
6131166 | Wong-Isley | Oct 2000 | A |
6158546 | Hanson et al. | Dec 2000 | A |
6173417 | Merrill | Jan 2001 | B1 |
6175924 | Arnold | Jan 2001 | B1 |
6175925 | Nardone et al. | Jan 2001 | B1 |
6178509 | Nardone et al. | Jan 2001 | B1 |
6188257 | Buer | Feb 2001 | B1 |
6199152 | Kelly et al. | Mar 2001 | B1 |
6205550 | Nardone et al. | Mar 2001 | B1 |
6212635 | Reardon | Apr 2001 | B1 |
6222923 | Schwenk | Apr 2001 | B1 |
6252650 | Nakaumra | Jun 2001 | B1 |
6269392 | Cotichini et al. | Jul 2001 | B1 |
6275933 | Fine et al. | Aug 2001 | B1 |
6282650 | Davis | Aug 2001 | B1 |
6282651 | Ashe | Aug 2001 | B1 |
6282657 | Kaplan et al. | Aug 2001 | B1 |
6308270 | Guthery et al. | Oct 2001 | B1 |
6327652 | England et al. | Dec 2001 | B1 |
6330670 | England et al. | Dec 2001 | B1 |
6357004 | Davis | Mar 2002 | B1 |
6363485 | Adams | Mar 2002 | B1 |
6374286 | Gee et al. | Apr 2002 | B1 |
6378068 | Foster | Apr 2002 | B1 |
6378072 | Collins et al. | Apr 2002 | B1 |
6389537 | Davis et al. | May 2002 | B1 |
6397379 | Yates, Jr. et al. | May 2002 | B1 |
6412035 | Webber | Jun 2002 | B1 |
6421702 | Gulick | Jul 2002 | B1 |
6435416 | Slassi | Aug 2002 | B1 |
6445797 | McGough et al. | Sep 2002 | B1 |
6463535 | Drews et al. | Oct 2002 | B1 |
6463537 | Tello | Oct 2002 | B1 |
6496847 | Bugnion et al. | Dec 2002 | B1 |
6507904 | Ellison et al. | Jan 2003 | B1 |
6529909 | Bowman-Amuah | Mar 2003 | B1 |
6535988 | Poisner | Mar 2003 | B1 |
6557104 | Vu et al. | Apr 2003 | B2 |
6560627 | McDonald et al. | May 2003 | B1 |
6609199 | DeTreville | Aug 2003 | B1 |
6615278 | Curtis | Sep 2003 | B1 |
6629178 | Smith | Sep 2003 | B1 |
6633963 | Ellison et al. | Oct 2003 | B1 |
6633981 | Davis | Oct 2003 | B1 |
6651171 | England et al. | Nov 2003 | B1 |
6678825 | Ellison et al. | Jan 2004 | B1 |
6684326 | Cromer et al. | Jan 2004 | B1 |
6789156 | Waldspurger | Sep 2004 | B1 |
6795966 | Lim et al. | Sep 2004 | B1 |
6934269 | Hasha et al. | Aug 2005 | B1 |
20010027511 | Wakabayashi et al. | Oct 2001 | A1 |
20010037450 | Metlitski et al. | Nov 2001 | A1 |
20020007456 | Peinado et al. | Jan 2002 | A1 |
20020023032 | Pearson et al. | Feb 2002 | A1 |
20020147916 | Strongin et al. | Oct 2002 | A1 |
20020166061 | Falik et al. | Nov 2002 | A1 |
20020169717 | Challener | Nov 2002 | A1 |
20030018892 | Tello | Jan 2003 | A1 |
20030074548 | Cromer et al. | Apr 2003 | A1 |
20030115453 | Grawrock | Jun 2003 | A1 |
20030126442 | Glew et al. | Jul 2003 | A1 |
20030126453 | Glew et al. | Jul 2003 | A1 |
20030159056 | Cromer et al. | Aug 2003 | A1 |
20030188179 | Challener et al. | Oct 2003 | A1 |
20030196085 | Lampson et al. | Oct 2003 | A1 |
20040117539 | Bennett et al. | Jun 2004 | A1 |
20050198632 | Lantz et al. | Sep 2005 | A1 |
Number | Date | Country |
---|---|---|
0473913 | Mar 1992 | EP |
0600112 | Jun 1994 | EP |
0602867 | Jun 1994 | EP |
0892521 | Jan 1999 | EP |
0930567 | Jul 1999 | EP |
0961193 | Dec 1999 | EP |
0965902 | Dec 1999 | EP |
1055989 | Nov 2000 | EP |
1056014 | Nov 2000 | EP |
1085396 | Mar 2001 | EP |
1146715 | Oct 2001 | EP |
1209563 | May 2002 | EP |
1271277 | Jan 2003 | EP |
WO9524696 | Sep 1995 | WO |
WO9812620 | Mar 1998 | WO |
WO9834365 | Aug 1998 | WO |
WO9844402 | Oct 1998 | WO |
WO9905600 | Feb 1999 | WO |
WO9909482 | Feb 1999 | WO |
WO9918511 | Apr 1999 | WO |
WO9957863 | Nov 1999 | WO |
WO9965579 | Dec 1999 | WO |
WO0021238 | Apr 2000 | WO |
WO 0062232 | Oct 2000 | WO |
WO0163994 | Aug 2001 | WO |
WO0201794 | Jan 2002 | WO |
WO02060121 | Aug 2002 | WO |
WO03058412 | Jul 2003 | WO |
Number | Date | Country | |
---|---|---|---|
20020143842 A1 | Oct 2002 | US |