Refresh management of memory modules

Abstract
One embodiment sets forth an interface circuit configured to manage refresh command sequences that includes a system interface adapted to receive a refresh command from a memory controller, clock frequency detection circuitry configured to determine the timing for issuing staggered refresh commands to two or more memory devices coupled to the interface circuit based on the refresh command received from the memory controller, and at least two refresh command sequence outputs configured to generate the staggered refresh commands for the two or more memory devices.
Description
BACKGROUND OF THE INVENTION

1. Field of the Invention


Embodiments of the present invention generally relate to memory modules and, more specifically, to methods and apparatus for refresh management of memory modules.


2. Description of the Related Art


The storage capacity of memory systems is increasing rapidly due to various trends in computing, such as the introduction of 64-bit processors, multi-core processors, and advanced operating systems. Such memory systems may include one or more memory devices, such as, for example, dynamic random access memory (DRAM) devices. The cells of a typical DRAM device can retain data for a time period ranging from several seconds to tens of seconds, but to ensure that the data is properly retained and not lost, DRAM manufacturers usually specify a very low threshold for instituting a refresh operation. The specification for most modern memory systems containing DRAM devices is that the cells of the DRAM devices are refreshed once every 64 milliseconds. This means that each cell in a given DRAM device must be read out to the sense amplifier and then written back into the DRAM device at full signal strength once every 64 milliseconds. Furthermore, for some DRAM devices, to account for the effect of higher signal loss rate at higher temperature, the refresh rate is doubled when the device is operating above a standard temperature, typically above 85° C.


To simplify the task of ensuring that all DRAM cells are properly refreshed, most DRAM devices, including double data rate (DDR) and DDR2 synchronous DRAM (SDRAM) devices, have an internal refresh row address register that keeps track of the row identification (ID) of the last refreshed row. Typically, a memory controller sends a single refresh command to the DRAM device. Subsequently, the DRAM device increments the row ID in the refresh row address register and executes a sequence of standard steps (typically referred to a “row cycle”) to refresh the data contained in DRAM cells of all rows with the appropriate row ID's in all of the banks in the DRAM device.


With the advent of higher capacity DRAM devices, there are more cells to refresh. Thus, to properly refresh all DRAM cells in a higher capacity DRAM device, either the refresh operations need to be performed more frequently or more cells need to be refreshed with each refresh command. To simplify memory controller design, the choice made by DRAM device manufacturers and memory controller designers is to keep the frequency of refresh operations the same, but refresh more DRAM cells for each refresh operation for the higher capacity DRAM devices. However, one issue associated with the action of refreshing more DRAM devices for each refresh operation in the higher capacity DRAM devices is that larger electrical currents may be drawn by the higher capacity DRAM devices for each refresh operation.


As the foregoing illustrates, what is needed in the art are new techniques for refreshing multiple memory devices in a memory system. In particular, higher capacity DRAM devices that must refresh a large number of DRAM cells for each refresh command.


SUMMARY OF THE INVENTION

One embodiment sets forth an interface circuit configured to manage refresh command sequences. The interface circuit includes a system interface adapted to receive a refresh command from a memory controller, clock frequency detection circuitry configured to determine the timing for issuing staggered refresh commands to two or more memory devices coupled to the interface circuit based on the refresh command received from the memory controller, and at least two refresh command sequence outputs configured to generate the staggered refresh commands for the two or more memory devices.





BRIEF DESCRIPTION OF THE DRAWINGS

So that the manner in which the above recited features can be understood in detail, a more particular description of the invention, briefly summarized above, may be had by reference to embodiments, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings illustrate only typical embodiments of this invention and are therefore not to be considered limiting of its scope, for the invention may admit to other equally effective embodiments.



FIG. 1A illustrates a multiple memory device system, according to one embodiment;



FIG. 1B illustrates a memory stack, according to one embodiment;



FIG. 1C illustrates a multiple memory device system, according to one embodiment that includes both an intelligent register and a intelligent buffer;



FIG. 2 illustrates a multiple memory device system, according to another embodiment;



FIG. 3 illustrates an idealized current draw as a function of time for a refresh cycle of a single memory device that executes two internal refresh cycles for each external refresh command, according to one embodiment;



FIG. 4A illustrates current draw as a function of time for two refresh cycles, started independently and staggered by a time period of half of the period of a single refresh cycle, according to another embodiment;



FIG. 4B illustrates voltage droop as a function of a stagger offset for two refresh cycles, according to one embodiment;



FIG. 5 illustrates the start and finish times of eight independent refresh cycles, according to one embodiment;



FIG. 6 illustrates a configuration of eight memory devices refreshed by two independently controlled refresh cycles starting at times tST1 and tST2, respectively, according to one embodiment;



FIG. 7 illustrates a configuration of eight memory devices refreshed by four independently controlled refresh cycles starting at times tST1, tST2, tST3 and tST4, respectively, according to another embodiment;



FIG. 8 illustrates a configuration of sixteen memory devices refreshed by eight independently controlled refresh cycles tST1, tST2, tST3 and tST4, tST5, tST6, tST7 and tST8, respectively, according to one embodiment;



FIG. 9 illustrates the octal configuration of the memory devices of FIG. 8 implemented within the multiple memory device system of FIG. 1A, according to one embodiment;



FIG. 10A is a flowchart of method steps for configuring, calculating, and generating the timing and assertion of two or more refresh commands, according to one embodiment;



FIG. 10B depicts a series of operations for calculating refresh stagger times for a given configuration.



FIG. 11 is a flowchart of method steps for configuring, calculating, and generating the timing and assertion of two or more refresh commands continuously and asynchronously, according to one embodiment;



FIG. 12 illustrates the interface circuit of FIG. 1A with refresh command outputs adapted to connect to a plurality of memory devices, such as the memory devices of FIG. 1A, according to one embodiment;



FIG. 13 is an exemplary illustration of a 72-bit ECC DIMM based upon industry-standard DRAM devices arranged vertically into stacks and horizontally into an array of stacks, according to one embodiment; and



FIG. 14 is a conceptual illustration of a computer platform including an interface circuit.





DETAILED DESCRIPTION

Illustrative information will now be set forth regarding various optional architectures and features of different embodiments with which the foregoing frameworks may or may not be implemented, per the desires of the user. It should be strongly noted that the following information is set forth for illustrative purposes and should not be construed as limiting in any manner. Any of the following features may be optionally incorporated with or without the other features described.



FIG. 1A illustrates a multiple memory device system 100, according to one embodiment. As shown, the multiple memory device system 100 includes, without limitation, a system device 106 coupled to an interface circuit 102, which is, in turn, coupled to a plurality of physical memory devices 104A-N. The memory devices 104A-N may be any type of memory devices. For example, in various embodiments, one or more of the memory devices 104A, 104B, 104N may include a monolithic memory device. For instance, such monolithic memory device may take the form of dynamic random access memory (DRAM). Such DRAM may take any form including, but not limited to synchronous (SDRAM), double data rate synchronous (DDR DRAM, DDR2 DRAM, DDR3 DRAM, etc.), quad data rate (QDR DRAM), direct RAMBUS (DRDRAM), fast page mode (FPM DRAM), video (VDRAM), extended data out (EDO DRAM), burst EDO (BEDO DRAM), multibank (MDRAM), synchronous graphics (SGRAM), and/or any other type of DRAM. Of course, one or more of the memory devices 104A, 104B, 104N may include other types of memory such as magnetic random access memory (MRAM), intelligent random access memory (IRAM), distributed network architecture (DNA) memory, window random access memory (WRAM), flash memory (e.g. NAND, NOR, or others, etc.), pseudostatic random access memory (PSRAM), wetware memory, and/or any other type of memory device that meets the above definition. In some embodiments, each of the memory devices 104A-N is a separate memory chip. For example, each may be a DDR2 DRAM.


In some embodiments, the any of the memory devices 104A-N may itself be a group of memory devices, or may be a group in the physical orientation of a stack. For example, FIG. 1B shows a memory device 130 which is comprised of a group of DRAM memory devices 132A-132N all electrically interconnected to each other and an intelligent buffer 133. In alternative embodiments, the intelligent buffer 133 may include the functionality of interface circuit 102. Further, the memory device 130 may be included in a DIMM (dual in-line memory module) or other type of memory module.


The memory devices 1032A-N may be any type of memory devices. Furthermore, in some embodiments, the memory devices 104A-N may be symmetrical, meaning each has the same capacity, type, speed, etc., while in other embodiments they may be asymmetrical. For ease of illustration only, three such memory devices are shown, 104A, 104B, and 104N, but actual embodiments may use any plural number of memory devices. As will be discussed below, the memory devices 104A-N may optionally be coupled to a memory module (not shown), such as a DIMM.


The system device 106 may be any type of system capable of requesting and/or initiating a process that results in an access of the memory devices 104A-N. The system device 106 may include a memory controller (not shown) through which the system device 106 accesses the memory devices 104A-N.


The interface circuit 102 may include any circuit or logic capable of directly or indirectly communicating with the memory devices 104A-N, such as, for example, an interface circuit advanced memory buffer (AMB) chip or the like. The interface circuit 102 interfaces a plurality of signals 108 between the system device 106 and the memory devices 104A-N. The signals 108 may include, for example, data signals, address signals, control signals, clock signals, and the like. In some embodiments, all of the signals 108 communicated between the system device 106 and the memory devices 104A-N are communicated via the interface circuit 102. In other embodiments, some other signals, shown as signals 110, are communicated directly between the system device 106 (or some component thereof, such as a memory controller or an AMB) and the memory devices 104A-N, without passing through the interface circuit 102. In some embodiments, the majority of signals are communicated via the interface circuit 102, such that L>M.


As will be explained in greater detail below, the interface circuit 102 presents to the system device 106 an interface to emulate memory devices which differ in some aspect from the physical memory devices 104A-N that are actually present within system 100. The terms “emulating,” “emulated,” “emulation,” and the like are used herein to signify any type of emulation, simulation, disguising, transforming, converting, and the like, that results in at least one characteristic of the memory devices 104A-N appearing to the system device 106 to be different than the actual, physical characteristic of the memory devices 104A-N. For example, the interface circuit 102 may tell the system device 106 that the number of emulated memory devices is different than the actual number of physical memory devices 104A-N. In various embodiments, the emulated characteristic may be electrical in nature, physical in nature, logical in nature, pertaining to a protocol, etc. An example of an emulated electrical characteristic might be a signal or a voltage level. An example of an emulated physical characteristic might be a number of pins or wires, a number of signals, or a memory capacity. An example of an emulated protocol characteristic might be timing, or a specific protocol such as DDR3.


In the case of an emulated signal, such signal may be an address signal, a data signal, or a control signal associated with an activate operation, pre-charge operation, write operation, mode register set operation, refresh operation, etc. The interface circuit 102 may emulate the number of signals, type of signals, duration of signal assertion, and so forth. In addition, the interface circuit 102 may combine multiple signals to emulate another signal.


The interface circuit 102 may present to the system device 106 an emulated interface, for example, a DDR3 memory device, while the physical memory devices 104A-N are, in fact, DDR2 memory devices. The interface circuit 102 may emulate an interface to one version of a protocol, such as DDR2 with 3-3-3 latency timing, while the physical memory chips 104A-N are built to another version of the protocol, such as DDR with 5-5-5 latency timing. The interface circuit 102 may emulate an interface to a memory having a first capacity that is different than the actual combined capacity of the physical memory devices 104A-N.


An emulated timing signal may relate to a chip enable or other refresh signal. Alternatively, an emulated timing signal may relate to the latency of, for example, a column address strobe latency (tCAS), a row address to column address latency (tRCD), a row precharge latency (tRP), an activate to precharge latency (tRAS), and so forth.


The interface circuit 102 may be operable to receive a signal 107 from the system device 106 and communicate the signal 107 to one or more of the memory devices 104A-N after a delay (which may be hidden from the system device 106). In one embodiment, such a delay may be fixed, while in other embodiments, the delay may be variable. If variable, the delay may depend on e.g. a function of the current signal or a previous signal, a combination of signals, or the like. The delay may include a cumulative delay associated with any one or more of the signals. The delay may result in a time shift of the signal 107 forward or backward in time with respect to other signals. Different delays may be applied to different signals. The interface circuit 102 may similarly be operable to receive the signal 108 from one of the memory devices 104A-N and communicate the signal 108 to the system device 106 after a delay.


The interface circuit 102 may take the form of, or incorporate, or be incorporated into, a register, an AMB, a buffer, or the like, and may comply with JEDEC standards, and may have forwarding, storing, and/or buffering capabilities.


In one embodiment, the interface circuit 102 may perform multiple operations when a single operation is commanded by the system device 106, where the timing and sequence of the multiple operations are performed by the interface circuit 102 to the one or more of the memory devices without the knowledge of the system device 106. One such operation is a refresh operation. In the situation where the refresh operations are issued simultaneously, a large parallel load is presented to the power supply. To alleviate this load, multiple refresh operations could be staggered in time, thus reducing instantaneous load on the power supply. In various embodiments, the multiple memory device system 100 shown in FIG. 1A may include multiple memory devices 104A-N capable of being independently refreshed by the interface circuit 102. The interface circuit 102 may identify one or more of the memory devices 104A-N which are capable of being refreshed independently, and perform the refresh operation on those memory devices. In yet another embodiment, the multiple memory device system 100 shown in FIG. 1A includes the memory devices 104A-N which may be physically oriented in a stack, with each of the memory devices 104A-N capable to read/write a single bit. For example, to implement an eight-bit wide memory in a stack, eight one-bit wide memory devices 104A-N could be arranged in a stack of eight memory devices. In such a case, it may be desirable to control the refresh cycles of each of the memory devices 104A-N independently.


The interface circuit 102 may include one or more devices which together perform the emulation and related operations. In various embodiments, the interface circuit may be coupled or packaged with the memory devices 104A-N, or with the system device 106 or a component thereof, or separately. In one embodiment, the memory devices and the interface circuit are coupled to a DIMM. In alternative embodiments, the memory devices 104 and/or the interface circuit 102 may be coupled to a motherboard or some other circuit board within a computing device.



FIG. 1C illustrates a multiple memory device system, according to one embodiment. As shown, the multiple memory device system includes, without limitation, a host system device coupled to an host interface circuit, also known as an intelligent register circuit 102, which is, in turn, coupled to a plurality of intelligent buffer circuits 107A-107D, memory devices which is, in turn, coupled to a plurality of physical memory devices 104A-N.



FIG. 2 illustrates a multiple memory device system 200, according to another embodiment. As shown, the multiple memory device system 200 includes, without limitation, a system device 204 which communicates address, control, and clock signals 208 and data signals 210 with a memory subsystem 201. The memory subsystem 201 includes an interface circuit 202, which presents the system device 204 with an emulated interface to emulated memory, and a plurality of physical memory devices, which are shown as DRAM 06A-D. In one embodiment, the DRAM devices 206A-D are stacked, and the interface circuit 202 is electrically disposed between the DRAM devices 206A-D and the system device 204. Although the embodiments described here show the stack consisting of multiple DRAM circuits, a stack may refer to any collection of memory devices (e.g., DRAM circuits, flash memory devices, or combinations of memory device technologies, etc.).


The interface circuit 202 may buffer signals between the system device 204 and the DRAM devices 206A-D, both electrically and logically. For example, the interface circuit 202 may present to the system device 204 an emulated interface to present the memory as though the memory comprised a smaller number of larger capacity DRAM devices, although, in actuality, the memory subsystem 201 includes a larger number of smaller capacity DRAM devices 206A-D. In another embodiment, the interface circuit 202 presents to the system device 204 an emulated interface to present the memory as though the memory were a smaller (or larger) number of larger capacity DRAM devices having more configured (or fewer configured) ranks, although, in actuality, the physical memory is configured to present a specified number of ranks. Although the FIG. 2 shows four DRAM devices 206A-D, this is done for ease of illustration only. In other embodiments, other numbers of DRAM devices may be used.


As also shown in FIG. 2, the interface circuit 202 is coupled to send address, control, and clock signals 208 to the DRAM devices 206A-D via one or more buses. In the embodiment shown, each of the DRAM devices 206A-D has its own, dedicated data path for sending and receiving data signals 210 to and from the interface circuit 202. Also, in the embodiment shown, the DRAM devices 206A-D are physically arranged on a single side of the interface circuit 202.


In one embodiment, the interface circuit 202 may be a part of the stack of the DRAM devices 206A-D. In other embodiments, the interface circuit 202 may be the bottom-most chip in the stack or otherwise disposed in or on the stack, or may be separate from the stack.


In some embodiments, the interface circuit 202 may perform operations whose relative timing and ordering are executed without the knowledge of the system device 204. One such operation is a refresh operation. The interface circuit 202 may identify one or more of the DRAM devices 206A-D that should be refreshed concurrently when a single refresh operation is issued by the system device 204 and perform the refresh operation on those DRAM devices. The methods and apparatuses capable of performing refresh operations on a plurality of memory devices are described later herein.


In general, it is desirable to manage the application of refresh operations such that the current draw and voltage levels remain within acceptable limits. Such limits may depend on the number and type of the memory devices being refreshed, physical design characteristics, and the characteristics of the system device (e.g., system devices 106, 204.)



FIG. 3 illustrates an idealized current draw as a function of time for a refresh cycle of a single memory device that executes two internal refresh cycles for each external refresh command, according to one embodiment. The single memory device may be, for example, one of the memory devices 104A-N described in FIG. 1A or one of the DRAM devices described in FIG. 2.



FIG. 3 also shows several time periods, in particular, tRAS, and tRC. There is relatively less current draw during the 35 ns period between 40 ns and 75 ns as compared with the 35 ns period between 5 ns and 40 ns. Thus, in the specific case of managing refresh cycles independently for two memory devices (or independently for two banks), the instantaneous current draw can be minimized by staggering the beginning of the refresh cycles of the individual memory devices. In such an embodiment, the peak current draw for two independent, staggered refresh cycles of the two memory devices is reduced by starting the second refresh cycle at about 30 ns. However, in practical (non-idealized) systems, the optimal start time for a second or any subsequent refresh cycle may be a function of time as well as a function of many variables other than time.



FIG. 4A illustrates current draw as a function of time for two refresh cycles 410 and 420, started independently and staggered by a time period of half of the period of a single refresh cycle.



FIG. 4B illustrates voltage droop on the VDD voltage supply from the nominal voltage of 1.8 volt as a function of a stagger offset for two refresh cycles, according to one embodiment. “Stagger offset” is defined herein as the difference between the starting times of the first and second refresh cycles.


A curve of the voltage droop on the VDD voltage supply from the nominal voltage of 1.8 volt as a function of the stagger offset as shown in FIG. 4B can be generated from simulation models of the interconnect components and the interconnect itself, or can be dynamically calculated from measurements. Three distinct regions become evident in this curve:

    • A: A local minimum in the voltage droop on the VDD voltage supply from the nominal voltage of 1.8 volt results when the refreshes are staggered by an offset such that the increasing current transient from one refresh event counters the decreasing current transient from another refresh event. The positive slew rate from one refresh produces destructive interference with the negative slew rate from another refresh, thus reducing the effective load.
    • B: The best case, namely when the droop is minimum, occurs when the current draw profiles have almost zero overlap.
    • C: Once the waveforms are separated in time so that the refresh cycles do not overlap additional stagger spacing does not offer significant additional relief to the power delivery system. Consequently, thereafter, the level of voltage droop on the VDD supply voltage remains nearly constant.


As can be seen from a simple inspection, the optimal time to begin the second refresh cycle is at the point of minimum voltage droop (highest voltage), point B, which in this example is at about 110 ns. Persons skilled in the art will understand that the values used in the calculations resulting in the curve of FIG. 4B are for illustrative purposes only, and that a large number of other curves with different points of minimum voltage droop are possible, depending on the characteristics of the memory device, and the electrical characteristics of the physical design of the memory subsystem.



FIG. 5 illustrates the start and finish times of eight independent refresh cycles, according to one embodiment of the present application. The optimization of the start times of successive independent refresh cycles may be accomplished by circuit simulation (e.g., SPICE™ or H-SPICE as sold by Cadence Design Systems) or with logic-oriented timing analysis tools (e.g. Verilog™ as sold by Cadence Design Systems). Alternatively, the start times of the independent refresh cycles may be optimized dynamically through implementation of a dynamic parameter extraction capability. For example, the interface circuit 202 may contain a clock frequency detection circuit that the interface circuit 202 can use to determine the optimal timing for the independent refresh cycles. In the example of FIG. 5, the first independently controlled duple of cycles 510 and 511 begins at time zero. The next independently controlled duple of cycles, cycles 520 and 521, begins approximately at time 25 nS, and the next duple at approximately 37 nSec. In this example, current draw is reduced inasmuch as each next duple of refresh cycles does not begin until such time as the peak current draw of the previous duple has passed. This simplified regime is for illustrative purposes, and one skilled in the art will recognize that other regimes would emerge depending on the characteristic shape of the current draw during a refresh cycle.


In some embodiments, multiple instances of a memory device may be organized to form memory words that are longer than a single instance of the aforementioned memory device. In such a case, it may be convenient to control the independent refresh cycles of the multiple instances of the memory device that form such a memory word with multiple independently controlled memory refresh commands, with a separate refresh command sequence corresponding to each different instance of the memory device.



FIG. 6 illustrates a configuration of eight memory devices refreshed by two independently controlled refresh cycles starting at times tST1 and tST2, respectively, according to one embodiment. The motivation for the refresh schedule is to minimize voltage droop while completing all refresh operations with the allotted time window, as per JEDEC specifications.


As shown, the eight memory devices are organized into two DRAM stacks, and each DRAM stack is driven by two independently controllable refresh command sequences. The memory devices labeled R0B01[7:4], R0B01[3:0], R1B45[7:4], and R1B45[3:0] are refreshed by refresh cycle tST1, while the remaining memory devices are refreshed by the refresh cycle tST2.



FIG. 7 illustrates a configuration of eight memory devices refreshed by four independently controlled refresh cycles starting at tST1, tST2, tST3 and tST4, respectively, according to another embodiment. Such a configuration is referred to herein as a “quad configuration,” and the stagger offsets in this configuration are referred to as “quad-stagger.” The quad-stagger allows for four independent stagger times distributed over eight devices, thus spreading out the total current draw and lowering large slews that may result from simultaneous activation of refresh cycles in all eight DRAM devices.



FIG. 8 illustrates a configuration of sixteen memory devices refreshed by eight independently controlled refresh cycles, according to yet another embodiment. Such a configuration is referred to herein as an “octal configuration.” The motivation for this stagger schedule is the same as for the previously mentioned dual and quad configurations, however in the octal configuration it is not possible to complete all refresh operation on all eight memories within the window unless the operations are bunched up more closely than in the quad or dual cases.



FIG. 9 illustrates the octal configuration of the memory devices of FIG. 8 implemented within the multiple memory device system 100 of FIG. 1A, according to one embodiment. As previously described, the system device 106 is connected to the interface circuit 102, which, in turn, is connected to the memory devices 104A-N. As shown in FIG. 9, there are four independently controllable refresh command sequence outputs of block 930. Outputs of R0 are independently controllable refresh command sequences. Also, outputs of R1 are independently controllable refresh command sequences. The blocks 930, 940, implement their respective functionalities using a combination of logic gates, transistors, finite state machines, programmable logic or any technique capable of operating on or delaying logic or analog signals.


The techniques and exemplary embodiments for how to independently control refresh command sequences to a plurality of memory devices using an interface circuit have now been disclosed. The following describes various techniques for calculating the timing of assertions of the refresh command sequences.



FIG. 10A is a flowchart of method steps for configuring, calculating, and generating the timing and assertion of two or more refresh command sequences, according to one embodiment. Although the method is described with respect to the system of FIG. 1A, persons skilled in the art will understand that any system configured to perform the method steps, in any order, is within the scope of the claims. As shown in FIG. 10A, the method includes the steps of analyzing the connectivity of the refresh command sequences between the memory devices 104 A-N and the interface circuit 102 outputs, calculating the timing of each of the independently controlled refresh command sequences, and asserting each of the refresh command sequences at the calculated time. In exemplary embodiments, one or more of the steps of FIG. 10A are performed in the logic embedded in the interface circuit 102. In another embodiment one or more of the steps of FIG. 10A are performed in the logic embedded in the interface circuit 102 while any remaining steps of FIG. 10A are performed in the intelligent buffer 133.


In one embodiment, analyzing the connectivity of the refresh command sequences between the memory devices 104A-N and the interface circuit 102 outputs is performed statically, prior to applying power to the system device 106. Any number of characteristics of the system device 106, motherboard, trace-length, capacitive loading, memory type, interface circuit output buffers, or other physical design characteristics, may be used in an analysis or simulation in order to analyze or optimize the timing of the plurality of independently controllable refresh command sequences.


In another embodiment, analyzing the connectivity of the refresh command sequences between the memory devices 104A-N and the interface circuit 102 outputs is performed dynamically, after applying power to the system device 106. Any number of characteristics of the system device 106, motherboard, trace-length, capacitive loading, memory type, interface circuit output buffers, or other physical design characteristics, may be used in an analysis or simulation in order to analyze or optimize the timing of the plurality of independently controllable refresh command sequences.


In some embodiments of the multiple memory device system of FIG. 1A, the physical design can have a significant impact on the current draw, voltage droop, and staggering of the multiple independently controlled refresh command sequences. A designer of a DIMM, motherboard, or system would seek to minimize spikes in current draw, the resulting voltage droop on the VDD voltage supply, and still meet the required refresh cycle time. Some rules and guidelines for the physical design of the trace lengths and capacitance for the signals 108, and for the packaging of the memory circuits 104A-104N as related to refresh staggering include:

    • Reduce the inductance between intelligent buffer 133 and each memory device 132A-N, between intelligent buffer 133 and the intelligent register 102.
    • Increase decoupling capacitance between VDD and VSS at all levels of the PDS: PCB, BGA, substrate, wirebond, RDL and die.
    • Separate the spikes in current draw by staggering the refresh times between multiple memory devices.


In another embodiment, configuring the connectivity of the refresh command sequences between the memory devices 104A-N and the interface circuit 102 outputs is performed periodically at times after application of power to the system device 106. Dynamic configuration uses a measurement unit (e.g., element 1202 of FIG. 12) that is capable of performing a series of analog and logic tests on one or more of various pins of the interface circuit 102 such that actual characteristics of the pin is measured and stored for use in refresh scheduling calculations. Examples of such characteristics include, but are not limited to timing of response at first detected voltage change, timing of response where detected voltage change crosses the logic1/logic0 threshold value, timing of response at peak detected voltage change, duration and amplitude of response ring, operating frequency of the interface circuit and operating frequency of the DRAM devices etc.



FIG. 10B shows steps of a method to be performed periodically at some time after application of power to the system device 106. The steps include determining the connectivity characteristics of the affecting communication of the refresh commands, determining operating conditions, including one or more temperatures, determining the configuration of the memory (e.g. size, number of ranks, memory word organization, etc.), calculating the refresh timing for initialization, and calculating refresh timing for the operation phase. Similarly to the method of 10A, the method of 10B may be applied repeatedly, beginning at any step, in an autonomous fashion or based on any technically feasible event, such as a power-on reset event or the receipt of a time-multiplexed or other signal, a logical combination of signals, a combination of signals and stored state, a command or a packet from any component of the host system, including the memory controller.


In embodiments where one or more temperatures are measured, the calculation of the refresh timing considers not only the measured temperatures, but also the manufacturer's specifications of the DRAMs



FIG. 11 is a flowchart of method steps for analysing, calculating, and generating the timing and assertion of two or more refresh command sequences continuously and asynchronously, according to one embodiment. Although the method is described with respect to the systems of FIGS. 1A, 1B, 1C, and FIG. 12, persons skilled in the art will understand that any system configured to implement the method steps in any order, is within the scope of the claims. As shown in FIG. 11, the method includes the steps of continuously and asynchronously analysing the connectivity affecting the assertion of refresh commands between the memory devices 104A-N and the interface circuit 102 outputs, continuously and asynchronously calculating the timing of each of the independently controlled refresh command sequences, and continuously and asynchronously scheduling the assertion of each of the refresh command sequences at the calculated time. In one embodiment, the method steps of FIG. 11 may be implementation in hardware. Those skilled in the art will recognize that physical characteristics such as capacitance, resistance, inductance and temperature may vary slightly with time and during operation, and such variations may affect scheduling of the refresh commands. Moreover, during operation, the assertion of refresh commands is intended to continue on a schedule that is not in violation of any schedule required by the DRAM manufacturer, therefore the step of calculating timing of refresh command sequences and may operate concurrently with the step of asserting refresh command sequences.



FIG. 12 illustrates the interface circuit 102 of FIG. 1A with refresh command sequence outputs 1201 adapted to connect to a plurality of memory devices, such as the memory devices 104A-N of FIG. 1A, according to one embodiment. In this embodiment, each of a measurement unit 1202, a calculation unit 1204, and a scheduler 1206 is configured to operate continuously and asynchronously.


The measurement unit 1202 is configured to generate signals 1205 and to sample analog values of inputs 1203 either autonomously at some time after power-on or upon receiving a command from the system device 106. The measurement unit 1202 also is operable to determine the configuration of the memory devices 104A-N (not shown). The configuration determination and measurements are communicated to the calculation unit 1204. The calculation unit 1204 analyses the measurements received from the measurement unit 1202 and calculates the optimized timing for staggering the refresh command sequences, as previously described herein.


Understanding the use of the disclosed techniques for managing refresh commands, there are many apparent embodiments based upon industry-standard configurations of DRAM devices.



FIG. 13 is an exemplary illustration of a 72-bit ECC (error-correcting code) DIMM based upon industry-standard DRAM devices 1310 arranged vertically into stacks 1320 and horizontally into an array of stacks, according to one embodiment. As shown, the stacks of DRAM devices 1320 are organized into an array of stacks of sixteen 4-bit wide DRAM devices 1310 resulting in a 72-bit wide DIMM. Persons skilled in the art will understand that many configurations of the ECC DIMM of FIG. 13 may be possible and envisioned. A few of the exemplary configurations are further described in the following paragraphs.


In another embodiment, the configuration contains N DRAM devices, each of capacity M that—in concert with the interface circuit(s) 1470—emulates one DRAM devices, each of capacity N*M. In a system with a system device 1420 designed to interface with a DRAM device of capacity N*M, the system device will allow for a longer refresh cycle time than it would allow to each DRAM device of capacity M. In this configuration, when a refresh command is issued by the system device to the interface circuit, the interface circuit will stagger N numbers of refresh cycles to the N numbers of DRAM devices. In one optional feature, the interface circuit may use a user-programmable setting or a self calibrated frequency detection circuit to compute the optimal stagger spacing between each of the N numbers of refresh cycles to each of the N numbers of DRAM devices. The result of the computation is minimized voltage droop on the power delivery network and functional correctness in that the entire sequence of N staggered refresh events are completed within the refresh cycle time expected by the system device. For example, a configuration may contain 4 DRAM devices, each 1 gigabit in capacity that an interface circuit may use to emulate one DRAM device that is 4 gigabit in capacity. In a JEDEC compliant DDR2 memory system, the defined refresh cycle time for the 4 gigabit device is 327.5 nanoseconds, and the defined refresh cycle time for the 1 gigabit device is 127.5 nanoseconds. In this specific example, the interface circuit may stagger refresh commands to each of the 1 gigabit DRAM devices with spacing that is carefully selected based on the operating characteristics of the system, such as temperature, frequency, and voltage levels, while still ensuring that that the entire sequence is complete within the 327.5 ns expected by the memory controller.


In another embodiment, the configuration contains 2*N DRAM devices, each of capacity M that—in concert with the interface circuit(s) 1470—emulates two DRAM devices, each of capacity N*M. In a system with a system device 1420 designed to interface with a DRAM device of capacity N*M, the system device will allow for a longer refresh cycle time than it would allow to each DRAM device of capacity M. In this configuration, when a refresh command is issued by the system device to the interface circuit to refresh one of the two emulated DRAM devices, the interface circuit will stagger N numbers of refresh cycles to the N numbers of DRAM devices. In one optional feature when the system device issues the refresh command to the interface circuit to refresh both of the emulated DRAM devices, the interface circuit will stagger 2*N numbers of refresh cycles to the 2*N numbers of DRAM devices to minimize voltage droop on the power delivery network, while ensuring that the entire sequence completes within the allowed refresh cycle time of the single emulated DRAM device of capacity N*M.


As can be understood from the above discussion of the several disclosed configurations of the embodiments of FIG. 13, there exist at least as many refresh command sequence spacing possibilities as there are possible configurations of DRAM memory devices on a DIMM.


The response of a memory device to one or more time-domain pulses can be represented in the frequency domain as a spectrograph. Similarly, the power delivery system of a motherboard has a natural frequency domain response. In one embodiment, the frequency domain response of the power delivery system is measured, and the timing of refresh command sequence for a DIMM configuration is optimized to match the natural frequency response of the power delivery subsystem. That is, the frequency domain characteristics between the power delivery system and the memory device on the DIMM are anti-correlated such that the energy of the pulse stream of refresh command sequences spread the energy of the pulse stream out over a broad spectral range. Accordingly one embodiment of a method for optimizing memory refresh command sequences in a DIMM on a motherboard is to measure and plot the frequency domain response of the motherboard power delivery system, measure and plot the frequency domain response of the memory devices, superimpose the two frequency domain plots and define a refresh command sequence pulse train which frequency domain response, when superimposed on the aforementioned plots results in a flatter frequency domain response.



FIG. 14 is a conceptual illustration of a computer platform 1400 configured to implement one or more aspects of the embodiments. As an option, the contents of FIG. 14 may be implemented in the context of the architecture and/or environment of the figures previously described herein. Of course, however, such contents may be implemented in any desired environment.


As shown, the computer platform 1400 includes, without limitation, a system device 1420 (e.g., a motherboard), interface circuit(s) 1470, and memory module(s) 1480 that include physical memory devices 1481 (e.g., physical memory devices, such as the memory devices 104A-N shown in FIG. 1A). In one embodiment, the memory module(s) 1480 may include DIMMs. The physical memory devices 1481 are connected directly to the system 1420 by way of one or more sockets.


In one embodiment, the system device 1420 includes a memory controller 1421 designed to the specifics of various standards, in particular the standard defining the interfaces to JEDEC-compliant semiconductor memory (e.g., DRAM, SDRAM, DDR2, DDR3, etc.). The specifications of these standards address physical interconnection and logical capabilities. FIG. 14 depicts the system device 1420 further including logic for retrieval and storage of external memory attribute expectations 1422, memory interaction attributes 1423, a data processing engine 1424, various mechanisms to facilitate a user interface 1425, and the system basic Input/Output System (BIOS) 1426.


In various embodiments, the system device 1420 may include a system BIOS program capable of interrogating the physical memory module 1480 (e.g., DIMMs) as a mechanism to retrieve and store memory attributes. Furthermore, in external memory embodiments, JEDEC-compliant DIMMs include an EEPROM device known as a Serial Presence Detect (SPD) 1482 where the DIMM's memory attributes are stored. It is through the interaction of the system BIOS 1426 with the SPD 1482 and the interaction of the system BIOS 1426 with the physical attributes of the physical memory devices 1481 that the various memory attribute expectations and memory interaction attributes become known to the system device 1420. Also optionally included on the memory module(s) 1480 are an address register logic 1483 (e.g. JEDEC standard register, register, etc.) and data buffer(s) and logic 1484.


In various embodiments, the compute platform 1400 includes one or more interface circuits 1470, electrically disposed between the system device 1420 and the physical memory devices 1481. The interface circuits 1470 may be physically separate from the DIMM, may be placed on the memory module(s) 1480, or may be part of the system device 1420 (e.g., integrated into the memory controller 1421, etc.)


Some characteristics of the interface circuit(s) 1470, in accordance with an optional embodiment, includes several system-facing interfaces such as, for example, a system address signal interface 1471, a system control signal interface 1472, a system clock signal interface 1473, and a system data signal interface 1474. Similarly, the interface circuit(s) 1470 may include several memory-facing interfaces such as, for example, a memory address signal interface 1475, a memory control signal interface 1476, a memory clock signal interface 1477, and a memory data signal interface 1478.


In additional embodiments, an additional characteristic of the interface circuit(s) 1470 is the optional presence of one or more sub-functions of emulation logic 1430. The emulation logic 1430 is configured to receive and optionally store electrical signals (e.g., logic levels, commands, signals, protocol sequences, communications) from or through the system-facing interfaces 1471-1474 and to process those signals. In particular, the emulation logic 1430 may contain one or more sub functions (e.g., power management logic 1432 and delay management logic 1433) configured to manage refresh command sequencing with the physical memory devices 1481.


Aspects of embodiments of the invention can be implemented in hardware or software or both, with the software being delivered as a program product for use with a computer system. The program(s) of the program product defines functions of the embodiments (including the methods described herein) and can be contained on a variety of computer-readable storage media. Illustrative computer-readable storage media include, but are not limited to: (i) non-writable storage media (e.g., read-only memory devices within a computer such as CD-ROM disks readable by a CD-ROM drive) on which information is permanently stored; and (ii) writable storage media (e.g., floppy disks within a diskette drive or hard-disk drive) on which alterable information is stored. Such computer-readable storage media, when carrying computer-readable instructions that direct the functions disclosed herein, are yet further embodiments.


While the foregoing is directed to exemplary embodiments, other and further embodiments may be devised without departing from the basic scope thereof.

Claims
  • 1. A memory module comprising: 2*N dynamic random access memory (DRAM) devices each having a capacity of M, wherein the 2*N DRAM devices comprising: a first group of N DRAM devices; anda second group of N DRAM devices, wherein each of the N DRAM devices in the first group shares a distinct refresh control signal with a respective DRAM device in the second group;emulation logic configured to emulate an interface protocol of two emulated DRAM devices each having a capacity of N*M, wherein a first of the two emulated DRAM devices includes the N DRAM devices from the first group, and a second of the two emulated DRAM devices includes the N DRAM devices from the second group;an interface circuit configured to receive from a memory controller a refresh command for the two emulated DRAM devices, the interface circuit including: a calculation unit configured to determine offset timings for N independently controlled staggered refresh cycles, wherein exactly one DRAM device from the first group and one DRAM device from the second group are refreshed in each of the independently controlled staggered refresh cycles, the offset timings providing timings of each of the independently controlled staggered refresh cycles; anda scheduler configured to order independently controlled staggered refresh commands directed to the 2*N DRAM devices in the first and the second groups based on the offset timings determined by the calculation unit.
  • 2. The memory module of claim 1, wherein the interface circuit further comprises: a measurement unit configured to perform analog signal measurements and to determine a configuration of DRAM devices;wherein the calculation unit is configured to determine the independently controlled staggered refresh cycles based on measurements received from the measurement unit and the refresh command received from the memory controller.
  • 3. The memory module of claim 2, wherein the measurement unit is further configured to perform a series of analog measurements to determine analog pin characteristics of DRAM devices.
  • 4. The memory module of claim 2, wherein the measurement unit is further configured to perform a series of analog measurements to determine timing responses at selected logic threshold levels.
  • 5. The memory module of claim 2, wherein the measurement unit is further configured to perform a series of analog measurements to determine a timing response at a peak detected voltage change, a duration and a response ring.
  • 6. The memory module of claim 2, wherein the measurement unit is further configured to perform a series of measurements to determine an operating temperature of each of the DRAM devices.
  • 7. The memory module of claim 1, wherein the calculation unit is configured to determine the offset timings for two independently controlled staggered refresh cycles for four DRAM devices coupled to the interface circuit, wherein the two independently controlled staggered refresh cycles are staggered by an amount of time equal to approximately half a single refresh cycle associated with the refresh command received from the memory controller, and wherein each of the two independently controlled staggered refresh cycles refreshes a DRAM device in the first group and a DRAM device in the second group.
  • 8. The memory module of claim 1, wherein the calculation unit is configured to determine the offset timings for four independently controlled staggered refresh cycles for eight DRAM devices coupled to the interface circuit, wherein the four independently controlled staggered refresh cycles are staggered by an amount of time equal to approximately a quarter of a single refresh cycle associated with the refresh command received from the memory controller, and wherein each of the four independently controlled staggered refresh cycles refreshes a DRAM device in the first group and a DRAM device in the second group.
  • 9. The memory module of claim 1, wherein the calculation unit is configured to determine the offset timings for eight independently controlled staggered refresh cycles for sixteen DRAM devices coupled to the interface circuit, wherein the eight independently controlled staggered refresh cycles are staggered by an amount of time equal to approximately an eighth of a single refresh cycle associated with the refresh command received from the memory controller and wherein each of the eight independently controlled staggered refresh cycles refreshes a DRAM device in the first group and a DRAM device in the second.
  • 10. The memory module of claim 1, wherein the calculation unit is configured to dynamically determine, at a time subsequent to applying power to the dynamic random access memory devices, the offset timings for the independently controlled staggered refresh cycles that minimize instantaneous power supply load.
  • 11. The memory module of claim 1, wherein the interface circuit further comprises a memory address signal interface, a memory control signal interface, a memory clock signal interface, and a memory data signal interface.
  • 12. The memory module of claim 1, wherein each of the independently controlled staggered refresh cycles is transmitted to exactly two DRAM devices in a group.
  • 13. The memory module of claim 12, wherein the interface circuit is integrated within one of the first group or second group.
  • 14. The memory module of claim 13, wherein the interface circuit comprises an intelligent buffer chip.
  • 15. The memory module of claim 14, wherein the memory module is a dual in-line memory module.
  • 16. The memory module of claim 1, wherein the independently controlled staggered refresh cycles or the scheduling are performed asynchronously.
  • 17. The memory module of claim 16, wherein the memory module is a dual in-line memory module.
  • 18. The memory module of claim 1, wherein a time difference between the timings of each of the N independently controlled staggered refresh cycles differs for each of the independently controlled staggered refresh cycles.
  • 19. A memory module comprising: 2*N dynamic random access memory (DRAM) devices each having a capacity of M, wherein the 2*N DRAM devices comprise: a first group of N DRAM devices; anda second group of N DRAM devices, wherein each of the N DRAM devices in the first group shares a distinct refresh control signal with a respective DRAM device in the second group; andan interface circuit comprising: emulation logic configured to emulate an interface protocol of two emulated DRAM devices each having a capacity of N*M, wherein a first of the two emulated DRAM devices includes the N DRAM devices from the first group, and a second of the two emulated DRAM devices includes the N DRAM devices from the second group;a calculation unit configured to determine offset timings for N independently controlled staggered refresh cycles, wherein exactly one DRAM device from the first group and one DRAM device from the second group are refreshed in each of the independently controlled staggered refresh cycles, the offset timings providing timings of each of the independently controlled staggered refresh cycles; anda scheduler configured to order independently controlled staggered refresh commands directed to the 2*N DRAM devices based on the offset timings determined by the calculation unit.
  • 20. The memory module of claim 19, wherein the interface circuit further comprises: a measurement unit configured to perform analog signal measurements and to determine a configuration of DRAM devices;wherein the calculation unit is configured to determine the independently controlled staggered refresh cycles based on measurements received from the measurement unit and the refresh command received from the memory controller.
  • 21. The memory module of claim 19, wherein the calculation unit is configured to dynamically determine, at a time subsequent to applying power to the dynamic random access memory devices, the offset timings for the independently controlled staggered refresh cycles that minimize instantaneous power supply load.
  • 22. A sub-system comprising: a printed circuit board;a memory module comprising: 2*N dynamic random access memory (DRAM) devices each having a capacity of M, wherein the 2*N DRAM devices comprise: a first group of N DRAM devices; anda second group of N DRAM devices, wherein each of the N DRAM devices in the first group shares a distinct refresh control signal with a respective DRAM device in the second group; andan interface circuit comprising:emulation logic configured to emulate an interface protocol of two emulated DRAM devices each having a capacity of N*M, wherein a first of the two emulated DRAM devices includes the N DRAM devices from the first group, and a second of the two emulated DRAM devices includes the N DRAM devices from the second group;a calculation unit configured to determine offset timings for N independently controlled staggered refresh cycles, wherein exactly one DRAM device from the first group and one DRAM device from the second group are refreshed in each of the independently controlled staggered refresh cycles, the offset timings providing timings of each of the independently controlled staggered refresh cycles; anda scheduler configured to order independently controlled staggered refresh commands directed to the 2*N DRAM devices based on the offset timings determined by the calculation unit,wherein the memory module and the interface circuit are mounted to the printed circuit board, and the memory module is electrically coupled to the interface circuit.
  • 23. The sub-system of claim 22, wherein the interface circuit further comprises: a measurement unit configured to perform analog signal measurements and to determine a configuration of DRAM devices;wherein the calculation unit is configured to determine the independently controlled staggered refresh cycles based on measurements received from the measurement unit and the refresh command received from the memory controller.
  • 24. The sub-system of claim 22, wherein the calculation unit is configured to dynamically determine, at a time subsequent to applying power to the dynamic random access memory devices, the offset timings for the independently controlled staggered refresh cycles that minimize instantaneous power supply load.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of the U.S. patent application Ser. No. 11/828,181, filed on Jul. 25, 2007, which is a continuation-in-part of the U.S. patent application Ser. No. 11/584,179, filed on Oct. 20, 2006 now U.S. Pat. No. 7,581,127, which is a continuation of the U.S. patent application Ser. No. 11/524,811, filed on Sep. 20, 2006 now U.S. Pat. No. 7,590,796, which is a continuation-in-part of the U.S. patent application Ser. No. 11/461,439, filed on Jul. 31, 2006 now U.S. Pat. No. 7,580,312. Application Ser. No. 11/828,181 also claims the priority benefit of U.S. Provisional Patent Application No. 60/823,229, filed on Aug. 22, 2006. The subject matter the above related applications is hereby incorporated herein by reference. However, insofar as any definitions, information used for claim interpretation, etc. from the above parent application conflict with that set forth herein, such definitions, information, etc. in the present application should apply.

US Referenced Citations (845)
Number Name Date Kind
3800292 Curley et al. Mar 1974 A
4069452 Conway et al. Jan 1978 A
4323965 Johnson et al. Apr 1982 A
4334307 Bourgeois et al. Jun 1982 A
4345319 Bernardini et al. Aug 1982 A
4392212 Miyasaka et al. Jul 1983 A
4525921 Carson et al. Jul 1985 A
4566082 Anderson Jan 1986 A
4592019 Huang et al. May 1986 A
4646128 Carson et al. Feb 1987 A
4698748 Juzswik et al. Oct 1987 A
4706166 Go Nov 1987 A
4710903 Hereth et al. Dec 1987 A
4764846 Go Aug 1988 A
4780843 Tietjen Oct 1988 A
4794597 Ooba et al. Dec 1988 A
4796232 House Jan 1989 A
4807191 Flannagan Feb 1989 A
4841440 Yonezu et al. Jun 1989 A
4862347 Rudy Aug 1989 A
4884237 Mueller et al. Nov 1989 A
4887240 Garverick et al. Dec 1989 A
4888687 Allison et al. Dec 1989 A
4899107 Corbett et al. Feb 1990 A
4912678 Mashiko Mar 1990 A
4922451 Lo et al. May 1990 A
4935734 Austin Jun 1990 A
4937791 Steele et al. Jun 1990 A
4956694 Eide Sep 1990 A
4982265 Watanabe et al. Jan 1991 A
4983533 Go Jan 1991 A
5025364 Zellmer Jun 1991 A
5072424 Brent et al. Dec 1991 A
5083266 Watanabe Jan 1992 A
5104820 Go et al. Apr 1992 A
5193072 Frenkil et al. Mar 1993 A
5212666 Takeda May 1993 A
5220672 Nakao et al. Jun 1993 A
5222014 Lin Jun 1993 A
5241266 Ahmad et al. Aug 1993 A
5252807 Chizinsky Oct 1993 A
5257233 Schaefer Oct 1993 A
5278796 Tillinghast et al. Jan 1994 A
5282177 McLaury Jan 1994 A
5332922 Oguchi et al. Jul 1994 A
5347428 Carson et al. Sep 1994 A
5369749 Baker et al. Nov 1994 A
5384745 Konishi et al. Jan 1995 A
5388265 Volk Feb 1995 A
5390334 Harrison Feb 1995 A
5392251 Manning Feb 1995 A
5408190 Wood et al. Apr 1995 A
5432729 Carson et al. Jul 1995 A
5448511 Paurus et al. Sep 1995 A
5467455 Gay et al. Nov 1995 A
5483497 Mochizuki et al. Jan 1996 A
5498886 Hsu et al. Mar 1996 A
5502333 Bertin et al. Mar 1996 A
5502667 Bertin et al. Mar 1996 A
5513135 Dell et al. Apr 1996 A
5513339 Agrawal et al. Apr 1996 A
5519832 Warchol May 1996 A
5526320 Zagar et al. Jun 1996 A
5530836 Busch et al. Jun 1996 A
5550781 Sugawara et al. Aug 1996 A
5559990 Cheng et al. Sep 1996 A
5561622 Bertin et al. Oct 1996 A
5563086 Bertin et al. Oct 1996 A
5566344 Hall et al. Oct 1996 A
5581498 Ludwig et al. Dec 1996 A
5581779 Hall et al. Dec 1996 A
5590071 Kolor et al. Dec 1996 A
5598376 Merritt et al. Jan 1997 A
5604714 Manning et al. Feb 1997 A
5606710 Hall et al. Feb 1997 A
5608262 Degani et al. Mar 1997 A
5610864 Manning Mar 1997 A
5623686 Hall et al. Apr 1997 A
5627791 Wright et al. May 1997 A
5640337 Huang et al. Jun 1997 A
5640364 Merritt et al. Jun 1997 A
5652724 Manning Jul 1997 A
5654204 Anderson Aug 1997 A
5661677 Rondeau et al. Aug 1997 A
5661695 Zagar et al. Aug 1997 A
5668773 Zagar et al. Sep 1997 A
5675549 Ong et al. Oct 1997 A
5680342 Frankeny Oct 1997 A
5682354 Manning Oct 1997 A
5692121 Bozso et al. Nov 1997 A
5692202 Kardach et al. Nov 1997 A
5696732 Zagar et al. Dec 1997 A
5696929 Hasbun et al. Dec 1997 A
5702984 Bertin et al. Dec 1997 A
5703813 Manning et al. Dec 1997 A
5706247 Merritt et al. Jan 1998 A
RE35733 Hernandez et al. Feb 1998 E
5717654 Manning Feb 1998 A
5721859 Manning Feb 1998 A
5724288 Cloud et al. Mar 1998 A
5729503 Manning Mar 1998 A
5729504 Cowles Mar 1998 A
5742792 Yanai et al. Apr 1998 A
5748914 Barth et al. May 1998 A
5752045 Chen May 1998 A
5757703 Merritt et al. May 1998 A
5760478 Bozso et al. Jun 1998 A
5761703 Bolyn Jun 1998 A
5781766 Davis Jul 1998 A
5787457 Miller et al. Jul 1998 A
5798961 Heyden et al. Aug 1998 A
5802010 Zagar et al. Sep 1998 A
5802395 Connolly et al. Sep 1998 A
5802555 Shigeeda Sep 1998 A
5812488 Zagar et al. Sep 1998 A
5819065 Chilton et al. Oct 1998 A
5831833 Shirakawa et al. Nov 1998 A
5831931 Manning Nov 1998 A
5831932 Merritt et al. Nov 1998 A
5834838 Anderson Nov 1998 A
5835435 Bogin et al. Nov 1998 A
5838165 Chatter Nov 1998 A
5838177 Keeth Nov 1998 A
5841580 Farmwald et al. Nov 1998 A
5843799 Hsu et al. Dec 1998 A
5843807 Burns Dec 1998 A
5845108 Yoo et al. Dec 1998 A
5850368 Ong et al. Dec 1998 A
5859792 Rondeau et al. Jan 1999 A
5860106 Domen et al. Jan 1999 A
5870347 Keeth et al. Feb 1999 A
5870350 Bertin et al. Feb 1999 A
5872907 Griess et al. Feb 1999 A
5875142 Chevallier Feb 1999 A
5878279 Athenes Mar 1999 A
5884088 Kardach et al. Mar 1999 A
5901105 Ong et al. May 1999 A
5903500 Tsang et al. May 1999 A
5905688 Park May 1999 A
5907512 Parkinson et al. May 1999 A
5910010 Nishizawa et al. Jun 1999 A
5915105 Farmwald et al. Jun 1999 A
5915167 Leedy Jun 1999 A
5917758 Keeth Jun 1999 A
5923611 Ryan Jul 1999 A
5924111 Huang et al. Jul 1999 A
5926435 Park et al. Jul 1999 A
5929650 Pappert et al. Jul 1999 A
5943254 Bakeman, Jr. et al. Aug 1999 A
5946265 Cowles Aug 1999 A
5949254 Keeth Sep 1999 A
5953215 Karabatsos Sep 1999 A
5953263 Farmwald et al. Sep 1999 A
5954804 Farmwald et al. Sep 1999 A
5956233 Yew et al. Sep 1999 A
5963429 Chen Oct 1999 A
5963463 Rondeau et al. Oct 1999 A
5963464 Dell et al. Oct 1999 A
5963504 Manning Oct 1999 A
5966724 Ryan Oct 1999 A
5966727 Nishino Oct 1999 A
5969996 Muranaka et al. Oct 1999 A
5973392 Senba et al. Oct 1999 A
5978304 Crafts Nov 1999 A
5995424 Lawrence et al. Nov 1999 A
5995443 Farmwald et al. Nov 1999 A
6001671 Fjelstad Dec 1999 A
6002613 Cloud et al. Dec 1999 A
6002627 Chevallier Dec 1999 A
6014339 Kobayashi et al. Jan 2000 A
6016282 Keeth Jan 2000 A
6026027 Terrell, II et al. Feb 2000 A
6026050 Baker et al. Feb 2000 A
6029250 Keeth Feb 2000 A
6032214 Farmwald et al. Feb 2000 A
6032215 Farmwald et al. Feb 2000 A
6034916 Lee Mar 2000 A
6034918 Farmwald et al. Mar 2000 A
6035365 Farmwald et al. Mar 2000 A
6038195 Farmwald et al. Mar 2000 A
6038673 Benn et al. Mar 2000 A
6044032 Li Mar 2000 A
6047073 Norris et al. Apr 2000 A
6047344 Kawasumi et al. Apr 2000 A
6047361 Ingenio et al. Apr 2000 A
6053948 Vaidyanathan et al. Apr 2000 A
6058451 Bermingham et al. May 2000 A
6065092 Roy May 2000 A
6069504 Keeth May 2000 A
6070217 Connolly et al. May 2000 A
6073223 McAllister et al. Jun 2000 A
6075730 Barth et al. Jun 2000 A
6075744 Tsern et al. Jun 2000 A
6078546 Lee Jun 2000 A
6079025 Fung Jun 2000 A
6084434 Keeth Jul 2000 A
6088290 Ohtake et al. Jul 2000 A
6091251 Wood et al. Jul 2000 A
RE36839 Simmons et al. Aug 2000 E
6101152 Farmwald et al. Aug 2000 A
6101564 Athenes et al. Aug 2000 A
6101612 Jeddeloh Aug 2000 A
6108795 Jeddeloh Aug 2000 A
6111812 Gans et al. Aug 2000 A
6134638 Olarig et al. Oct 2000 A
6154370 Degani et al. Nov 2000 A
6166991 Phelan Dec 2000 A
6181640 Kang Jan 2001 B1
6182184 Farmwald et al. Jan 2001 B1
6199151 Williams et al. Mar 2001 B1
6208168 Rhee Mar 2001 B1
6216246 Shau Apr 2001 B1
6222739 Bhakta et al. Apr 2001 B1
6226709 Goodwin et al. May 2001 B1
6226730 Murdoch et al. May 2001 B1
6233192 Tanaka May 2001 B1
6233650 Johnson et al. May 2001 B1
6240048 Matsubara May 2001 B1
6243282 Rondeau et al. Jun 2001 B1
6252807 Suzuki et al. Jun 2001 B1
6253278 Ryan Jun 2001 B1
6260097 Farmwald et al. Jul 2001 B1
6260154 Jeddeloh Jul 2001 B1
6262938 Lee et al. Jul 2001 B1
6266285 Farmwald et al. Jul 2001 B1
6266292 Tsern et al. Jul 2001 B1
6274395 Weber Aug 2001 B1
6279069 Robinson et al. Aug 2001 B1
6295572 Wu Sep 2001 B1
6298426 Ajanovic Oct 2001 B1
6304511 Gans et al. Oct 2001 B1
6307769 Nuxoll et al. Oct 2001 B1
6314051 Farmwald et al. Nov 2001 B1
6317352 Halbert et al. Nov 2001 B1
6317381 Gans et al. Nov 2001 B1
6324120 Farmwald et al. Nov 2001 B2
6326810 Keeth Dec 2001 B1
6327664 Dell et al. Dec 2001 B1
6330683 Jeddeloh Dec 2001 B1
6336174 Li et al. Jan 2002 B1
6338108 Motomura Jan 2002 B1
6338113 Kubo et al. Jan 2002 B1
6341347 Joy et al. Jan 2002 B1
6343019 Jiang et al. Jan 2002 B1
6343042 Tsern et al. Jan 2002 B1
6353561 Funyu et al. Mar 2002 B1
6356105 Volk Mar 2002 B1
6356500 Cloud et al. Mar 2002 B1
6362656 Rhee Mar 2002 B2
6363031 Phelan Mar 2002 B2
6378020 Farmwald et al. Apr 2002 B2
6381188 Choi et al. Apr 2002 B1
6381668 Lunteren Apr 2002 B1
6389514 Rokicki May 2002 B1
6392304 Butler May 2002 B1
6414868 Wong et al. Jul 2002 B1
6418034 Weber et al. Jul 2002 B1
6421754 Kau et al. Jul 2002 B1
6424532 Kawamura Jul 2002 B2
6426916 Farmwald et al. Jul 2002 B2
6429029 Eldridge et al. Aug 2002 B1
6430103 Nakayama et al. Aug 2002 B2
6434660 Lambert et al. Aug 2002 B1
6437600 Keeth Aug 2002 B1
6438057 Ruckerbauer Aug 2002 B1
6442698 Nizar Aug 2002 B2
6445591 Kwong Sep 2002 B1
6452826 Kim et al. Sep 2002 B1
6452863 Farmwald et al. Sep 2002 B2
6453400 Maesako et al. Sep 2002 B1
6453402 Jeddeloh Sep 2002 B1
6453434 Delp et al. Sep 2002 B2
6455348 Yamaguchi Sep 2002 B1
6457095 Volk Sep 2002 B1
6459651 Lee et al. Oct 2002 B1
6473831 Schade Oct 2002 B1
6476476 Glenn Nov 2002 B1
6480929 Gauthier et al. Nov 2002 B1
6487102 Halbert et al. Nov 2002 B1
6489669 Shimada et al. Dec 2002 B2
6490161 Johnson Dec 2002 B1
6492726 Quek et al. Dec 2002 B1
6493789 Ware et al. Dec 2002 B2
6496440 Manning Dec 2002 B2
6496897 Ware et al. Dec 2002 B2
6498766 Lee et al. Dec 2002 B2
6510097 Fukuyama Jan 2003 B2
6510503 Gillingham et al. Jan 2003 B2
6512392 Fleury et al. Jan 2003 B2
6521984 Matsuura Feb 2003 B2
6526471 Shimomura et al. Feb 2003 B1
6526473 Kim Feb 2003 B1
6526484 Stacovsky et al. Feb 2003 B1
6545895 Li et al. Apr 2003 B1
6546446 Farmwald et al. Apr 2003 B2
6553450 Dodd et al. Apr 2003 B1
6560158 Choi et al. May 2003 B2
6563337 Dour May 2003 B2
6563759 Yahata et al. May 2003 B2
6564281 Farmwald et al. May 2003 B2
6564285 Mills et al. May 2003 B1
6574150 Suyama et al. Jun 2003 B2
6584037 Farmwald et al. Jun 2003 B2
6587912 Leddige et al. Jul 2003 B2
6590822 Hwang et al. Jul 2003 B2
6594770 Sato et al. Jul 2003 B1
6597616 Tsern et al. Jul 2003 B2
6597617 Ooishi et al. Jul 2003 B2
6614700 Dietrich et al. Sep 2003 B2
6618267 Dalal et al. Sep 2003 B1
6618791 Dodd et al. Sep 2003 B1
6621760 Ahmad et al. Sep 2003 B1
6628538 Funaba et al. Sep 2003 B2
6630729 Huang Oct 2003 B2
6631086 Bill et al. Oct 2003 B1
6639820 Khandekar et al. Oct 2003 B1
6646939 Kwak Nov 2003 B2
6650588 Yamagata Nov 2003 B2
6650594 Lee et al. Nov 2003 B1
6657634 Sinclair et al. Dec 2003 B1
6657918 Foss et al. Dec 2003 B2
6657919 Foss et al. Dec 2003 B2
6658016 Dai et al. Dec 2003 B1
6658530 Robertson et al. Dec 2003 B1
6659512 Harper et al. Dec 2003 B1
6664625 Hiruma Dec 2003 B2
6665224 Lehmann et al. Dec 2003 B1
6665227 Fetzer Dec 2003 B2
6668242 Reynov et al. Dec 2003 B1
6674154 Minamio et al. Jan 2004 B2
6683372 Wong et al. Jan 2004 B1
6684292 Piccirillo et al. Jan 2004 B2
6690191 Wu et al. Feb 2004 B2
6697295 Farmwald et al. Feb 2004 B2
6701446 Tsern et al. Mar 2004 B2
6705877 Li et al. Mar 2004 B1
6708144 Merryman et al. Mar 2004 B1
6710430 Minamio et al. Mar 2004 B2
6711043 Friedman et al. Mar 2004 B2
6713856 Tsai et al. Mar 2004 B2
6714891 Dendinger Mar 2004 B2
6724684 Kim Apr 2004 B2
6730540 Siniaguine May 2004 B2
6731009 Jones et al. May 2004 B1
6731527 Brown May 2004 B2
6742098 Halbert et al. May 2004 B1
6744687 Koo et al. Jun 2004 B2
6747887 Halbert et al. Jun 2004 B2
6751113 Bhakta et al. Jun 2004 B2
6751696 Farmwald et al. Jun 2004 B2
6754129 Khatri et al. Jun 2004 B2
6754132 Kyung Jun 2004 B2
6757751 Gene Jun 2004 B1
6762948 Kyun et al. Jul 2004 B2
6765812 Anderson Jul 2004 B2
6766469 Larson et al. Jul 2004 B2
6771526 LaBerge Aug 2004 B2
6772359 Kwak et al. Aug 2004 B2
6779097 Gillingham et al. Aug 2004 B2
6785767 Coulson Aug 2004 B2
6791877 Miura et al. Sep 2004 B2
6795899 Dodd et al. Sep 2004 B2
6799241 Kahn et al. Sep 2004 B2
6801989 Johnson et al. Oct 2004 B2
6807598 Farmwald et al. Oct 2004 B2
6807650 Lamb et al. Oct 2004 B2
6807655 Rehani et al. Oct 2004 B1
6816991 Sanghani Nov 2004 B2
6819602 Seo et al. Nov 2004 B2
6819617 Hwang et al. Nov 2004 B2
6820163 McCall et al. Nov 2004 B1
6820169 Wilcox et al. Nov 2004 B2
6826104 Kawaguchi et al. Nov 2004 B2
6839290 Ahmad et al. Jan 2005 B2
6845027 Mayer et al. Jan 2005 B2
6845055 Koga et al. Jan 2005 B1
6847582 Pan Jan 2005 B2
6850449 Takahashi Feb 2005 B2
6854043 Hargis et al. Feb 2005 B2
6862202 Schaefer Mar 2005 B2
6862249 Kyung Mar 2005 B2
6862653 Dodd et al. Mar 2005 B1
6873534 Bhakta et al. Mar 2005 B2
6878570 Lyu et al. Apr 2005 B2
6894933 Kuzmenka et al. May 2005 B2
6898683 Nakamura May 2005 B2
6908314 Brown Jun 2005 B2
6912778 Ahn et al. Jul 2005 B2
6914786 Paulsen et al. Jul 2005 B1
6917219 New Jul 2005 B2
6922371 Takahashi et al. Jul 2005 B2
6930900 Bhakta et al. Aug 2005 B2
6930903 Bhakta et al. Aug 2005 B2
6938119 Kohn et al. Aug 2005 B2
6943450 Fee et al. Sep 2005 B2
6944748 Sanches et al. Sep 2005 B2
6947341 Stubbs et al. Sep 2005 B2
6951982 Chye et al. Oct 2005 B2
6952794 Lu Oct 2005 B2
6961281 Wong et al. Nov 2005 B2
6968416 Moy Nov 2005 B2
6968419 Holman Nov 2005 B1
6970968 Holman Nov 2005 B1
6980021 Srivastava et al. Dec 2005 B1
6986118 Dickman Jan 2006 B2
6992501 Rapport Jan 2006 B2
6992950 Foss et al. Jan 2006 B2
7000062 Perego et al. Feb 2006 B2
7003618 Perego et al. Feb 2006 B2
7003639 Tsern et al. Feb 2006 B2
7007095 Chen et al. Feb 2006 B2
7007175 Chang et al. Feb 2006 B2
7010642 Perego et al. Mar 2006 B2
7010736 Teh et al. Mar 2006 B1
7024518 Halbert et al. Apr 2006 B2
7026708 Cady et al. Apr 2006 B2
7028215 Depew et al. Apr 2006 B2
7028234 Huckaby et al. Apr 2006 B2
7033861 Partridge et al. Apr 2006 B1
7035150 Streif et al. Apr 2006 B2
7043599 Ware et al. May 2006 B1
7043611 McClannahan et al. May 2006 B2
7045396 Crowley et al. May 2006 B2
7045901 Lin et al. May 2006 B2
7046538 Kinsley et al. May 2006 B2
7053470 Sellers et al. May 2006 B1
7053478 Roper et al. May 2006 B2
7058776 Lee Jun 2006 B2
7058863 Kouchi et al. Jun 2006 B2
7061784 Jakobs et al. Jun 2006 B2
7061823 Faue et al. Jun 2006 B2
7066741 Burns et al. Jun 2006 B2
7075175 Kazi et al. Jul 2006 B2
7079396 Gates et al. Jul 2006 B2
7079441 Partsch et al. Jul 2006 B1
7079446 Murtagh et al. Jul 2006 B2
7085152 Ellis et al. Aug 2006 B2
7085941 Li Aug 2006 B2
7089438 Raad Aug 2006 B2
7093101 Aasheim et al. Aug 2006 B2
7103730 Saxena et al. Sep 2006 B2
7110322 Farmwald et al. Sep 2006 B2
7111143 Walker Sep 2006 B2
7117309 Bearden Oct 2006 B2
7119428 Tanie et al. Oct 2006 B2
7120727 Lee et al. Oct 2006 B2
7126399 Lee Oct 2006 B1
7127567 Ramakrishnan et al. Oct 2006 B2
7133960 Thompson et al. Nov 2006 B1
7136978 Miura et al. Nov 2006 B2
7138823 Janzen et al. Nov 2006 B2
7149145 Kim et al. Dec 2006 B2
7149824 Johnson Dec 2006 B2
7173863 Conley et al. Feb 2007 B2
7200021 Raghuram Apr 2007 B2
7205789 Karabatsos Apr 2007 B1
7210059 Jeddeloh Apr 2007 B2
7215561 Park et al. May 2007 B2
7218566 Totolos, Jr. et al. May 2007 B1
7224595 Dreps et al. May 2007 B2
7228264 Barrenscheen et al. Jun 2007 B2
7231562 Ohlhoff et al. Jun 2007 B2
7233541 Yamamoto et al. Jun 2007 B2
7234081 Nguyen et al. Jun 2007 B2
7243185 See et al. Jul 2007 B2
7245541 Janzen Jul 2007 B2
7254036 Pauley et al. Aug 2007 B2
7266639 Raghuram Sep 2007 B2
7269042 Kinsley et al. Sep 2007 B2
7269708 Ware Sep 2007 B2
7274583 Park et al. Sep 2007 B2
7277333 Schaefer Oct 2007 B2
7286436 Bhakta et al. Oct 2007 B2
7289386 Bhakta et al. Oct 2007 B2
7296754 Nishizawa et al. Nov 2007 B2
7299330 Gillingham et al. Nov 2007 B2
7302598 Suzuki et al. Nov 2007 B2
7307863 Yen et al. Dec 2007 B2
7317250 Koh et al. Jan 2008 B2
7327613 Lee Feb 2008 B2
7337293 Brittain et al. Feb 2008 B2
7363422 Perego et al. Apr 2008 B2
7366947 Gower et al. Apr 2008 B2
7379316 Rajan May 2008 B2
7386656 Rajan et al. Jun 2008 B2
7392338 Rajan et al. Jun 2008 B2
7408393 Jain et al. Aug 2008 B1
7409492 Tanaka et al. Aug 2008 B2
7414917 Ruckerbauer et al. Aug 2008 B2
7428644 Jeddeloh et al. Sep 2008 B2
7437579 Jeddeloh et al. Oct 2008 B2
7441064 Gaskins Oct 2008 B2
7457122 Lai et al. Nov 2008 B2
7464225 Tsern Dec 2008 B2
7472220 Rajan et al. Dec 2008 B2
7474576 Co et al. Jan 2009 B2
7480147 Hoss et al. Jan 2009 B2
7480774 Ellis et al. Jan 2009 B2
7496777 Kapil Feb 2009 B2
7515453 Rajan Apr 2009 B2
7532537 Solomon et al. May 2009 B2
7539800 Dell et al. May 2009 B2
7573136 Jiang et al. Aug 2009 B2
7580312 Rajan et al. Aug 2009 B2
7581121 Barth et al. Aug 2009 B2
7581127 Rajan et al. Aug 2009 B2
7590796 Rajan et al. Sep 2009 B2
7599205 Rajan Oct 2009 B2
7606245 Ma et al. Oct 2009 B2
7609567 Rajan et al. Oct 2009 B2
7613880 Miura et al. Nov 2009 B2
7619912 Bhakta et al. Nov 2009 B2
7724589 Rajan et al. May 2010 B2
7730338 Rajan et al. Jun 2010 B2
7761724 Rajan et al. Jul 2010 B2
7934070 Brittain et al. Apr 2011 B2
7990797 Moshayedi et al. Aug 2011 B2
8116144 Shaw et al. Feb 2012 B2
20010000822 Dell et al. May 2001 A1
20010003198 Wu Jun 2001 A1
20010011322 Stolt et al. Aug 2001 A1
20010019509 Aho et al. Sep 2001 A1
20010021106 Weber et al. Sep 2001 A1
20010021137 Kai et al. Sep 2001 A1
20010046129 Broglia et al. Nov 2001 A1
20010046163 Yanagawa Nov 2001 A1
20010052062 Lipovski Dec 2001 A1
20020002662 Olarig et al. Jan 2002 A1
20020004897 Kao et al. Jan 2002 A1
20020015340 Batinovich Feb 2002 A1
20020019961 Blodgett Feb 2002 A1
20020034068 Weber et al. Mar 2002 A1
20020038405 Leddige et al. Mar 2002 A1
20020040416 Tsern et al. Apr 2002 A1
20020041507 Woo et al. Apr 2002 A1
20020051398 Mizugaki May 2002 A1
20020060945 Ikeda May 2002 A1
20020060948 Chang et al. May 2002 A1
20020064073 Chien May 2002 A1
20020064083 Ryu et al. May 2002 A1
20020089831 Forthun Jul 2002 A1
20020089970 Asada et al. Jul 2002 A1
20020094671 Distefano et al. Jul 2002 A1
20020121650 Minamio et al. Sep 2002 A1
20020121670 Minamio et al. Sep 2002 A1
20020124195 Nizar Sep 2002 A1
20020129204 Leighnor et al. Sep 2002 A1
20020145900 Schaefer Oct 2002 A1
20020165706 Raynham Nov 2002 A1
20020167092 Fee et al. Nov 2002 A1
20020172024 Hui et al. Nov 2002 A1
20020174274 Wu et al. Nov 2002 A1
20020184438 Usui Dec 2002 A1
20030002262 Benisek et al. Jan 2003 A1
20030011993 Summers et al. Jan 2003 A1
20030016550 Yoo et al. Jan 2003 A1
20030021175 Tae Kwak Jan 2003 A1
20030026155 Yamagata Feb 2003 A1
20030026159 Frankowsky et al. Feb 2003 A1
20030035312 Halbert et al. Feb 2003 A1
20030039158 Horiguchi et al. Feb 2003 A1
20030041295 Hou et al. Feb 2003 A1
20030061458 Wilcox et al. Mar 2003 A1
20030061459 Aboulenein et al. Mar 2003 A1
20030083855 Fukuyama May 2003 A1
20030088743 Rader May 2003 A1
20030093614 Kohn et al. May 2003 A1
20030101392 Lee May 2003 A1
20030105932 David et al. Jun 2003 A1
20030110339 Calvignac et al. Jun 2003 A1
20030117875 Lee et al. Jun 2003 A1
20030123389 Russell et al. Jul 2003 A1
20030126338 Dodd et al. Jul 2003 A1
20030127737 Takahashi Jul 2003 A1
20030131160 Hampel et al. Jul 2003 A1
20030145163 Seo et al. Jul 2003 A1
20030158995 Lee et al. Aug 2003 A1
20030164539 Yau Sep 2003 A1
20030164543 Kheng Lee Sep 2003 A1
20030174569 Amidi Sep 2003 A1
20030182513 Dodd et al. Sep 2003 A1
20030183934 Barrett Oct 2003 A1
20030189868 Riesenman et al. Oct 2003 A1
20030189870 Wilcox Oct 2003 A1
20030191888 Klein Oct 2003 A1
20030191915 Saxena et al. Oct 2003 A1
20030200382 Wells et al. Oct 2003 A1
20030200474 Li Oct 2003 A1
20030205802 Segaram et al. Nov 2003 A1
20030206476 Joo Nov 2003 A1
20030217303 Chua-Eoan et al. Nov 2003 A1
20030223290 Park et al. Dec 2003 A1
20030227798 Pax Dec 2003 A1
20030229821 Ma Dec 2003 A1
20030230801 Jiang et al. Dec 2003 A1
20030231540 Lazar et al. Dec 2003 A1
20030231542 Zaharinova-Papazova et al. Dec 2003 A1
20030234664 Yamagata Dec 2003 A1
20040016994 Huang Jan 2004 A1
20040027902 Ooishi et al. Feb 2004 A1
20040034732 Valin et al. Feb 2004 A1
20040034755 LaBerge et al. Feb 2004 A1
20040037133 Park et al. Feb 2004 A1
20040042503 Shaeffer et al. Mar 2004 A1
20040044808 Salmon et al. Mar 2004 A1
20040047228 Chen Mar 2004 A1
20040049624 Salmonsen Mar 2004 A1
20040057317 Schaefer Mar 2004 A1
20040064647 DeWhitt et al. Apr 2004 A1
20040064767 Huckaby et al. Apr 2004 A1
20040083324 Rabinovitz et al. Apr 2004 A1
20040088475 Streif et al. May 2004 A1
20040100837 Lee May 2004 A1
20040117723 Foss Jun 2004 A1
20040123173 Emberling et al. Jun 2004 A1
20040125635 Kuzmenka Jul 2004 A1
20040133736 Kyung Jul 2004 A1
20040139359 Samson et al. Jul 2004 A1
20040145963 Byon Jul 2004 A1
20040151038 Ruckerbauer et al. Aug 2004 A1
20040174765 Seo et al. Sep 2004 A1
20040177079 Gluhovsky et al. Sep 2004 A1
20040178824 Pan Sep 2004 A1
20040184324 Pax Sep 2004 A1
20040186956 Perego et al. Sep 2004 A1
20040188704 Halbert et al. Sep 2004 A1
20040195682 Kimura Oct 2004 A1
20040196732 Lee Oct 2004 A1
20040205433 Gower et al. Oct 2004 A1
20040208173 Di Gregoria Oct 2004 A1
20040225858 Brueggen Nov 2004 A1
20040228166 Braun et al. Nov 2004 A1
20040228196 Kwak et al. Nov 2004 A1
20040228203 Koo Nov 2004 A1
20040230932 Dickmann Nov 2004 A1
20040236877 Burton Nov 2004 A1
20040250989 Im et al. Dec 2004 A1
20040256638 Perego et al. Dec 2004 A1
20040257847 Matsui et al. Dec 2004 A1
20040257857 Yamamoto et al. Dec 2004 A1
20040260957 Jeddeloh et al. Dec 2004 A1
20040264255 Royer Dec 2004 A1
20040268161 Ross Dec 2004 A1
20050018495 Bhakta et al. Jan 2005 A1
20050021874 Georgiou et al. Jan 2005 A1
20050024963 Jakobs et al. Feb 2005 A1
20050027928 Avraham et al. Feb 2005 A1
20050028038 Pomaranski et al. Feb 2005 A1
20050034004 Bunker et al. Feb 2005 A1
20050036350 So et al. Feb 2005 A1
20050041504 Perego et al. Feb 2005 A1
20050044302 Pauley et al. Feb 2005 A1
20050044303 Perego et al. Feb 2005 A1
20050044305 Jakobs et al. Feb 2005 A1
20050047192 Matsui et al. Mar 2005 A1
20050071543 Ellis et al. Mar 2005 A1
20050078532 Ruckerbauer et al. Apr 2005 A1
20050081085 Ellis et al. Apr 2005 A1
20050086548 Haid et al. Apr 2005 A1
20050099834 Funaba et al. May 2005 A1
20050102590 Norris et al. May 2005 A1
20050105318 Funaba et al. May 2005 A1
20050108460 David May 2005 A1
20050127531 Tay et al. Jun 2005 A1
20050132158 Hampel et al. Jun 2005 A1
20050135176 Ramakrishnan et al. Jun 2005 A1
20050138267 Bains et al. Jun 2005 A1
20050138304 Ramakrishnan et al. Jun 2005 A1
20050139977 Nishio et al. Jun 2005 A1
20050141199 Chiou et al. Jun 2005 A1
20050149662 Perego et al. Jul 2005 A1
20050152212 Yang et al. Jul 2005 A1
20050156934 Perego et al. Jul 2005 A1
20050166026 Ware et al. Jul 2005 A1
20050193163 Perego et al. Sep 2005 A1
20050193183 Barth et al. Sep 2005 A1
20050194676 Fukuda et al. Sep 2005 A1
20050194991 Dour et al. Sep 2005 A1
20050195629 Leddige et al. Sep 2005 A1
20050201063 Lee et al. Sep 2005 A1
20050204111 Natarajan Sep 2005 A1
20050207255 Perego et al. Sep 2005 A1
20050210196 Perego et al. Sep 2005 A1
20050223179 Perego et al. Oct 2005 A1
20050224948 Lee et al. Oct 2005 A1
20050232049 Park Oct 2005 A1
20050235119 Sechrest et al. Oct 2005 A1
20050235131 Ware Oct 2005 A1
20050237838 Kwak et al. Oct 2005 A1
20050243635 Schaefer Nov 2005 A1
20050246558 Ku Nov 2005 A1
20050249011 Maeda Nov 2005 A1
20050259504 Murtugh et al. Nov 2005 A1
20050263312 Bolken et al. Dec 2005 A1
20050265506 Foss et al. Dec 2005 A1
20050269715 Yoo Dec 2005 A1
20050278474 Perersen et al. Dec 2005 A1
20050281096 Bhakta et al. Dec 2005 A1
20050281123 Bell et al. Dec 2005 A1
20050283572 Ishihara Dec 2005 A1
20050285174 Saito et al. Dec 2005 A1
20050286334 Saito et al. Dec 2005 A1
20050289292 Morrow et al. Dec 2005 A1
20050289317 Liou et al. Dec 2005 A1
20060002201 Janzen Jan 2006 A1
20060010339 Klein Jan 2006 A1
20060026484 Hollums Feb 2006 A1
20060038597 Becker et al. Feb 2006 A1
20060039204 Cornelius Feb 2006 A1
20060039205 Cornelius Feb 2006 A1
20060041711 Miura et al. Feb 2006 A1
20060041730 Larson Feb 2006 A1
20060044909 Kinsley et al. Mar 2006 A1
20060044913 Klein et al. Mar 2006 A1
20060049502 Goodwin et al. Mar 2006 A1
20060050574 Streif et al. Mar 2006 A1
20060056244 Ware Mar 2006 A1
20060062047 Bhakta et al. Mar 2006 A1
20060067141 Perego et al. Mar 2006 A1
20060085616 Zeighami et al. Apr 2006 A1
20060087900 Bucksch et al. Apr 2006 A1
20060090031 Kirshenbaum et al. Apr 2006 A1
20060090054 Choi et al. Apr 2006 A1
20060106951 Bains May 2006 A1
20060112214 Yeh May 2006 A1
20060112219 Chawla et al. May 2006 A1
20060117152 Amidi et al. Jun 2006 A1
20060117160 Jackson et al. Jun 2006 A1
20060118933 Haba Jun 2006 A1
20060120193 Casper Jun 2006 A1
20060123265 Ruckerbauer et al. Jun 2006 A1
20060126369 Raghuram Jun 2006 A1
20060129712 Raghuram Jun 2006 A1
20060129740 Ruckerbauer et al. Jun 2006 A1
20060129755 Raghuram Jun 2006 A1
20060133173 Jain et al. Jun 2006 A1
20060136791 Nierle Jun 2006 A1
20060149857 Holman Jul 2006 A1
20060149982 Vogt Jul 2006 A1
20060174082 Bellows et al. Aug 2006 A1
20060176744 Stave Aug 2006 A1
20060179262 Brittain et al. Aug 2006 A1
20060179333 Brittain et al. Aug 2006 A1
20060179334 Brittain et al. Aug 2006 A1
20060180926 Mullen et al. Aug 2006 A1
20060181953 Rotenberg et al. Aug 2006 A1
20060195631 Rajamani Aug 2006 A1
20060198178 Kinsley et al. Sep 2006 A1
20060203590 Mori et al. Sep 2006 A1
20060206738 Jeddeloh et al. Sep 2006 A1
20060233012 Sekiguchi et al. Oct 2006 A1
20060236165 Cepulis et al. Oct 2006 A1
20060236201 Gower et al. Oct 2006 A1
20060248261 Jacob et al. Nov 2006 A1
20060248387 Nicholson et al. Nov 2006 A1
20060262586 Solomon et al. Nov 2006 A1
20060262587 Matsui et al. Nov 2006 A1
20060277355 Ellsberry et al. Dec 2006 A1
20060294295 Fukuzo Dec 2006 A1
20070005998 Jain et al. Jan 2007 A1
20070050530 Rajan Mar 2007 A1
20070058471 Rajan et al. Mar 2007 A1
20070070669 Tsern Mar 2007 A1
20070088995 Tsern et al. Apr 2007 A1
20070091696 Niggemeier et al. Apr 2007 A1
20070106860 Foster et al. May 2007 A1
20070136537 Doblar et al. Jun 2007 A1
20070162700 Fortin et al. Jul 2007 A1
20070188997 Hockanson et al. Aug 2007 A1
20070192563 Rajan et al. Aug 2007 A1
20070195613 Rajan et al. Aug 2007 A1
20070204075 Rajan et al. Aug 2007 A1
20070216445 Raghavan et al. Sep 2007 A1
20070247194 Jain Oct 2007 A1
20070279084 Oh et al. Dec 2007 A1
20070288683 Panabaker et al. Dec 2007 A1
20070288686 Arcedera et al. Dec 2007 A1
20070288687 Panabaker et al. Dec 2007 A1
20080002447 Gulachenski et al. Jan 2008 A1
20080010435 Smith et al. Jan 2008 A1
20080025108 Rajan et al. Jan 2008 A1
20080025122 Schakel et al. Jan 2008 A1
20080025136 Rajan et al. Jan 2008 A1
20080025137 Rajan et al. Jan 2008 A1
20080027697 Rajan et al. Jan 2008 A1
20080027702 Rajan et al. Jan 2008 A1
20080027703 Rajan et al. Jan 2008 A1
20080028135 Rajan et al. Jan 2008 A1
20080028136 Schakel et al. Jan 2008 A1
20080028137 Schakel et al. Jan 2008 A1
20080031030 Rajan et al. Feb 2008 A1
20080031072 Rajan et al. Feb 2008 A1
20080034130 Perego et al. Feb 2008 A1
20080037353 Rajan et al. Feb 2008 A1
20080056014 Rajan et al. Mar 2008 A1
20080062773 Rajan et al. Mar 2008 A1
20080065820 Gillingham et al. Mar 2008 A1
20080082763 Rajan et al. Apr 2008 A1
20080086588 Danilak et al. Apr 2008 A1
20080089034 Hoss et al. Apr 2008 A1
20080098277 Hazelzet Apr 2008 A1
20080103753 Rajan et al. May 2008 A1
20080104314 Rajan et al. May 2008 A1
20080109206 Rajan et al. May 2008 A1
20080109595 Rajan et al. May 2008 A1
20080109597 Schakel et al. May 2008 A1
20080109598 Schakel et al. May 2008 A1
20080115006 Smith et al. May 2008 A1
20080120443 Rajan et al. May 2008 A1
20080120458 Gillingham et al. May 2008 A1
20080123459 Rajan et al. May 2008 A1
20080126624 Prete et al. May 2008 A1
20080126687 Rajan et al. May 2008 A1
20080126688 Rajan et al. May 2008 A1
20080126689 Rajan et al. May 2008 A1
20080126690 Rajan et al. May 2008 A1
20080126692 Rajan et al. May 2008 A1
20080130364 Guterman et al. Jun 2008 A1
20080133825 Rajan et al. Jun 2008 A1
20080155136 Hishino Jun 2008 A1
20080159027 Kim Jul 2008 A1
20080170425 Rajan Jul 2008 A1
20080195894 Schreck et al. Aug 2008 A1
20080215832 Allen et al. Sep 2008 A1
20080239857 Rajan et al. Oct 2008 A1
20080239858 Rajan et al. Oct 2008 A1
20080256282 Guo et al. Oct 2008 A1
20080282084 Hatakeyama Nov 2008 A1
20080282341 Hatakeyama Nov 2008 A1
20090024789 Rajan et al. Jan 2009 A1
20090024790 Rajan et al. Jan 2009 A1
20090049266 Kuhne Feb 2009 A1
20090063865 Berenbaum et al. Mar 2009 A1
20090063896 Lastras-Montano et al. Mar 2009 A1
20090070520 Mizushima Mar 2009 A1
20090089480 Wah et al. Apr 2009 A1
20090109613 Legen et al. Apr 2009 A1
20090216939 Smith et al. Aug 2009 A1
20090285031 Rajan et al. Nov 2009 A1
20090290442 Rajan Nov 2009 A1
20100005218 Gower et al. Jan 2010 A1
20100020585 Rajan Jan 2010 A1
20100257304 Rajan et al. Oct 2010 A1
20100271888 Rajan Oct 2010 A1
20100281280 Rajan et al. Nov 2010 A1
Foreign Referenced Citations (33)
Number Date Country
102004051345 May 2006 DE
102004053316 May 2006 DE
102005036528 Feb 2007 DE
0644547 Mar 1995 EP
62121978 Jun 1987 JP
01-171047 Jul 1989 JP
03-29357 Feb 1991 JP
03-276487 Dec 1991 JP
03-286234 Dec 1991 JP
05-298192 Nov 1993 JP
07-141870 Jun 1995 JP
08-77097 Mar 1996 JP
11-149775 Jun 1999 JP
22025255 Jan 2002 JP
3304893 May 2002 JP
04-327474 Nov 2004 JP
2006236388 Sep 2006 JP
1020040062717 Jul 2004 KR
2005120344 Dec 2005 KR
WO9505676 Feb 1995 WO
WO9725674 Jul 1997 WO
WO9900734 Jan 1999 WO
WO0045270 Aug 2000 WO
WO0190900 Nov 2001 WO
WO0197160 Dec 2001 WO
WO2004044754 May 2004 WO
WO2004051645 Jun 2004 WO
WO2006072040 Jul 2006 WO
WO 2007002324 Jan 2007 WO
WO2007028109 Mar 2007 WO
WO2007038225 Apr 2007 WO
WO2007095080 Aug 2007 WO
WO 2008063251 May 2008 WO
Non-Patent Literature Citations (266)
Entry
Non-final Office Action from U.S. Appl. No. 11/461,430 mailed on Feb. 19, 2009.
Final Office Action from U.S. Appl. No. 11/461,435 mailed on Jan. 28, 2009.
Non-final Office Action from U.S. Appl. No. 11/461,437 mailed on Jan. 26, 2009.
Non-final Office Action from U.S. Appl. No. 11/939,432 mailed on Feb. 19, 2009.
Office Action from U.S. Appl. No. 11/461,427 mailed on Sep. 5, 2008.
Final Office Action from U.S. Appl. No. 11/461,430 mailed on Sep. 08, 2008.
Notice of Allowance from U.S. Appl. No. 11/474,075 mailed on Nov. 26, 2008.
Office Action from U.S. Appl. No. 11/474,076 mailed on Nov. 3, 2008.
Office Action from U.S. Appl. No. 11/524,811 mailed on Sep. 17, 2008.
German Office Action From German Patent Application No. 11 2006 002 300.4-55 Mailed Jun. 5, 2009 (With Translation).
Non-Final Office Action From U.S. Appl. No. 11/461,430 Mailed Feb. 19, 2009.
Final Office Action From U.S. Appl. No. 11/461,435 Mailed Jan. 28, 2009.
Non-Final Office Action From U.S. Appl. No. 11/461,437 Mailed Jan. 26, 2009.
Non-Final Office Action From U.S. Appl. No. 11/461,441 Mailed Apr. 2, 2009.
Non-Final Office Action From U.S. Appl. No. 11/611,374 Mailed Mar. 23, 2009.
Non-Final Office Action From U.S. Appl. No. 11/762,010 Mailed Mar. 20, 2009.
Non-Final Office Action From U.S. Appl. No. 11/939,432 Mailed Feb. 6, 2009.
Non-Final Office Action From U.S. Appl. No. 12/111,819 Mailed Apr. 27, 2009.
Non-Final Office Action From U.S. Appl. No. 12/111,828 Mailed Apr. 17, 2009.
Fang et al., W. Power Complexity Analysis of Adiabatic SRAM, 6th Int. Conference on ASIC, vol. 1, Oct. 2005, pp. 334-337.
Pavan et al., P. A Complete Model of E2PROM Memory Cells for Circuit Simulations, IEEE Transactions on Computer-Aided Design of Integrated Circuits and Systems, vol. 22, No. 8, Aug. 2003, pp. 1072-1079.
German Office Action From German Patent Application No. 11 2006 001 810.8-55 Mailed Apr. 20, 2009 (With Translation).
Final Rejection From U.S. Appl. No. 11/461,437 Mailed Nov. 10, 2009.
Final Rejection from U.S. Appl. No. 11/762,010 Mailed Dec. 4, 2009.
Non-Final Rejection from U.S. Appl. No. 11/672,921 Mailed Dec. 8, 2009.
Non-Final Rejection from U.S. Appl. No. 11/672,924 Mailed Dec. 14, 2009.
Non-Final Rejection from U.S. Appl. No. 11/929,225 Mailed Dec. 14, 2009.
Non-Final Rejection from U.S. Appl. No. 11/929,261 Mailed Dec. 14, 2009.
Notice of Allowance From U.S. Appl. No. 11/611,374 Mailed Nov. 30, 2009.
Notice of Allowance From U.S. Appl. No. 11/939,432 Mailed Dec. 1, 2009.
Notice of Allowance From U.S. Appl. No. 12/111,819 Mailed Nov. 20, 2009.
Notice of Allowance From U.S. Appl. No. 12/111,828 Mailed Dec. 15, 2009.
Great Britain Office Action from GB Patent Application No. GB0800734.6 Mailed Mar. 1, 2010.
Final Office Action from U.S. Appl. No. 11/461,420 Mailed Apr. 28, 2010.
Notice of Allowance from U.S. Appl. No. 11/553,372 Mailed Mar. 12, 2010.
Notice of Allowance from U.S. Appl. No. 11/553,399 Mailed Mar. 22, 2010.
Non-Final Office Action from U.S. Appl. No. 11/588,739 Mailed Dec. 29, 2009.
Notice of Allowance from U.S. Appl. No. 11/611,374 Mailed Apr. 5, 2010.
Non-Final Office Action from U.S. Appl. No. 11/828,181 Mailed Mar. 2, 2010.
Non-Final Office Action from U.S. Appl. No. 11/828,182 Mailed Mar. 29, 2010.
Final Office Action from U.S. Appl. No. 11/858,518 Mailed Apr. 21, 2010.
Non-Final Office Action from U.S. Appl. No. 11/929,432 Mailed Jan. 14, 2010.
Non-Final Office Action from U.S. Appl. No. 11/929,571 Mailed Mar. 3, 2010.
Non-Final Office Action from U.S. Appl. No. 11/929,636 Mailed Mar. 9, 2010.
Non-Final Office Action from U.S. Appl. No. 11/929,655 Mailed Mar. 3, 2010.
Non-Final Office Action from U.S. Appl. No. 11/939,432 Mailed Apr. 12, 2010.
Notice of Allowance from U.S. Appl. No. 12/111,819 Mailed Mar. 10, 2010.
Non-Final Office Action from U.S. Appl. No. 12/507,682 Mailed Mar. 8, 2010.
Notice of Allowance from U.S. Appl. No. 11/762,010 Dated Jun. 8, 2011.
Non-Final Office Action from U.S. Appl. No. 11/672,924 Dated Jun. 8, 2011.
Non-Final Office Action from U.S. Appl. No. 11/929,225 Dated Jun. 8, 2011.
Notice of Allowance from U.S. Appl. No. 11/929,500 Dated Jun. 13, 2011.
Notice of Allowance from U.S. Appl. No. 11/941,589 Dated Jun. 15, 2011.
Final Office Action from U.S. Appl. No. 12/057,306 Dated Jun. 15, 2011.
Final Office Action from U.S. Appl. No. 12/769,428 Dated Jun. 16, 2011.
Notice of Allowance from U.S. Appl. No. 12/203,100 Dated Jun. 17, 2011.
Notice of Allowance from U.S. Appl. No. 11/762,013 Dated Jun. 20, 2011.
Non-Final Office Action from U.S. Appl. No. 12/797,557 Dated Jun. 21, 2011.
Notice of Allowance from U.S. Appl. No. 11/929,483 Dated Jun. 23, 2011.
Non-Final Office Action from U.S. Appl. No. 11/702,960 Dated Jun. 23, 2011.
Non-Final Office Action from U.S. Appl. No. 11/929,655 Dated Jun. 24, 2011.
Notice of Allowance from U.S. Appl. No. 11/763,365 Dated Jun. 24, 2011.
Notice of Allowance from U.S. Appl. No. 11/611,374 Dated Jun. 24, 2011.
Notice of Allowance from U.S. Appl. No. 12/838,896 Dated Apr. 19, 2011.
Notice of Allowance from U.S. Appl. No. 11/702,981 Dated Apr. 25, 2011.
Notice of Allowance from U.S. Appl. No. 11/929,320 Dated May 5, 2011.
Final Office Action from U.S. Appl. No. 11/939,440 Dated May 19, 2011.
Final Office Action from Application No. 11/855,805, Dated May 26, 2011.
Non-Final Office Action from U.S. Appl. No. 11/672,921 Dated May 27, 2011.
Supplemental European Search Report and Search Opinion issued Sep. 21, 2009 in European Application No. 07870726.2, 8 pp.
Wu et al., ‘eNVy: A Non-Volatile, Main Memory Storage System’, ASPLOS-VI Proceedings, Oct. 4-7, 1994, pp. 86-97.
Buffer Device for Memory Modules (DIMM)', IP.com Prior Art Database, <URL: http://ip.com/IPCOM/000144850>, Feb. 10, 2007, 1 pg.
German Office Action from German Patent Application No. 11 2006 002 300.4-55 Dated May 11, 2009 (With Translation).
Great Britain Office Action from GB Patent Application No. GB0803913.3 Dated Mar. 1, 2010.
Preliminary Report on Patentability From PCT Application No. PCT/US06/24360 Dated on Jan. 10, 2008.
Written Opinion From PCT Application No. PCT/US06/24360 Dated on Jan. 8, 2007.
International Search Report From PCT Application No. PCT/US06/34390 Dated on Nov. 21, 2007.
Written Opinion From PCT Application No. PCT/US06/34390 Dated on Nov. 21, 2007.
International Preliminary Examination Report From PCT Application No. PCT/US07/016385 Dated Feb. 3, 2009.
Search Report and Written Opinion From PCT Application No. PCT/US07/03460 Dated on Feb. 14, 2008.
Search Report From PCT Application No. PCT/US10/038041 Dated Aug. 23, 2010.
Non-Final Office Action from Application No. 11/461,420 Dated Jul. 23, 2009.
Notice of Allowance from Application No. 11/461,430 Dated Sep. 10, 2009.
Non-Final Office Action from Application No. 11/461,435 Dated Aug. 5, 2009.
Final Office Action from Application No. 11/461,435 Dated May 13, 2010.
Non-Final Office Action from Application No. 11/461,437 Dated Jan. 4, 2011.
Non-Final Office Action from Application No. 11/515,167 Dated Sep. 25, 2009.
Final Office Action from Application No. 11/515,167 Dated Jun. 3, 2010.
Non-Final Office Action from Application No. 11/515,223 Dated Sep. 22, 2009.
Notice of Allowance from Application No. 11/515,223 Dated Jul. 30, 2010.
Notice of Allowance from Application No. 11/515,223 Dated Feb. 4, 2011.
Non-Final Office Action from Application No. 11/538,041 Dated Jun. 10, 2009.
Non-Final Office Action from Application No. 11/553,372 Dated Jun. 25, 2009.
Notice of Allowance from Application No. 11/553,372 Dated Sep. 30, 2009.
Notice of Allowance from Application No. 11/553,372 Dated Aug. 4, 2010.
Non-Final Office Action from Application No. 11/553,372 Dated Jan. 5, 2011.
Non-Final Office Action from Application No. 11/553,390 Dated Sep. 9, 2009.
Final Office Action from Application No. 11/553,390 Dated Jun. 24, 2010.
Non-Final Office Action from Application No. 11/553,399 Dated Jul. 7, 2009.
Notice of Allowance from Application No. 11/553,399 Dated Oct. 13, 2009.
Notice of Allowance from Application No. 11/553,399 Dated Dec. 3, 2010.
Final Office Action from Application No. 11/588,739 Dated Dec. 15, 2010.
Notice of Allowance from Application No. 11/611,374 Dated Sep. 15, 2009.
Notice of Allowance from Application No. 11/611,374 Dated Jul. 19, 2010.
Notice of Allowance from Application No. 11/611,374 Dated Oct. 29, 2010.
Final Office Action from Application No. 11/672,921 Dated Jul. 23, 2010.
Final Office Action from Application No. 11/672,924 Dated Sep. 7, 2010.
Non-Final Office Action from Application No. 11/702,960 Dated Sep. 25, 2009.
Final Office Action from Application No. 11/702,960 Dated Jun. 21, 2010.
Non-Final Office Action from Application No. 11/702,981 Dated Mar. 11, 2009.
Non-Final Office Action from Application No. 11/702,981 Dated Aug. 19, 2009.
Notice of Allowance from Application No. 11/762,010 Dated Jul. 2, 2010.
Notice of Allowance from Application No. 11/762,010 Dated Oct. 22, 2010.
Notice of Allowance from Application No. 11/762,010 Dated Feb. 18, 2011.
Non-Final Office Action from Application No. 11/762,013 Dated Jun. 5, 2009.
Notice of Allowance from Application No. 11/762,013 Dated Aug. 17, 2010.
Notice of Allowance from Application No. 11/762,013 Dated Dec. 7, 2010.
Non-Final Office Action from Application No. 11/763,365 Dated Oct. 28, 2009.
Notice of Allowance from Application No. 11/763,365 Dated Jun. 29, 2010.
Notice of Allowance from Application No. 11/763,365 Dated Oct. 20, 2010.
Non-Final Office Action from Application No. 11/828,181 Dated Mar. 2, 2010.
Final Office Action from Application No. 11/828,182 Dated Dec. 22, 2010.
Non-Final Office Action from Application No. 11/855,805 Dated Sep. 21, 2010.
Non-Final Office Action from Application No. 11/855,826 Dated Jan. 13, 2011.
Non-Final Office Action from Application No. 11/858,518 Dated Aug. 14, 2009.
Non-Final Office Action from Application No. 11/858,518 Dated Sep. 8, 2010.
Final Office Action from Application No. 11/929,225 Dated Aug. 27, 2010.
Final Office Action from Application No. 11/929,261 Dated Sep. 7, 2010.
Final Office Action from Application No. 11/929,286 Dated Aug. 20, 2010.
Notice of Allowance from Application No. 11/929,320 Dated Sep. 29, 2010.
Final Office Action from Application No. 11/929,403 Dated Aug. 31, 2010.
Final Office Action from Application No. 11/929,417 Dated Aug. 31, 2010.
Final Office Action from Application No. 11/929,432 Dated Aug. 20, 2010.
Final Office Action from Application No. 11/929,450 Dated Aug. 20, 2010.
Notice of Allowance from Application No. 11/929,483 Dated Oct. 7, 2010.
Non-Final Office Action from Application No. 11/929,500 Dated Oct. 13, 2009.
Final Office Action from Application No. 11/929,500 Dated Jun. 24, 2010.
Final Office Action from Application No. 11/929,655 Dated Nov. 22, 2010.
Notice of Allowance from Application No. 11/939,432 Dated Sep. 24, 2009.
Notice of Allowance from Application No. 11/939,432 Dated Feb. 18, 2011.
Non-Final Office Action from Application No. 11/939,440 Dated Sep. 17, 2010.
Non-Final Office Action from Application No. 11/941,589 Dated Oct. 1, 2009.
Notice of Allowance from Application No. 11/941,589 Dated Oct. 25, 2010.
Non-Final Office Action from Application No. 12/057,306 Dated Oct. 8, 2010.
Notice of Allowance from Application No. 12/144,396 Dated Feb. 1, 2011.
Non-Final Office Action from Application No. 12/203,100 Dated Dec. 1, 2010.
Non-Final Office Action from Application No. 12/574,628 Dated Jun. 10, 2010.
Non-Final Office Action from Application No. 12/769,428 Dated Nov. 8, 2010.
Non-Final Office Action from Application No. 12/816,756 Dated Feb. 7, 2011.
Non-Final Office Action from Application No. 12/838,896 Dated Sep. 3, 2010.
Notice of Allowance from Application No. 11/762,013 Dated Feb. 22, 2011.
Notice of Allowance from Application No. 11/929,500 Dated Feb. 24, 2011.
Notice of Allowance from Application No. 11/763,365 Dated Mar. 1, 2011.
Final Office Action from Application No. 12/574,628 Dated Mar. 3, 2011.
Final Office Action from Application No. 11/929,571 Dated Mar. 3, 2011.
Notice of Allowance from Application No. 11/611,374 Dated Mar. 4, 2011.
Notice of Allowance from Application No. 11/929,483 Dated Mar. 4, 2011.
Notice of Allowance from Application No. 11/553,399 Dated Mar. 18, 2011.
Final Office Action from Application No. 12/507,682 Dated Mar. 29, 2011.
Non-Final Office Action from Application No. 11/929,403 Dated Mar. 31, 2011.
Non-Final Office Action from Application No. 11/929,417 Dated Mar. 31, 2011.
Office Action, including English translation, from co-pending Japanese application No. 2008-529353, Dated Jul. 31, 2012.
Final Office Action from U.S. Appl. No. 13/315,933, Dated Aug. 24, 2012.
Final Office Action from U.S. Appl. No. 13/276,212, Dated Aug. 30, 2012.
Non-Final Office Action from U.S. Appl. No. 13/367,182, Dated Aug. 31, 2012.
Notice of Allowance from U.S. Appl. No. 11/461,420, Dated Sep. 5, 2012.
Final Office Action from U.S. Appl. No. 13/280,251, Dated Sep. 12, 2012.
Non-Final Office Action from U.S. Appl. No. 11/929,225, Dated Sep. 17, 2012.
Notice of Allowance from U.S. Appl. No. 12/508,496, Dated Sep. 17, 2012.
Non-Final Office Action from U.S. Appl. No. 11/672,921, Dated Oct. 1, 2012.
Notice of Allowance from U.S. Appl. No. 12/057,306, Dated Oct. 10, 2012.
Notice Allowance from U.S. Appl. No. 12/144,396, Dated Oct. 11, 2012.
Non-Final Office Action from U.S. Appl. No. 13/411,489, Dated Oct. 17, 2012.
Non-Final Office Action from U.S. Appl. No. 13/471,283, Dated Dec. 7, 2012.
English translation of Office Action from co-pending Korean patent application No. KR1020087005172, dated Dec. 20, 2012.
Office Action, including English translation, from co-pending Japanese application No. 2008-529353, Dated Dec. 27, 2012.
Office Action from co-pending European patent application No. EP12150798, Dated Jan. 3, 2013.
Final Office Action from U.S. Appl. No. 11/672,924, Dated Feb. 1, 2013.
Non-Final Office Action from U.S. Appl. No. 13/260,650, Dated Feb. 1, 2013.
Notice of Allowance from U.S. Appl. No. 13/141,844, Dated Feb. 5, 2013.
Non-Final Office Action from U.S. Appl. No. 11/828,182 Dated Jun. 27, 2011.
Non-Final Office Action from U.S. Appl. No. 11/828,181 Dated Jun. 27, 2011.
Non-Final Office Action from U.S. Appl. No. 12/378,328 Dated Jul. 15, 2011.
Final Office Action from U.S. Appl. No. 11/461,420 Dated Jul. 20, 2011.
Notice of Allowance from U.S. Appl. No. 11/461,437 Dated Jul. 25, 2011.
Notice of Allowance from U.S. Appl. No. 11/702,981 Dated Aug. 5, 2011.
Notice of Allowability from U.S. Appl. No. 11/855,826 Dated Aug. 15, 2011.
Non-Final Office Action from U.S. Appl. No. 12/574,628 Dated Sep. 20, 2011.
Non-Final Office Action from U.S. Appl. No. 11/858,518 Dated Sep. 27, 2011.
Notice of Allowance from U.S. Appl. No. 11/929,571 Dated Sep. 27, 2011.
Notice of Allowance from U.S. Appl. No. 11/929,500 Dated Sep. 27, 2011.
Notice of Allowance from U.S. Appl. No. 11/941,589 Dated Sep. 30, 2011.
Notice of Allowance from U.S. Appl. No. 12/816,756 Dated Oct. 3, 2011.
Non-Final Office Action from U.S. Appl. No. 12/508,496 Dated Oct. 11, 2011.
Non-Final Office Action from U.S. Appl. No. 11/588,739 Dated Oct. 13, 2011.
Notice of Allowance from U.S. Appl. No. 11/939,432 Dated Oct. 24, 2011.
Non-Final Office Action from U.S. Appl. No. 11/929,631 Dated Nov. 1, 2011.
Non-Final Office Action from U.S. Appl. No. 11/553,372 Dated Nov. 14, 2011.
Notice of Allowance from U.S. Appl. No. 11/515,223 Dated Nov. 29, 2011.
Notice of Allowance from U.S. Appl. No. 12/769,428 Dated Nov. 28, 2011.
Final Office Action from U.S. Appl. No. 11/939,440 Dated Dec. 12, 2011.
Notice of Allowance from U.S. Appl. No. 12/797,557 Dated Dec. 28, 2011.
Office Action, including English translation, from co-pending Japanese application No. 2008-529353, Dated Jan. 10, 2012.
Notice of Allowance from U.S. Appl. No. 12/838,896 Dated Jan. 18, 2012.
Final Office Action from U.S. Appl. No. 11/929,655 Dated Jan. 19, 2012.
Final Office Action from U.S. Appl. No. 12/378,328 Dated Feb. 3, 2012.
Final Office Action from U.S. Appl. No. 11/672,921 Dated Feb. 16, 2012.
Final Office Action from U.S. Appl. No. 11/672,924 Dated Feb. 16, 2012.
Final Office Action from U.S. Appl. No. 11/929,225 Dated Feb. 16, 2012.
International Search Report for Application No. EP12150807 Dated Feb. 16, 2012.
Final Office Action from U.S. Appl. No. 11/828,181 Dated Feb. 23, 2012.
Non-Final Office Action from U.S. Appl. No. 11/461,520 Dated Feb. 29, 2012.
Notice of Allowance from U.S. Appl. No. 12/574,628 Dated Mar. 6, 2012.
Non-Final Office Action from U.S. Appl. No. 13/276,212 Dated Mar. 15, 2012.
Non-Final Office Action from U.S. Appl. No. 13/343,612 Dated Mar. 29, 2012.
Notice of Allowance from U.S. Appl. No. 11/939,440 Dated Mar. 30, 2012.
European Search Report from co-pending European application No. 11194876.6-2212/2450798, Dated Apr. 12, 2012.
European Search Report from co-pending European application No. 11194862.6-2212/2450800, Dated Apr. 12, 2012.
Notice of Allowance from U.S. Appl. No. 11/929,636, Dated Apr. 17, 2012.
Final Office Action from U.S. Appl. No. 11/858,518, Dated Apr. 17, 2012.
European Search Report from co-pending European application No. 11194883.2-2212, Dated Apr. 27, 2012.
Non-Final Office Action from U.S. Appl. No. 11/553/372, Dated May 3, 2012.
Notice of Allowance from U.S. Appl. No. 11/929,631, Dated May 3, 2012.
Non-Final Office Action from U.S. Appl. No. 13/165,713, Dated May 22, 2012.
Non-Final Office Action from U.S. Appl. No. 12/144,396, Dated May 29, 2012.
Non-Final Office Action from U.S. Appl. No. 13/165,713, Dated May 31, 2012.
Non-Final Office Action from U.S. Appl. No. 13/280,251, Dated Jun. 12, 2012.
Final Office Action from U.S. Appl. No. 11/855,805, Dated Jun. 14, 2012.
Notice of Allowance from U.S. Appl. No. 13/473,827, Dated Feb. 15, 2013.
Notice of Allowance from U.S. Appl. No. 12/378,328, Dated Feb. 27, 2013.
Non-Final Office Action from U.S. Appl. No. 13/536,093, Dated Mar. 1, 2013.
Office Action from co-pending Japanese patent application No. 2012-132119, Dated Mar. 6, 2013.
Notice of Allowance from U.S. Appl. No. 11/461,435, Dated Mar. 6, 2013.
Notice of Allowance from U.S. Appl. No. 11/515,223, Dated Mar. 18, 2013.
Notice of Allowance from U.S. Appl. No. 13/471,283, Dated Mar. 21, 2013.
Extended European Search Report for co-pending European patent application No. EP12150807.1, dated Feb. 1, 2013, mailed Mar. 22, 2013.
Notice of Allowance from U.S. Appl. No. 13/181,716, Dated Apr. 3, 2013.
English translation of Office Action from co-pending Korean patent application No. KR1020087019582, Dated Mar. 13, 2013.
Notice of Allowance from U.S. Appl. No. 13/618,246, Dated Apr. 23, 2013.
Notice of Allowance from U.S. Appl. No. 13/182,234, Dated May 1, 2013.
Final Office Action from U.S. Appl. No. 13/315,933, Dated May 3, 2013.
English Translation of Office Action from co-pending Korean patent application No. 10-2013-7004006, Dated Apr. 12, 2013.
Non-Final Office Action from U.S. Appl. No. 13/620,793, Dated May 6, 2013.
Non-Final Office Action from U.S. Appl. No. 13/620,565, Dated May 24, 2013.
Final Office Action from U.S. Appl. No. 11/929,225, Dated May 24, 2013.
Final Office Action from U.S. Appl. No. 11/672,921, Dated May 24, 2013.
Notice of Allowance from U.S. Appl. No. 11/929,631, Dated May 28, 2013.
Notice of Allowance from U.S. Appl. No. 13/620,424, Dated May 29, 2013.
Notice of Allowance from U.S. Appl. No. 13/341,844, Dated May 30, 2013.
Non-Final Office Action from U.S. Appl. No. 13/455,691, Dated Jun. 4, 2013.
Non-Final Office Action from U.S. Appl. No. 13/620,199, Dated Jun. 17, 2013.
Non-Final Office Action from U.S. Appl. No. 13/620,207, Dated Jun. 20, 2013.
Non-Final Office Action from U.S. Appl. No. 11/828,182, Dated Jun. 20, 2013.
Final Office Action from U.S. Appl. No. 11/828,181, Dated Jun. 20, 2013.
Notice of Allowance from U.S. Appl. No. 13/597,895, Dated Jun. 25, 2013.
Non-Final Office Action from U.S. Appl. No. 13/620,645, Dated Jun. 26, 2013.
Notice of Allowance from U.S. Appl. No. 13/471,283, Dated Jun. 28, 2013.
Notice of Allowance from U.S. Appl. No. 13/181,747, Dated Jul. 9, 2013.
Notice of Allowance from U.S. Appl. No. 11/515,223, Dated Jul. 18, 2013.
Notice of Allowance from U.S. Appl. No. 13/182,234, Dated Jul. 22, 2013.
Notice of Allowance from U.S. Appl. No. 13/181,716, Dated Jul. 22, 2013.
Non-Final Office Action from U.S. Appl. No. 13/620,233, Dated Aug. 2, 2013.
Final Office Action from U.S. Appl. No. 13/367,182, Dated Aug. 8, 2013.
Notice of Allowance from U.S. Appl. No. 13/615,008, Dated Aug. 15, 2013.
Notice of Allowance from U.S. Appl. No. 13/620,425, Dated Aug. 20, 2013.
Non-Final Office Action from U.S. Appl. No. 13/620,601, Dated Aug. 23, 2013.
Related Publications (1)
Number Date Country
20080109597 A1 May 2008 US
Provisional Applications (1)
Number Date Country
60823229 Aug 2006 US
Continuations (2)
Number Date Country
Parent 11828181 Jul 2007 US
Child 11929631 US
Parent 11524811 Sep 2006 US
Child 11584179 US
Continuation in Parts (2)
Number Date Country
Parent 11584179 Oct 2006 US
Child 11828181 US
Parent 11461439 Jul 2006 US
Child 11524811 US