Connect public, paid and private patent data with Google Patents Public Datasets

Systems, methods, and apparatus with programmable memory control for heterogeneous main memory

Info

Publication number
WO2008040028A2
WO2008040028A2 PCT/US2007/080015 US2007080015W WO2008040028A2 WO 2008040028 A2 WO2008040028 A2 WO 2008040028A2 US 2007080015 W US2007080015 W US 2007080015W WO 2008040028 A2 WO2008040028 A2 WO 2008040028A2
Authority
WO
Grant status
Application
Patent type
Prior art keywords
memory
module
controller
channel
heterogeneous
Prior art date
Application number
PCT/US2007/080015
Other languages
French (fr)
Other versions
WO2008040028A3 (en )
Inventor
Kenneth Okin
George Moussa
Kumar Ganapathy
Vijay Karamcheti
Rajesh Parekh
Original Assignee
Virident Systems, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRICAL DIGITAL DATA PROCESSING
    • G06F13/00Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/14Handling requests for interconnection or transfer
    • G06F13/16Handling requests for interconnection or transfer for access to memory bus
    • G06F13/1668Details of memory controller
    • G06F13/1694Configuration of memory controller to different memory types
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRICAL DIGITAL DATA PROCESSING
    • G06F12/00Accessing, addressing or allocating within memory systems or architectures
    • G06F12/02Addressing or allocation; Relocation
    • G06F12/08Addressing or allocation; Relocation in hierarchically structured memory systems, e.g. virtual memory systems
    • G06F12/0802Addressing of a memory level in which the access to the desired data or data block requires associative addressing means, e.g. caches
    • G06F12/0893Caches characterised by their organisation or structure
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRICAL DIGITAL DATA PROCESSING
    • G06F13/00Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/14Handling requests for interconnection or transfer
    • G06F13/16Handling requests for interconnection or transfer for access to memory bus
    • G06F13/1668Details of memory controller
    • G06F13/1684Details of memory controller using multiple buses
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRICAL DIGITAL DATA PROCESSING
    • G06F12/00Accessing, addressing or allocating within memory systems or architectures
    • G06F12/02Addressing or allocation; Relocation
    • G06F12/08Addressing or allocation; Relocation in hierarchically structured memory systems, e.g. virtual memory systems
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRICAL DIGITAL DATA PROCESSING
    • G06F2212/00Indexing scheme relating to accessing, addressing or allocation within memory systems or architectures
    • G06F2212/20Employing a main memory using a specific memory technology
    • G06F2212/205Hybrid memory, e.g. using both volatile and non-volatile memory
    • Y02D10/13
    • Y02D10/14

Abstract

A computer system is disclosed including a printed circuit board (200) (PCB) including a plurality of traces (116A.116B.116N)1 at least one processor (231) mounted to the PCB to couple to some of the plurality of trace (116A,116B,116N), a heterogeneous memory channel (125A.125N) including a plurality of sockets (113A.213A coupled to a memory channel bus of the PCB, and a memory controller (221) coupled between the at least one processor and the heterogeneous memory channel. The heterogeneous memory channel includes a plurality o sockets coupled to a memory channel bus of the PCB. The plurality of sockets are configured to receive a plurality of different types of memory modules (115A, 214A). The memory controller may be a programmable heterogeneous memory controller to flexibly adapt to the memory channel bus to control access to each of the different types of memory modules in the heterogeneous memory channel.

Description

SYSTEMS, METHODS, AND APPARATUS WITH PROGRAMMABLE MEMORY CONTROL FOR HETEROGENEOUS MAIN MEMORY

CROSS REFERENCE TO RELATED APPLICATIONS

[001] This patent application claims the benefit of U.S. Provisional Patent Application No. 60/956,681 entitled PROGRAMMABLE MEMORY CONTROL FOR HETEROGENEOUS MAIN MEMORY filed on August 17, 2007 by Kenneth Alan Okin et al; and further claims the benefit of U.S. Provisional Patent Application No. 60/827,421 entitled SUBSTITUTION OF A PROCESSOR WITH A BUILT IN DRAM MEMORY CONTROLLER BY A NON- DRAM MEMORY CONTROLLER TO CONTROL ACCESS TO NON-DRAM TYPE MEMORY MODULES filed on September 28, 2006 by inventors Kumar Ganapathy et al.; U.S. Provisional Patent Application No. 60/862,597 entitled EXPANSION OF MAIN MEMORY IN A MULTPROCESSOR SYSTEM WITH A NON-DRAM MEMORY CONTROLLER TO CONTROL ACCESS TO NON-DRAM TYPE MEMORY filed on October 23, 2006 by inventors Kumar Ganapathy et al; and U.S. Non-Provisional Application No. 11/864,763 entitled SYSTEMS AND APPARATUS WITH PROGRAMMABLE MEMORY CONTROL FOR HETEROGENEOUS MAIN MEMORY filed on September 28, 2007 by inventors Kenneth Alan Okin et al.

FIELD

[002] This application generally relates to memory controllers for controlling access to memory modules in main memory.

BACKGROUND

[003] A computing system may have a homogeneous main memory with one type of memory, such as dynamic random access memory (DRAM) integrated circuits (ICs).

[004] DRAM ICs retain data information by storing a certain amount of charge on a capacitor in each memory cell to store a logical one or alternatively, a logical zero. Over time, and because of read operations, the stored charge on the capacitor dissipates, in a process often referred to as leaking off. To preserve the stored charge on a DRAM capacitor, and thus maintain the ability of the DRAM to hold its memory contents, the stored charge in the memory cell may be increased through refresh cycles, which sometimes are performed periodically. A refresh cycle consumes power. BRIEF DESCRIPTIONS OF THE DRAWINGS

[005] Figure IA is a functional block diagram of a computer system with a heterogeneous main memory with programmable heterogeneous memory controllers for control thereof.

[006] Figure IB is a functional block diagram of a computer system with a heterogeneous main memory including DRAM memory modules and translating memory modules with different types of memory.

[007] Figure 2 is a functional block diagram of another computer system with a heterogeneous main memory with programmable heterogeneous memory controllers plugged into processor sockets or included as part of the processor to control the heterogeneous main memory.

[008] Figure 3 is a functional block diagram of another computer system with a heterogeneous main memory with memory circuits and memory controller circuits, including programmable heterogeneous memory controllers, coupled to a motherboard.

[009] Figure 4A is a functional block diagram of a non-DRAM type of memory module. [010] Figure 4B is a functional block diagram of a DRAM type of memory module. [011] Figure 4C is a functional block diagram of a translating memory module.

[012] Figure 5A is a functional block diagram of a system controller including a programmable heterogeneous memory controller.

[013] Figure 5B is a functional block diagram of a processor or multiprocessor including a programmable heterogeneous memory controller.

[014] Figure 6A is a block diagram of a plurality of standard memory channels with different types of memory modules coupled to a programmable heterogeneous memory controller.

[015] Figure 6B is a block diagram of a plurality of newly specified memory channels coupled to a re-programmed programmable heterogeneous memory controller.

[016] Figures 7A-7B are high-level functional block diagrams of an implementation of a programmable heterogeneous memory controller coupled to different types of memory modules in a memory channel.

[017] Figures 8A- 8B are more detailed functional block diagrams of an implementation of a programmable heterogeneous memory controller.

[018] Figure 9 is a functional block diagram of a memory module driver for each different type of memory module.

[019] Figure 10 is a table to illustrate information stored in a memory module socket register/table for each memory channel in a main memory.

[020] Figures 1 IA-11C are tables to illustrate reassigning the wire interconnect of a memory channel on the fly in response to the type of memory module being accessed.

[021] Figure 12A is a flow chart of a method of heterogeneous communication in a memory channel having different types of memory modules.

[022] Figure 12B is a flow chart of a method of communication to a non- volatile memory module in a memory channel.

[023] Figure 13 is a flow chart of a method of initializing the programmable heterogeneous memory controller.

[024] Figure 14 (including Figs. 14-1 through 14-5) is a table of a sample pin configuration re-mapping of a memory channel to access an exemplary non-volatile memory module.

DETAILED DESCRIPTION

[025] In the following detailed description, numerous examples of specific implementations are set forth. However, implementations may include configurations that include less than all of the alternatives for the detailed features and combinations set forth in these examples.

INTRODUCTION

[026] In some implementations, a programmable memory controller is provided to control access to different types of memory modules in a main memory. Non-volatile memory modules and DRAM memory modules may be used in the same memory channel that implements the same memory channel specification to form a heterogeneous main memory. In some implementations, the programmable memory controller may be contained in a commercially available processor or have the pin out of a commercially available processor so it may reside in the processor socket of a system. For example, the programmable memory controller may have a pinout of a processor and be plugged into a pre-existing motherboard with a socket that can receive the processor.

[027] Newer memory modules may have greater density and different electrical characteristics. Previously to gain the benefit of newer memory module designs, a new computer or a new mother board was purchased to accept the new type of memory module, because the design of the memory controller was tightly coupled to the type of memory module being accessed. If new memory modules with different technology are used in the design of a new system, a new hardware design for a new memory controller is oftentimes generated. Designing a new hardware design for a new memory controller may increase the time to market a new system. Instead of designing a new memory controller from scratch, a programmable memory controller may be programmed to provide the functionality to control and access new memory module designs and speed up the time to market for new systems.

COMPUTER SYSTEMS WITH HETEROGENEOUS MEMORY CHANNELS

[028] Referring now to Figure IA, a functional block diagram of a computer system IOOA with a heterogeneous main memory is illustrated. The computer system IOOA includes a multiprocessor mother-board IOOA'. Mounted to the mother-board IOOA' is a plurality of processor sockets 101A-101N. Processors 122A-122N may be inserted into these processor sockets. The processor sockets 101A-101N are connected to the interconnect fabric 103 via traces 102A-102N. The interconnect fabric 103 may consist of just traces or it may contain other integrated circuits, but its function is to connect the various processors, memory, and I/O together within the mother-board IOOA' . Portions of the interconnect fabric logic may be embedded within the processors and memory controllers.

[029] Additionally mounted to the mother-board IOOA' are one or more programmable heterogeneous memory controllers 107A-107N coupled to the interconnect fabric 103 via traces 106A-106N. The programmable heterogeneous memory controllers 107A-107N respectively control each of the memory channels 123A-123N. Printed circuit board traces 11 OA-I ION in each of the memory channels 123A-123N are coupled between the memory module sockets 108A-108N and the programmable heterogeneous memory controllers 107A- 107N. The memory module sockets may have proprietary pinouts or may be any one of the standard JEDEC pinouts (e.g., DDR2, DDR3, or other memory specification). [030] A plurality of different types of memory modules 109A-109N are plugged into the sockets 108A-108N of the heterogeneous memory channels. A heterogeneous memory channel is a memory channel in which mixed types or different types of memory modules may couple to the same memory channel bus. A homogeneous memory channel is a memory channel in which the same type of memory module (e.g., memory type (e.g., DDR2 DRAM etc)), but perhaps with different memory capacity, may couple to the same memory channel bus. The different types of memory modules in a heterogeneous memory channel may be dynamic random access memory dual-inline-memory modules (DRAM DIMMs) and nonvolatile random access memory dual-inline-memory modules (NVRAM DIMM)s, for example. In some implementations of the memory modules, the different types of memory modules are designed to meet some or all of the DDR2 memory module specification (or DDR3 or other memory specification). In other implementations of memory modules, new memory modules meet the DDR2 specification (or DDR3 or other memory specification) and reassigning existing motherboard interconnects to contain different control signals to interface between the memory controller and the new memory modules. The programmable heterogeneous memory controller supports the use of different control signaling for various purposes. For example, the new control signals to the new memory modules might increase memory capacity or signal additional device status information over the pre-existing memory channel traces.

[031] The programmable heterogeneous memory controller arbitrates and controls access to the memory channel bus by the different types of memory modules. The programmable memory controller can also arbitrate and control access to internal on-DEVIM data busses connecting integrated circuits within certain memory modules via additional control signaling. For example, non-volatile memory integrated circuits stacked up behind support chips may have their access to both the internal on-DEVIM bus and the memory channel bus arbitrated and controlled by the programmable heterogeneous memory controller. The programmable heterogeneous memory controller may control bus multiplexers in each of the DIMM support chips via extra control signals to allow access to the memory channel bus by selected non-volatile memory integrated circuits. In this manner, the non- volatile memory modules can have a greater memory capacity. Due to data skew and other timing considerations, typical main memory designs limit the number of DIMMS in a memory channel to a small number. The programmable heterogeneous memory controller allows extra control signaling so that the addressable memory capacity on a memory module and therefore within a memory channel can be increased substantially.

[032] The programmable heterogeneous memory controller may act autonomously from a processor. For example, the programmable heterogeneous memory controller may make all the memory coupled into the memory module sockets visible to the processors in the system or it may use some of the memory attached as a cache to improve the total performance of the memory system. In this case, faster types of memory modules may be selected by the memory controller to act as a level of cache memory. Additionally, the programmable heterogeneous memory controller may re-interpret address and read/write commands from a processor as it sees fit. This allows for example, the programmable heterogeneous memory controller to read from an address space encompassing a memory module while a write or erase operation is concurrently occurring within the same module.

[033] Additionally mounted to the mother-board IOOA are one or more I/O subsystems 105A-105N that are connected to the interconnect fabric 103 via traces 104A-104N. Alternatively or conjunctively, one or more VO subsystems 105' may be mounted to the mother-board IOOA and coupled to the programmable heterogeneous memory controllers 107A-107N (or a system controller) to provide access to I/O devices by the processors.

[034] In Figure IA, the memory controllers 107A-107N are directly coupled to the sockets 108A-108N in each memory channel 123A-123N by means of the PCB traces 11 OA-I ION. However, memory controllers may also indirectly couple to the sockets 108A-108N in each memory channel through secondary memory controllers.

[035] Referring now to Figure 2, an alternate multiprocessor system 200 and mother-board 200' is illustrated. In Figure 2, the programmable heterogeneous memory controller may be an external programmable heterogeneous memory controller 212 to plug into a socket or it may be an integrated programmable heterogeneous memory controller 212' co-packaged in the processor package as part of a processor 211. The processor 211 includes the integrated programmable heterogeneous memory controller 212'. That is, the processor package 211 contains both the processor element and the integrated programmable heterogeneous memory controller 212' . There may be one or more programmable heterogeneous memory controllers within one processor package.

[036] The external programmable heterogeneous memory controller 212 may be plugged into a processor socket 112B. Plugging the external programmable heterogeneous memory controller 212 into an open processor socket allows expansion and may upgrade a preexisting memory channel to support a heterogeneous main memory with different types of memory modules.

[037] In the multiprocessor system 200, processor sockets 112A-112N are connected to the interconnect fabric 103 via the traces 116A- 116N of the motherboard 200' . The processor sockets 112A-112N are also connected to the memory channels 113A-113N and 213A-213N via traces 125A-125N. Memory channels 113A-113N are homogeneous memory channels to control access to DRAM memory modules 114A-114N that are plugged into the sockets 115A-115N. Memory channels 213A-213N are heterogeneous memory channels to control access to different or mixed types of memory modules 214A-214N within each channel, such as DRAM memory modules and non- volatile memory modules that may be plugged into the sockets 115A-115N.

[038] In Figure 2, the main memory 150' may include homogeneous memory channels 113A-113N and heterogeneous memory channels 213A-213N that can be controlled by the heterogeneous memory controller 212,212'. Alternatively, a homogeneous memory controller 221 may be used to control access to homogeneous memory channels 113A-113N in the main memory. The homogeneous memory controller 221 may be co-packaged with a processor 231 and plugged into a socket 112A.

[039] One or more expansion connectors may also be used to upgrade the systems 10OA, 200 so that more memory capacity is available and/or reduce the power consumption in the main memory of the computer system.

[040] In some implementations, the one or more expansion connectors or slots 121A-121N may be used to upgrade and expand the main memory of the mother-board 100A',200'. A daughter card or expansion board (not shown) may be used to upgrade the main memory in the computer systems. The daughter card or expansion board would then include a programmable heterogeneous memory controller to control access to mixed or different types of memory modules in each channel. In this alternative manner, the main memory in the computer system may be expanded to be a heterogeneous main memory with different types of memory integrated circuits therein.

[041] In Figure 2, the external programmable heterogeneous memory controller 212, the processor 211 with the internal programmable heterogeneous memory controller 212', and the memory modules are plugged into sockets in order to couple to the mother board of the system. The programmable heterogeneous memory controller (PHMC) and the memory modules (MM) may be coupled to the mother boards of systems in other ways.

[042] Referring now to Figure 3, the memory controllers and the memory modules are coupled to the mother board 301 of a computer system 300 without a socket, such as by soldering chips directly thereto. The computer system 300 includes a mother board 301 with processors 122A-122N, memory controllers (programmable heterogeneous memory controllers 107A-107N, DRAM memory controller 117D, non-volatile memory controller 117NV), support chips 403A-403N, dynamic random access memory (DRAM) integrated circuits 314A-314N, static random access memory (SRAM) integrated circuits 315A-315N, and non- volatile memory integrated circuits 402A-402N directly coupled thereto without a socket, such as by soldering.

[043] The processors 122A-122N and the memory controllers (programmable heterogeneous memory controllers 107A-107N, DRAM memory controller 117D, nonvolatile memory controller 117NV) are coupled to the interconnect fabric 103 to communicate with each other. Alternatively, one or more of the memory controllers may be integrated into the processors as shown in Figure 2 to communicate with each other. Input/output chips 105A-105N may also be soldered to the motherboard and coupled to the interconnect fabric 103.

[044] The programmable heterogeneous memory controllers 107A-107N are coupled to the memory channel bus 110 to communicate with the different types of memory chips (SRAM 315A-315N, DRAM 114A-114N, NVRAM 402A-402N) in the heterogeneous memory channel. The DRAM memory controller (DMC) 117D is coupled to the memory channel bus 110' to communicate with the DRAM types of memory chips 314A-314N in the homogeneous memory channel. The non-volatile random access memory controller (NVMC) 117NV is coupled to the memory channel bus 110" to communicate with the NVRAM type of memory chips 402A-402N in a homogeneous memory channel. One or more support chips 403A-403N may be coupled between the respective memory chips and the respective memory channel bus 110,110', 110" to provide load isolation. The support chips may also be referred to as bridge chips herein. MEMORY MODULES

[045] Referring now to Figure 4A, a diagram of a non-DRAM type of memory module 214 (e.g., non-volatile memory module) is illustrated. The non-DRAM type of memory module 214 may be plugged into the memory module sockets 108A-108N, 115A-115N in the one or more heterogeneous memory channels 123A-123N, 213A-213N of the systems 10OA, 200 illustrated in Figures IA and 2, respectively.

[046] A given memory module may have different memory types (SRAM, DRAM, or NON- VOLITLE MEMORY) and logic or other circuitry on its printed circuit board. Alternatively, a given memory module may have a homogeneous type of memory and may contain logic or other types of circuitry.

[047] In some implementations, the non-DRAM type of memory module 214 is a nonvolatile type of memory module. The non- volatile type of memory module may include at least one NOR-gate flash electrically erasable programmable read only memory (EEPROM) integrated circuit in accordance with some implementations. In one configuration, read and write accesses to a non-volatile memory integrated circuit is asymmetric. In this case, a write to non- volatile memory integrated circuits takes more time than a read from the non- volatile memory integrated circuits. A memory erase operation in non- volatile memory integrated circuits also takes more time than a read access. Some types of non- volatile memory integrated circuits, such as NOR FLASH EEPROM integrated circuits, may be configured so that read access times may be reduced to levels sufficient for use in main memory where an address is presented and data returned. In one configuration to address the asymmetry between read and write performance, a data communication protocol for erasing and writing data into non-volatile memory modules may be used wherein instruction packets are written to the device and the device then commanded to program or erase larger amounts of data in non-volatile memory.

[048] In Figure 4A, the non-DRAM type of memory module 214 includes a printed circuit board (PCB) 400 having pads of edge connectors 401 (on each side for a DIMM) formed thereon, a plurality of non-DRAM memory chips 402A-402N, and a plurality of support chips 403A-403N. The printed circuit board (PCB) 400 has a low profile memory module form factor (e.g., 30 millimeters (mm) high or more and approximately 133mm wide) to be plugged into sockets without taking up much space. [049] The memory module 214 further includes a plurality of printed circuit board traces (e.g., printed wires) 404A-404N and 406A-406L formed on the PCB 400 coupling between the non-DRAM memory chips 402A-402N and the support chips 403A-403N and between the support chips 403A-403N and the pads of the edge connectors 401. The printed circuit board traces (e.g., printed wires) 404A-404N form an internal memory module bus 404 where the non-DRAM memory chips 402A-402N may contend for access to the memory channel bus through the support chips 403A-403B. The printed circuit board traces (e.g., printed wires) 406A-406L, collectively referred to by reference number 406, couple to the memory channel bus by way of the pads of the edge connectors 401.

[050] At least one of the plurality of support chips 403A-403N may include a memory module identification (MMID) 410 that may be stored therein to provided an identification of the type of memory module and information regarding the memory integrated circuits 402A- 402N mounted on the PCB 400. A plurality of signal lines form a communication port 412 over which the memory module identification (MMID) 410 may be communicated from each memory module to the programmable heterogeneous memory controller 107,212,212'. The support chip with the memory module identification further includes an input/output port 411 coupled to the communication port 412 to transmit and receive information over the port 412. If only a few signal lines are available to use, the communication port 412 may be a serial communication port and the I/O port 411 a serial I/O port with bi-direction communication of information being made with serial data. The MMID 410 may be polled by the programmable heterogeneous memory controller during initialization to determine the different types of memory modules that may be plugged into each socket. The MMID 410 may be communicated by a standard mechanism defined by a JEDEC standard or through some other mechanism.

[051] In some implementations, the memory module 214 is a dual in-line memory module (DIMM) and the printed circuit board (PCB) 400 is a DEVIM PCB with integrated circuits and pads of edge connectors on both front and back sides. The DIMMs may contain memory which does not have a deterministic access time. The DIMMs may thus signal the programmable heterogeneous memory controller that they either have data available for consumption or are ready to accept data. If a particular DIMM socket has a pinout for a specific JEDEC standard type of DDR, DDR2 or DDR3 DIMM and a DIMM not of that type is inserted into that particular socket, the programmable heterogeneous memory controller can program itself to reuse the existing pins of that DIMM SOCKET in the appropriate manner to control the type of DIMM that is inserted into the socket.

[052] In some implementations, the memory module 214 is a non-volatile memory module with the non-DRAM memory chips 402A-402N being non- volatile memory integrated circuit chips, such as NOR FLASH EEPROM integrated circuit chips. The non-volatile memory may be mapped into the same address space as the main memory and may look to the processor as being slightly slower main memory when read.

[053] Non-volatile memory integrated circuit chips typically have an asymmetry between read accesses and write accesses. Read access time is typically far less than the write access time due to the nature in which a write operation occurs into a non-volatile memory cell. Additionally, read accesses can randomly read any location in some non-volatile memory integrated circuits. However, write accesses tend to be block or sector oriented, once again due to the nature in which a write operation occurs to the non- volatile memory cells within the non- volatile memory integrated circuit. Thus, some non- volatile memory integrated circuits may be considered to randomly read locations like a random access memory but write sectors like a hard disk drive. These longer delays make the program and erase accesses to the non- volatile memory module non-deterministic events. That is, one may not know beforehand how long it will take a write operation or an erase operation to be completed by a non- volatile memory module.

[054] To try and alleviate some of the asymmetry with the write operations, each nonvolatile memory integrated circuit 402A-402N may include a write buffer 425 into which a plurality of write operations are stored for writing into a sector of memory cells at the appropriate moment. The write buffer 425 may store one or more words of data before data is written into the non-volatile memory cells, and a data communication protocol may be used to instruct the non- volatile memory integrated circuit where to write the data.

[055] The programmable heterogeneous memory controller may use one or more DRAM memory modules as cache memory for the non- volatile memory to improve system performance. In which case, the programmable heterogeneous memory controller may include a cache memory controller.

[056] Additionally, the non-volatile memory cells may be organized into a plurality of banks 426A-426D of non-volatile memory cells. In each memory integrated circuit, each of the banks may be further organized into sectors of non-volatile memory cells providing a predetermined memory capacity. While one bank is to be written with a write access or write operation, the other banks are free to be read by a read access or read operation. An erase operation to erase sectors of memory in the non- volatile memory integrated circuits may similarly be performed on a sector in one bank while other banks are free to be read by a read access or read operation.

[057] Each non-volatile memory integrated circuit 402A-402N may further include a status register 427 that may be polled by the memory controller to read the status of each bank, such as busy in a write mode or an erase mode. Additionally, the serial communication port 412 may be used to bi-directionally communicate information between the memory controller and the memory modules, such as status. The one or more support chips 403A-403N coupled to the serial communication port may include a register 415 to store status information regarding the operation of the memory integrated circuits 402A-402N that may be polled (requested) and communicated to the memory controller through the communication port 412.

[058] Moreover, a feedback control signal, such as the status signal 61 IF in Figure 6A, can be communicated from the non-volatile memory module to the memory controller to alleviate the non-deterministic nature of the write operations to the non- volatile memory modules. With the feedback control signal, the memory controller can avoid repeatedly polling the memory module to determine when an operation is completed by the memory module. One of the one or more support chips 403A-403N may receive status information from the memory integrated circuits 402A-402N and generate a status signal 61 IF that may be communicated to the memory controller over the memory channel bus.

[059] Data strobe signals used to access DRAM memory modules may change to be feedback control signals that can be communicated from a non-volatile memory module to the memory controller to alleviate the non-deterministic nature of the erase and write operations in the non-volatile memory modules. For example in the sample implementation illustrated in Figure 14, including Figs. 14-1 through 14-5, data strobe signals DQS 13, DQS 14, DQS 15, DQS 16 respectively change to status signals RY/BY_N_R1DO, RY/BY_N_R1D1, RY/BY_N_R1D2, RY/BY_N_R1D3 when a non-volatile memory module is being accessed within a memory module socket of a memory channel. The data strobe signals DQS 13, DQS 14, DQS 15, DQS 16 are used to clock data out each memory module in a DRAM memory channel. The RY/BY_N_R1DO, RY/BY_N_R1D1, RY/BY_N_R1D2, RY/BY_N_R1D3 signals are status signals for rank one memory of each of four DIMM modules/sockets that are in the memory channel. These status signals are fed back and coupled to the heterogeneous memory controller to more efficiently access the non-volatile memory module. Each status signal indicates whether or not a rank of memory in a memory module is busy or ready for another write or erase access to alleviate the non-deterministic nature of erase and write operations to non-volatile memory modules.

[060] While non-volatile memory integrated circuits individually may be slower to access than DRAM, high data bandwidth may be achieved over the memory channel bus by accessing a plurality of non-volatile memory integrated circuits in parallel. The average power consumption of non-volatile memory integrated circuits is relatively low so that a greater number may be mounted onto a DIMM printed circuit board to achieve a greater memory capacity within the same power budget. The programmable heterogeneous memory controller allows access to the plurality of non- volatile memory integrated circuits in parallel over a memory channel bus in a manner that is transparent to a processor.

[061] Note that the non-DRAM memory chips 402A-402N may also be some other kind of non-DRAM type of memory integrated circuit chips, such as static random access memory integrated circuits.

[062] The plurality of support chips 403A-403N may be used to buffer addresses, and/or multiplex and de-multiplex data to and from the non-DRAM memory chips 402A-403N. The plurality of support chips 403A-403N may also be referred to herein as a plurality of buffer integrated circuits 403.

[063] The support integrated circuit chips support (i.e., facilitate) read and write data accesses by the heterogeneous memory controller to the memory integrated circuits stacked up in different ranks and banks in the memory module. In some implementations, non-volatile memory integrated circuits are stacked up in a single multi chip package which is then attached to the non- volatile memory module.

[064] Each of the support chips 403A-403N may include a many-to-one bus multiplexer 422 and a one-to-many bus demultiplexer 424. Alternatively, the many-to-one bus multiplexer 422 and the one-to-many bus demultiplexer 424 may be integrated together as a cross-bar switch instead.

[065] The many-to-one bus multiplexer 422 is used to write data from some of the printed circuit board traces 404A-404N forming a plurality of busses coupled to the memory integrated circuits 402A-402N onto the memory channel bus over the printed circuit board traces 406A-406L. The many-to-one bus multiplexer 422 allows a large amount of data to be accessed in parallel, and then transferred to the memory controller in a burst of cycles. The one-to-many bus demultiplexer 424 may be used over a burst of cycles to receive data from the memory channel bus through the printed circuit board traces 406A-406L and then drive the data onto one of many data buses formed by printed circuit board traces 404A-404N coupled to the memory integrated circuits 402A-402N. A cross-bar switch may be similarly used to provide read and write access to the memory integrated circuits 402A-402N.

[066] The memory channel bus may be limited as to the number of integrated circuits that may directly couple thereto, due to loading and timing considerations. The bus multiplexing provided by the plurality of support chips 403A-403N on the memory module allows extra memory to be stacked up behind the support chip on each side of the DIMM so that is has a greater memory capacity available than otherwise possible without the support chips. The use of the plurality of support chips 403A-403N avoids adding extra capacitive loading onto the memory channel bus from the extra memory integrated circuit chips in the memory module. The programmable heterogeneous memory controller may control one or more of the plurality of support chips and the bus multiplexing over the memory channel bus to access the memory stacked up behind the support chips.

[067] Moreover if non-volatile memory modules are plugged into the sockets, a larger memory capacity may be had with less average power consumption. Even though extra memory integrated circuits are mounted in the memory module to increase memory capacity, the average power consumption may be lower if non- volatile memory integrated circuits are used in the memory modules.

[068] Reference is now made to Figure 4B illustrating a JEDEC standard DRAM DIMM 434 for a DDR2 memory channel bus. The DRAM DEVIM 434 includes a plurality of DRAM memory chips 436A-436N mounted to the printed circuit board 434 and directly coupled to the pads of the edge connector 440. Thus, the DRAM memory chips 436A-436N are more directly couple to the memory channel bus. The memory capacity of the DRAM DIMM 434 may be limited by the memory capacity provided by the DRAM memory chips 436A-436N directly coupled to the memory channel bus.

[069] The DRAM memory chips 436A-436N are designed to adhere to the specification of the memory channel bus, such as the DDR2 specification (or DDR3 or other memory specification). Each memory chip 436A-436N has address/control and data lines directly coupled to the pads of the edge connector 440.

[070] The DRAM DIMM 434 does not include any further support chips multiplexing data signals on and off the memory channel bus. The only multiplexing that may occur is internal to the memory chip itself and it is then multiplexing data bit columns of a memory array to the appropriate output pin of the memory chip. Without additional support chips providing additional multiplexing, the JEDEC standard ECC DRAM DIMM 434 may only have at most thirty-six individual memory chips. One rank of memory is typically located on the front side of the PCB 435 with memory chips directly coupled to the memory channel bus and another rank of memory is typically located on the back side of the PCB 435 with memory chips directly coupled to the memory channel bus. Limiting the number of ranks of memory to a predetermined number can limit the data bandwidth of the memory module and the memory channel.

[071] For greater memory capacity, the memory module 214 illustrated in Figure 4A may support up to 144 individual memory chips for example. Other non-volatile memory modules may be designed to support additional non- volatile memory integrated circuits.

[072] In accordance with the teachings of U.S. provisional patent application 60/827,421 filed on September 28, 2006 by inventors Kumar Ganapathy et al., incorporated here by reference, the main memory of the mother-board IOOA of Figure IA may be upgraded to swap out one or more DRAM memory modules with non- volatile memory modules in a memory channel to reduce average power consumption in a computer system. In this case, non-volatile memory modules 214 are plugged into the one or more sockets 108A-108N replacing DRAM memory modules in the respective memory channel with the appropriate memory controller inserted into sockets 107A-107N.

[073] In some implementations, each of the respective memory controllers 107A-107N of the memory channel is a programmable heterogeneous memory controller to control read and write access to the non-volatile memory modules 214 as well as other types of memory modules that may be plugged into the same memory channel. In some implementations, one or more processors in a multiprocessor system may be replaced with a processor package 211 having an integrated programmable heterogeneous memory controllers 212' to control read and write access to the non-volatile memory modules 214 in the respective memory channel. INTEGRATED PROGRAMMABLE HETEROGENEOUS MEMORY CONTROLLER

[074] Referring now to Figures 5A-5B, the programmable heterogeneous memory controller may be integrated into various chips to support memory channels with mixed types of memory modules.

[075] In Figure 5A, a functional block diagram of a system controller integrated circuit 500A is illustrated. The system controller integrated circuit 500A includes a programmable heterogeneous memory controller 50 IA, an input/output controller 502A, an expansion bus interface (e.g., PCI, hyperchannel) 504, and a device controller 506 to control access to devices other than memory. The programmable heterogeneous memory controller 50 IA controls access to mixed types of memory modules in the same memory channel.

[076] In Figure 5B, a functional block diagram of a central processing unit (CPU) or processor 500B with an integral or integrated memory controller is illustrated. The central processing unit (CPU) or processor 500B includes a programmable heterogeneous memory controller 50 IB, it may include an input/output controller 502B, a command controller 512, and one or more execution units (EU) 510. The programmable heterogeneous memory controller 50 IB may be integrated with the processor or merely co-packaged in the same package. The programmable heterogeneous memory controller 50 IB within the processor controls access to mixed types of memory modules in the same memory channel.

PROGRAMMABLE HETEROGENEOUS MEMORY CONTROLLER

[077] Referring now to Figures 6A-6B, the programmable heterogeneous memory controller 601A-601B is programmable to control access to memory modules within a memory channel. It may be programmed to support the different types of memory modules that may be plugged into the sockets of the same memory channel. That is, the types of memory modules plugged into the same memory channel may be mixed and the programmable heterogeneous memory controller may be programmed to communicate with each. For example, memory channel 602A may have any type of memory module 609A that supports the specification for memory channels (e.g., DDR2, DDR3, etc.) including a static random access memory module 609C, a non-volatile memory module 609D, or a DRAM memory module 609N. The programmable heterogeneous memory controller 60 IA may be programmed to communicate with each of these plurality of types of memory modules within the same memory channel. Provided that the memory module physically plugs into a memory socket 608A-608N, matches power connections or a subset thereof, and does not electrically invalidate the memory channel bus, it may be plugged into the same memory channel and accessed by the programmable heterogeneous memory controller 60 IA over the same memory channel bus as other modules. For example, memory modules with different data bandwidth's may be (e.g., BWl memory module 629 A and BW2 memory module 629C or non- volatile memory module 629D and DRAM memory module 629N) plugged into the same memory channel 602N and accessed by the memory controller 601A over the memory channel bus 610N.

[078] A memory channel 602A-602N is a group of wires coupled to a memory controller forming a memory channel bus 610A-610N with two classes of wire interconnect, point to point wires and broadcast or bus wires, which is in turn coupled to sockets to communicate with memory modules plugged therein. Each memory channel 602A-602N is independent from each other.

[079] Each memory channel bus 610A-610N further has a plurality of broadcast wires (PCB traces) 612 that are shared with each and every socket 608A-608N in the respective memory channel. That is, each of the wires making up the broadcast or bus wires 612 couple to each socket 608A-608N in the given memory channel and each memory module that is coupled there-to. Thus, signals that are written onto the broadcast wires 612 may be read by any one of the memory modules plugged into the memory sockets in the respective memory channel 602A-602N.

[080] Each memory channel bus 610A-610N has a plurality of point to point wires 611 that couple from the memory controller 60 IA to each respective socket 608A-608N. The plurality of point to point wires (PCB traces) 611 from the memory controller are independent from socket to socket.

[081] Generally in accordance with the JEDEC DDR2 specification there are four point to point wires for signals SO, Sl, ODTO, and ODTl in each memory channel. These point to point wires may be reassigned to another logical function. Additionally, there are approximately 29 address, clock and control output only signals from the memory controller to each and every socket/DIMM in each memory channel. Moreover, there are 72 bidirectional data lines and 36 bidirectional data strobe lines (1 data clock for four bits of data) between the memory controller and each and every socket/DIMM in each memory channel.

[082] One of the point to point wires 611 may be redefined to be a status signal 61 IF generated by a memory module that is communicated to the memory controller. For example, the status signal 61 IF may be fed back to the programmable heterogeneous memory controller 601A to let it know that the memory module is ready for another access. The status signal 61 IF is particularly useful for accessing non- volatile memory modules as it may take some time to write or erase memory locations therein. With the status signal 61 IF, the memory controller does not need to repeatedly poll the memory module with this capability to determine its status and whether or not it is ready for another erase or write operation.

[083] With reference to Figures 6A-6B, and 9, the heterogeneous memory controller 60 IA- 60 IB may be programmed by software, such as a memory module (MM) software driver 900. The memory module software driver 900 may read the memory module identification (ID) 904, then load data into the heterogeneous memory controller; such data might include the memory type 901 (e.g., SRAM, DRAM, or NVRAM); pin configuration 902; signal timing and logic levels 903 (e.g., active low or active high).

[084] A memory module can be matched to its memory module software driver through the memory module ID. That is, the memory module ID 410 read from the memory module should match the memory module identification (ID) 904 of the software driver 900. The memory module identification (ID) 410 may be encoded to indicate information regarding its source of manufacturer as well as the type of memory, its capacity, and speed. Moreover if a memory module software driver 900 for a given memory module ID is not readily available within the programmable heterogeneous memory controller 601A-601B, it may be downloaded over a network such as the internet or loaded from a disk, similar to how new printer drivers may be loaded into a computer system.

[085] With reference to Figure 10, the programmable heterogeneous memory controller 60 IA may poll each socket in each memory channel upon initialization to determine what types of memory module are plugged into each socket in each memory channel. Figure 10 illustrates an exemplary memory module socket table that may be stored in registers or a memory within the programmable heterogeneous memory controller 60 IA. The left most column indicates the socket number while the upper most row indicates the memory channel number. The entries into the table are representative of the memory module identification. For example, socket one (Sl) in memory channel one (MCl) may have an SRAMl type of memory module plugged in there-to. A socket may be empty or vacant. In which case, the table entry may be indicated as empty such as indicated for socket two (S2) in memory channel two (MC2) for example. The entries may be used to select the appropriate memory module driver to access each memory module in each respective memory channel.

[086] Referring now to Figures 1 IA-11C, differing pin configurations 902 are illustrated in the tables below the lines making up the memory channel bus 610. The first row in each table indicates the pin number. The second row in each table represents whether the pin is an input only pin (I), an output only pin (O), a bidirectional (both input and output) pin (B), or a power pin (P) such as a ground pin or a power supply pin. The third row in each table represents the functionality assigned to each pin, such as power (V), ground (G), no connect (NC), data pin (Di), address pin (Ai), or control pin (Ci). These differing pin configurations may be stored for example as the pin configuration 902 (see Figure 9) for different memory module drivers 900.

[087] Mixed types of memory modules in a memory channel may cause the memory controller to change the pin configuration of a memory channel bus on the fly as each memory module is being accessed. For example, the pin configuration illustrated in Figure 1 IA may be for accessing a first memory module over the memory channel bus 610. In Figure 1 IA, pins numbering 3 and 4 respectively are control input pins Cl and C2, for example. When accessing a second memory module of the memory channel bus 610, the pin configuration may change to that illustrated in Figure 1 IB, for example. In Figure 1 IB, pins numbering 3 and 4 are respectively bi-directional data bus pins Dl and D2, for example. When accessing a third memory module of the memory channel bus 610, the pin configuration may change to that illustrated in Figure 11C, for example. In Figure 11C, pins numbering 3 and 4 are respectively address input pins Al and A2, for example. The programmable heterogeneous memory controller 60 IA changes the signal functionality and pin assignment on the fly as each different memory module is accessed. If the same memory module is plugged into two memory sockets in the same memory channel, there may be no change in programming when the memory controller changes from accessing one to the other in succession.

[088] Note that the wires for power (V) and ground (G) do not change when accessing differing memory modules over the same memory channel. For example, pins numbering 1 and 2 remain constant as power (V) and ground (G) respectively. However, not every memory module need connect to every power or ground pin. For example, in Figure 1 IB, the memory module to be accessed with the pin configuration is a no-connect (NC) to pins N-I and N, ground (G) and power (V), respectively.

[089] To address additional memory and increase memory capacity of the main memory, the programmable heterogeneous memory controller in one configuration may use additional pins to form a larger address to address a larger memory space, in response to the type of memory module being accessed. In another configuration, the programmable heterogeneous memory controller may use pre-existing address pins over multiple address cycles to form a larger address to address a larger memory space in response to the type of memory module being accessed.

[090] Figure 14 (including Figs. 14-1 through 14-5) illustrates an exemplary pin configuration map of a non-volatile memory module in accordance with some implementations. When the non- volatile memory module is accessed, the pin configuration of the memory channel changes from the signal name column associated with a DDR2 memory module specification to the signal assigned column for the non- volatile memory module.

[091] For example, pins 73, 74 respectively change from WE#,CAS# to DIMM_ADDRO/ODTO,DIMM_ADDR1/ODT1 to identify which DIMM socket/DIMM memory module is being addressed after initialization and to setup the on-die termination during initialization.

[092] As another example, pins 188, 183, 63, 182, 61, 60, 180, 58, 179, 177, 70, 57, 176, 196, 174, 173, 54 respectively change from signal address bits AO, Al, A2, A3, A4, A5, A6, A7, A8, A9, A10/AP, Al l, A12, A13, A14, A15, A16/BA2 to multi-cycle address bits A0/A17/DSELJ), A1/A18/DSEL_1, A2/A19, A3/A20, A4/A21, A10/A27, Al l/Reset_N, A12/OE_N, A13/WEO_N, CE2_N/A14, CE3_N/A15, CE1_N/A16 to address a larger memory space within each memory module. To indicate whether an address high byte or an address low byte is available on these multi-cycle address pins, pin 195 respectively changes from ODTO to ADDR_HIGH. If ADDR_HIGH signal is a logically high signal, the address high byte (A17, A18, A19, etc.) is provided on the multi-cycle address bits. If ADDR_HIGH signal is a logically low signal, the address low byte (e.g., AO, Al, A2, etc) is provided on the multi-cycle address bits. [093] As another example, pins 193, 76 retain the same function. These signals select which rank of memory within a memory module is being accessed.

[094] As yet another example, pins 125, 134, 146, 155 respectively change from data strobe signals DQS9, DQSlO, DQSI l, DQS12 to RY/BY_N_R0D0, RY/BY_N_ROD1, RY/BY_N_R0D2, RY/BY_N_R0D3 when the non- volatile memory module is to be accessed within a socket. The RY/BY_N_R0D0, RY/BY_N_ROD1, RY/BY_N_R0D2, RY/BY_N_R0D3 signals are status signals for rank zero memory of each of four DIMM modules/sockets in a memory channel. Pins 202, 211, 223, 232 respectively change from data strobe signals DQS13, DQS14, DQS15, DQS16 to RY/BY_N_R1DO, RY/BY_N_R1D1, RY/BY_N_R1D2, RY/BY_N_R1D3 when the non- volatile memory module is to be accessed within a socket. The RY/BY_N_R1DO, RY/BY_N_R1D1, RY/BY_N_R1D2, RY/BY_N_R1D3 signals are status signals for rank one memory of each of the four DIMM modules/sockets in the memory channel. These status signals are fed back and coupled to the heterogeneous memory controller to more efficiently access the non-volatile memory module. Each status signal indicates whether or not a rank of memory in a memory module is busy or ready for another write or erase operation to alleviate the non-deterministic nature of erase and write operations to the non-volatile memory module.

[095] Figures 1 IA-11C have been described as changing the signal/pin configuration of the memory channel bus as each different memory module is accessed in each socket. However, the signal/pin configuration may also change due to a change in the specification of the memory channel bus for a new memory channel design.

[096] In Figure 6 A, each of the memory channel buses 610A-610N may be designed to support the DDR2 memory module specification. However, a new computer system may be designed with a different memory module specification and a different pin/signal configuration for a memory channel. As the heterogeneous memory controller 60 IA is programmable, its design can be readily updated to the new memory module specification and the new pin/signal configuration of a new memory channel.

[097] Consider Figure 6B for example. A new memory communication channel specification standard may be established to define a new pin/signal configuration for each of the new memory channel busses 650A-650N in each respective memory channel 602A'- 602N'. The memory modules may each be designed to mate with the new pin/signal configurations of the new memory channel busses 650A-650N. Provided that the total non- power pin count is equivalent, the programmable heterogeneous memory controller 60 IA may be readily updated by reprogramming to the programmable heterogeneous memory controller 60 IB illustrated in Figure 6B. The memory module drivers for the new memory channel standard are rewritten to support the new memory channel busses 640A-650B and the new drivers are loaded into the programmable heterogeneous memory controller 601B. In this manner, the logic design of the programmable heterogeneous memory controller can remain the same, being updated with software by loading new memory module drivers, while the circuits underneath the logic may change to adapt to new power supply voltages. That is, the logical netlist of the programmable heterogeneous memory controllers 60 IA and 60 IB remain the same while the pin configuration is updated by new memory module driver software. With the programmable heterogeneous memory controller 60 IA being programmable in this manner, the time to develop new or proprietary memory channels can be substantially reduced. Thus, the programmable heterogeneous memory controller is reusable as an IP core block as it can be readily programmable to the type of memory channel, memory channel bus, and memory modules to which it will interface. Different processor manufactures can purchase the logical netlist of the programmable heterogeneous memory controller and program it to meet their specific memory channel requirements.

[098] Referring now to Figures 7A-7B, a high-level functional block diagram of a programmable heterogeneous memory controller (PHMC) 700 is illustrated. In Figure 7A, the programmable heterogeneous memory controller 710 has yet to be programmed as it is waiting for memory modules to be plugged into the sockets or slots 705-708. Each memory channel controller 72Oi includes a specific memory module slot controller 721-724 for each slot or socket 705-708. In Figure 7B, two or more different types of memory modules (e.g., type A memory module 701, type B memory module 702, type C memory module 703, and type D memory module 704) are coupled into each memory channel 71Oi. Note that one or more of the memory modules plugged into the slots/sockets 705-708 may be the same type of memory module. In which case, two or more of the memory module slot controllers 721-724 may be programmed with the same program to handle the same types of DIMMs.

[099] For each memory channel 71Oi, the programmable heterogeneous memory controller 710 includes a memory channel controller 72Oi. Each of the memory channel controllers 72Oi is coupled between a processor interface 750 and their respective memory channel 71Oi. Each memory channel controller 72Oi couples to the processor or interconnect fabric interface 750 to communicate with a processor or I/O controller for memory operation instructions and results thereof.

[0100] As shown inn Figure 7B, each memory channel controller 72Oi may include a specific memory module slot controller 721-724 for each slot or socket 705-708 into which a memory module 701-704 may couple. Each memory channel controller 72Oi further includes a common memory module controller 730 coupled to a memory channel interface 732. Socket/Slot A memory module controller 721 is for controlling the type of memory module coupled into socket A 705 (e.g., type A memory module 701). Socket/slot B memory module controller 722 is for controlling the type of memory module coupled into socket B 706 (e.g., type B memory module 702). Socket/slot C memory module controller 723 is for controlling the type of memory module coupled into socket C 707 (e.g., type C memory module 703). Socket/slot D memory module controller 724 is for controlling the type of memory module coupled into socket D 708 (e.g., type D memory module 704). The specific memory module controllers 721-724 are for generating the different control signals for each different memory module that may be plugged into the available memory module sockets. The specific memory module controllers 721-724 are each programmable by a respective memory module software driver.

[0101] The common memory module controller 730 is for generating the common control signals amongst the different memory modules plugged into the available memory module sockets. The data pins and the address pins may remain the same between the different memory modules plugged into the available memory module sockets and may be under control of the common memory module controller 730.

[0102] The specific memory module controller 721-724 and the common memory module controller 730 for each memory channel 71Oi communicate to their respective memory modules through the memory channel interface 732. The memory channel interface 732 is flexible to allow for pin configuration changes in the memory channel bus 61Oi coupled to the memory modules and the respective sockets.

[0103] The memory channel bus 61Oi in each memory channel 71Oi includes a plurality of interconnect wires (PCB traces) which are shared or broadcast to all the memory modules and the respective sockets. The shared or broadcast signals to all the memory modules may be generated by the common memory module controller 730. The memory channel bus 61Oi in each memory channel 71Oi further includes a plurality of interconnect wires (PCB traces) which are independent and couple to only one of the memory modules and the respective sockets so that the signals are specific to that memory model. The specific signals for each individual memory model may be generated by the associated specific memory module controller 721-724. For example, specific signals for the type A memory module 701 and its socket 705 alone may be generated by the socket A memory module controller 721.

[0104] Referring now to Figure 8A, a more detailed functional block diagram of a programmable heterogeneous memory controller 800 is illustrated. Note that Figure 8A illustrates an example of how a programmable heterogeneous memory controller may be functionally organized internally - it is possible to construct programmable heterogeneous memory controller with a different arrangement of functional blocks. The programmable heterogeneous memory controller 800 includes a processor or interconnect fabric (system) interface 802, an input buffer 803, an output buffer 804, memory module socket control registers 806, micro-coded memory 808 (random access memory (RAM) and/or read only memory (ROM)), one or more input/output state machines 810, a flexible Input/Output port controller, and a flexible memory channel interface 814 (also referred to as a flexible I/O port) coupled together as shown. A direct memory access controller 813 may optionally be provided such that is may transfer data between the memory in the heterogeneous memory controller and some other device in the system.

[0105] The processor (system) interface 802 generally allows controlled access to a main memory by a processor. The processor (system) interface 802 may include an address port

816 to receive addresses from a processor from which to access main memory, a control port

817 to receive control signals from the processor to access main memory, a bidirectional data port 818 to read data from a processor to write into memory and to write data out to the processor after being read from memory, and status/control registers 820 to allow the processor to read the status of the memory channels and control the access to the memory channels coupled to the memory controller.

[0106] The input buffer 803 is to buffer addresses, controls, and data that is received from the processor. The output buffer 804 is to buffer the data that is to be written out to the processor. The input buffer 803 and the output buffer 804 may be combined together as a larger single input/output buffer with more complicated control logic.

[0107] The memory module socket registers 806 are provided to store the memory module identification (ID) of each memory module plugged into each socket in each memory channel that is directly coupled to the memory controller 800A. The memory module socket registers may store the information of a memory module socket table illustrated in Figure 10. With this information, the memory controller 800A knows what type of memory module it will directly communicate with in each socket.

[0108] The micro-coded memory 808 (random access memory (RAM) and/or read only memory (ROM)) is to store the memory module software drivers 900 for each different type of memory module indicated by the memory module socket registers 806. The memory module software drivers 900 may include the memory type 901 (e.g., SRAM, DRAM, or NVRAM); pin configuration 902; control signal timing and logic levels 903(e.g., active low or active high); and the memory module identification (ID) 904. The information contained in each memory module software driver 900 is coupled to the one or more I/O state machines 810. That is, the micro-coded memory 808 supplies memory module software drivers to the I/O state machines.

[0109] The one or more VO state machines 810 establish the appropriate pin configuration in the memory interface 814 and generate appropriate logic signals for the pins with the appropriate timing in response to the type of memory module being accessed in the given socket and its memory module software driver. The one or more I/O state machines 810 perform these functions each time a given memory module is accessed to perform a write operation, a read operation, or an erase operation. Functions of the one or more state machines are also described with reference to Figure 12. The one or more I/O state machines 810 signal the flexible I/O port controller 812 to establish the appropriate pin configuration in the memory interface 814 for accessing a given socket and memory module.

[0110] The flexible I/O port controller 812 establish the appropriate pin configuration in the memory interface 814 for accessing each given socket and memory module in response to control signals from the one or more I/O state machines 810.

[0111] The memory interface 814 establishes the state of its input/output buffers in response to controls from the port controller 812. Certain pins may be input only pins to received signals from the memory channel bus. Other pins may be output only pins with an output driver to drive out the signals to the memory channel bus. Still other pins, such as the data pins, may be bi-directional data pins that are selectively controlled to be input buffers when reading data off the memory channel bus and to be output buffers when writing data out to the memory channel bus.

[0112] The optional DMA controller 813 is for filling data buffers that may be included in the memory integrated circuits of the memory modules, such as the non- volatile memory integrated circuits. The optional DMA controller 813 uses direct memory access control to burst a sequence of data writes into memory modules or to burst read a sequence of data reads from a memory module into the memory controller. The DMA controller 813 instead may be a pre-fetch or cache controller with cache memory to decrease the latency for some type of memory modules.

[0113] Referring now to Figure 8B, further functional detail of the one or more I/O state machines 810 is now described. The one or more I/O state machines 810 includes a memory channel state machine 811A-81 IN for each memory channel 602A-602N coupled to the memory controller 800A. Each memory channel state machine 810A-811N includes a controller 825, a bus arbiter 826, and one or more memory module state machines 821A- 824A,821B-824B coupled together as shown for each memory module and each rank of memory therein.

[0114] For example, memory module state machines 82 IA and 82 IB are for a memory module that may be coupled into socket A. Memory module state machine 821A is for rank 1 of memory in a dual inline memory module plugged into socket A. Memory module state machine 82 IB is for rank 2 of memory in the dual inline memory module that is plugged into socket A. There may be additional memory module state machines for three or more ranks of memory for each respective memory module. Similarly, memory module state machines 822A and 822B (including any additional memory module state machines for additional ranks) are for respective ranks of memory of a memory module that may be coupled into socket B. Memory module state machines 823 A and 823B (including any additional memory module state machines for additional ranks) are for respective ranks of memory of a memory module that may be coupled into a socket C. Memory module state machines 824A and 824B (including any additional memory module state machines for additional ranks) are for respective ranks of memory of a memory module that may be coupled into a socket D and so on if additional sockets are available in a memory channel. While the programmable heterogeneous memory controller is being described here with respect to controlling access to a rank of memory assuming a homogeneous memory module, the memory controller may adapt to accessing different types of memory integrated circuits within one or more ranks of memory of a memory module. In that case, the memory module is a heterogeneous memory module being accessed by a programmable heterogeneous memory controller.

[0115] For non-volatile memory modules including non-volatile random access memory (NVRAM) integrated circuits, each of the memory module state machines 821A-824A,821B- 824B (including any additional memory module state machines for additional ranks) has a different operational mode and sequence of operations if memory in a given rank of memory is being read accessed (R), write accessed (W), and initialized or erased (I). Each of the memory module state machines 821A-824A,821B-824B is programmed with the information from the memory module software driver corresponding to the type of memory module plugged into the associated socket. For example, memory module state machines 82 IA and 821B will be programmed with the memory module software driver corresponding to the memory module plugged into the associated socket A in memory channel 602A.

[0116] In the case of other types of memory modules, there may be no initialization or erase operational sequence of operations.

[0117] The controller 825 is coupled to each memory module state machines 82 IA- 824A,821B-824B (including any additional memory module state machines for additional ranks) to control which memory module state machine is active and in which mode (read accessed (R), write accessed (W), initialized or erased (I)) in response to the type of access requested and the location of the memory module in the memory channel (e.g., which socket) that is being accessed.

[0118] The bus arbiter 826 is coupled to the controller 825 and each of the memory module state machines 821A-824A,821B-824B (including any additional memory module state machines for additional ranks) to arbitrate access to the memory channel bus when the state machines try to communicate with their corresponding memory module.

[0119] Each of the memory module state machines 821A-824A,821B-824B, along with the controller 825 and arbiter 826, generate the appropriate pin out configuration control signals to establish the proper pin out in the memory interface, the appropriate logic and timing of control signals, address signals, and data signals for reading and writing data over the memory channel bus into each memory module coupled thereto. METHODS FOR HETEROGENEOUS MEMORY CHANNEL COMMUNICATION

[0120] Figure 12A illustrates a flow chart of a method of communication to different types of memory modules in heterogeneous memory channels of a heterogeneous main memory.

[0121] At block 1202, a programmable heterogeneous memory controller is initialized. Each socket in each heterogeneous memory channel is polled to determine the different types of memory modules in each socket of each heterogeneous memory channel. The sockets in a heterogeneous memory channel may be vacant or empty in which case the programmable heterogeneous memory controller does not need a memory module driver for these sockets.

[0122] At block 1204, for each access to each different memory module in each heterogeneous memory channel, each pin of a memory channel interface is flexibly configured or adapted to communicate over wire interconnect of a memory channel bus to respective pins of each different memory module. This is in response to the type of memory module that is being accessed. Memory module software drivers may be used to flexibly adapt the pin configuration of the memory channel interface to the type of memory module that is being accessed. The memory channel interface may also be referred to as an input/output port.

[0123] To improve bandwidth in a heterogeneous memory channel, additional functionality may be assigned to underused or unused pins so that the communication protocol between some memory modules and the heterogeneous controller may be extended. Additional address control signal lines may be used to address additional ranks of memory or to address more complex types of memory or DIMM architectural extensions which allow much greater memory capacity. Moreover, a feedback pin may be defined for an underused or unused pin for each socket/memory module so that the programmable heterogeneous memory controller can receive status information from each memory module plugged into each socket in the heterogeneous memory controller. A status signal may be sent from each socket/memory module to the programmable heterogeneous memory controller so that it knows when each memory module may be accessed or not.

[0124] At block 1206, for each access to a different memory module in the heterogeneous memory channel, appropriate logic signals are generated for communication over the proper signal wires of the wire interconnect of the memory channel bus in order to communicate to a memory module. The appropriate logic signals are generated in response to the type of memory module that is being accessed at the time. For example, the logic signals may be active high signals or they may be active low signals depending upon the type of memory module being accessed. Thus, the appropriate logic signals to be generated may vary from memory module to memory module. Memory module software drivers may be used to flexibly change the generation of logic signals for communication over the memory channel bus in response to the type of memory module that is being accessed.

[0125] At block 1208, for each access to a different memory module in the heterogeneous memory channel, the logic signals are generated on the wire interconnect of the memory channel bus with appropriate signal timing to properly communicate with a memory module. The appropriate signal timing for driving logic signals onto the memory channel bus is responsive to the type of memory module that is being accessed at the time. That is, the appropriate signal timing may vary from memory module to memory module. Memory module software drivers may be used to flexibly change the signal timing of the generation of logic signals on the memory channel bus responsive to the type of memory module that is being accessed.

[0126] The programmable heterogeneous memory controller may be properly programmed for both write access and read access to each memory module in each socket of the heterogeneous memory channel in response to the type of memory module that is being accessed.

[0127] Referring now to Figure 12B, a flow chart of a method of communication to a nonvolatile memory module in a memory channel is illustrated.

[0128] At block 1212, the processor tells the memory controller to signal a non-volatile memory module to erase a sector of non-volatile memory or write a word of data into nonvolatile memory.

[0129] At block 1214, the non- volatile memory module being accessed signals back with a feedback status control signal that it is busy. The feedback status control signal from the memory module is coupled into the memory controller by way of a point-to-point wire interconnect in the memory channel bus. In some implementations, the feedback status control signal is the status signal 61 IF described herein.

[0130] At block 1216, the memory controller waits for an undetermined period of time due to the non-deterministic nature of the write and erase operations with the non- volatile memory module. That is, the memory controller waits for an indefinite period of time after receiving the feedback status control signal indicating busy.

[0131] At block 1218, the non-volatile memory module being accessed signals back with its feedback status control signal that it is now ready for another write operation or erase operation. A read operation may be performed by the non- volatile memory module into a different bank of memory while a write or erase operation is pending therein.

[0132] At block 1220, the memory controller initiates another operation with the memory module after the feedback status control signal is received. The memory controller may initiate another write access or erase a sector of non- volatile memory. Alternatively, the memory controller may interrupt the processor and signal that the non- volatile memory module is ready for another write or erase operation. The processor may also poll the feedback status control signal to await changes.

[0133] Figure 13 illustrates a flow chart of a method of initializing the programmable heterogeneous memory controller.

[0134] At block 1302, the computer system is powered on or re-booted such that the initialization of the programmable heterogeneous memory controller can occur.

[0135] At block 1304, each socket in each memory channel of main memory is polled to determine if a memory module is plugged into a socket. After polling a socket, if no response is heard by the programmable heterogeneous memory controller it may assume that no memory module is plugged into the socket. The socket is empty or vacant. The programmable heterogeneous memory controller may store information regarding the vacant or empty sockets into registers or scratch-pad memory as in the main memory socket table illustrated in Figure 10.

[0136] At block 1306, if a memory module is plugged into a socket, each memory module identification is read out and stored in association with its respective socket number or socket identifier. The memory module identification provides an indication of the type of memory module that is plugged into the socket. If a memory module identification cannot be read from a socket, the heterogeneous memory controller may try to communicate with the memory module assuming a different module type, and repeat the test until the known types of modules are exhausted.

[0137] At block 1308, after reading out the memory module identification, it is stored in association with its socket number and memory channel. The memory module identification may be stored into registers or a table in scratch pad memory of the programmable heterogeneous memory controller such as illustrated by the main memory socket table of Figure 10

[0138] At block 1310, memory module software drivers are loaded into the programmable heterogeneous memory controller and its one or more state machines to enable proper communication protocol with each of the different types of memory modules that may be coupled into each heterogeneous memory channel. If only one type of memory module is plugged into a memory channel, it is a homogeneous memory channel and only one memory module software driver may be required for proper communication to each.

[0139] If a memory module software driver is not available locally to the programmable heterogeneous memory controller, it may be acquired from a network source, such as the internet, or a software disk.

[0140] With the memory module software drivers coupled into the programmable heterogeneous memory controller and loaded into its one or more state machines, the programmable heterogeneous memory controller is initialized to access the different memory modules in each memory channel.

TRANSLATING MEMORY MODULES FOR HETEROGENEOUS MEMORY

CHANNELS

[0141] In the previous discussion, a programmable heterogeneous memory controller was used to flexibly adapt to communicate with different communication protocols to different types of memory modules in heterogeneous memory channels. However, newer memory modules may be designed to translate non-DDR signals into DDR signals so that prior DDR2 memory controllers may transparently communicate with newer memory modules of differing types.

[0142] Referring now to Figure IB, memory controllers 107A'-107N' may be standard DDR2 memory controllers to communicate with memory modules in accordance with the DDR2 specification over each memory channel bus. However, one or more of the memory modules 109A'-109N' plugged into sockets 108A- 108N in the memory channels 123A-123N may be a translating memory module (TMM). In Figure IB, each of the memory modules 109A' is a translating memory module. Another memory module 109N-1' in the same memory channel may be a DDR2 standard DRAM DIMM such that the memory channel 123A is a heterogeneous memory channel with the memory controller 107N' be unaware. The translating memory module (TMM) is designed to translate non-DDR signals into DDR signals for communication over each memory channel bus in a transparent manner to the memory controllers 107A'-107N'.

[0143] Referring now to Figure 4C, a functional block diagram of a translating memory module (TMM) 454 is illustrated. The translating memory module 454 includes a printed circuit board 455 with a non-DDR2 memory device 461 and a support chip 462 coupled thereto. One or several non-DDR2 memory devices 461 and the support chip 462 may be co- packaged together into one integrated circuit package 469 and mounted to the printed circuit board 455. A plurality of non-DDR2 memory devices 461 and a plurality of support chips 462 may be coupled to the PCB 455. The support chip 462 is coupled to the PCB 455 between the non-DDR2 memory 461 and pads of an edge connector 470. The pads of the edge connector 470 may be formed as part of the PCB 455. Otherwise a separate edge connector may be soldered to the PCB 455.

[0144] The support chip 462 includes a translator 465, a data transceiver (transmitter and receiver) 466 and an address/control receiver 467 coupled together as shown. The translator 465 is coupled between the non-DDR2 memory 461 and the data transceiver 466 and the address/control receiver 467.

[0145] The data transceiver 466 and the address/control receiver 467 bi-directionally interface the memory module 434 to the memory channel bus using DDR2 address, control, and data signaling.

[0146] The translator 465 is a bi-directional translator. The translator 465 translates non- DDR signals into DDR2 signals for communication over the memory channel bus in a transparent fashion to the memory controller. DDR2 signals received from the memory channel bus are translated as required by the translator 465 into non-DDR2 signals which the non-DDR2 memory 461 understands. In this manner, a non-DDR2 memory device in a memory module may communicate using a pre-existing memory channel bus and pre-existing memory controller. CONCLUSION

[0147] While this specification includes many specifics, these should not be construed as limitations on the scope of the disclosure or of what may be claimed, but rather as descriptions of features specific to particular implementations of the disclosure. Certain features that are described in this specification in the context of separate implementations also may be implemented in combination in a single implementation. Conversely, various features that are described in the context of a single implementation also may be implemented in multiple implementations separately or in sub-combination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination may in some cases be excised from the combination, and the claimed combination may be directed to a sub-combination or variation of a sub-combination.

[0148] A number of implementations have been described. Nevertheless, it will be understood that various modifications may be made without departing from the spirit and scope of the disclosure. Other implementations are within the scope of the following claims. For example, the memory modules and the memory sockets have been described as being dual in-line memory modules (DIMM) and DIMM sockets. However, the memory modules and memory sockets may have other types of form factors, such as single in-line memory modules (SIMM), for example.

Claims

CLAIMSWhat is claimed is:
1. A main memory comprising: a memory controller having one or more memory channel interfaces to couple to one or more respective memory channels; a memory channel having a memory channel bus coupled to one memory channel interface of the memory controller; and wherein the memory controller capable of controlling accesses to at least one dynamic random access memory module and at least one non-volatile memory module coupled to the memory channel bus.
2. The main memory of claim 1, wherein the memory controller is a programmable heterogeneous memory controller to flexibly adapt the memory channel interface to communicate with a memory module in response to the type of memory module being accessed.
3. The main memory of claim 1, wherein communication to the memory channel bus is specified in a standard specification, and the at least one non- volatile memory module is a translating memory module including a translator to translate standard specification data and instructions into data and instructions for a non-volatile memory integrated circuit.
4. The main memory of claim 2, wherein the programmable heterogeneous memory controller is packaged into an integrated circuit package with a processor compatible pinout to couple into a processor socket.
5. The main memory of claim 2, wherein the programmable heterogeneous memory controller is co-packaged into an integrated circuit package with a processor to couple into a processor socket.
6. The main memory of claim 1, wherein the channel further includes at least one socket coupled to the memory channel bus, the at least one socket capable of receiving the at least one dynamic random access memory module; and at least one other socket coupled to the memory channel bus, the at least one other socket capable of receiving the at least one non- volatile memory module.
7. The main memory of claim 6, wherein the memory channel bus includes one or more point to point wires independently coupled between the memory controller and each respective socket, and a plurality of bus wires coupled to the memory controller and every socket in the memory channel.
8. The main memory of claim 7, wherein one of the one or more point to point wires is assigned to be a feedback control signal from each memory module to the memory controller.
9. A computer system comprising: a printed circuit board including a plurality of traces; at least one processor coupled to some of the plurality of traces of the printed circuit board; a heterogeneous memory channel including a plurality of sockets coupled to a memory channel bus of the printed circuit board, the plurality of sockets to receive a plurality of different types of memory modules; and a memory controller coupled between the at least one processor and the heterogeneous memory channel, the memory controller to control access to the plurality of different types of memory modules in the heterogeneous memory channel.
10. The computer system of claim 9, wherein the memory controller is a programmable heterogeneous memory controller to flexibly adapt the memory channel bus to control access to each of the different types of memory modules in the heterogeneous memory channel.
11. The computer system of claim 9, wherein one memory module that is coupled to one socket in the heterogeneous memory channel is a random access memory module, and another memory module that is coupled to another socket in the heterogeneous memory channel is a non- volatile memory module.
12. The computer system of claim 11, wherein the random access memory module is a dynamic random access memory module.
13. The computer system of claim 11, wherein the random access memory module is a static random access memory module.
14. The computer system of claim 9, wherein the memory controller is an integrated memory controller integrated with at least one processor on a silicon die and coupled into a processor socket mounted to the printed circuit board.
15. The computer system of claim 9, wherein each of the plurality of different types of memory modules has a memory module identification to indicate the type of memory module coupled into the plurality of sockets of the heterogeneous memory channel.
16. A method of communicating to different types of memory modules in a memory channel, the method comprising: initializing a programmable heterogeneous memory controller to each memory module coupled to a memory channel bus; adapting each pin of a memory channel interface to communicate over wire interconnect of the memory channel bus to respective pins of each memory module in response to each different type of memory module being accessed; generating logic signals for communication over the wire interconnect of the memory channel bus to each memory module in response to each different type of memory module being accessed; and wherein the logic signals are generated on the wire interconnect of the memory channel bus with appropriate signal timing to communicate with each memory module in response to each different type of memory module being accessed.
17. The method of claim 16, further comprising: loading into the heterogeneous memory controller one or more memory module software drivers associated with the type of memory modules being accessed.
18. The method of claim 17, further comprising: downloading at least one of the one or more memory module software drivers over a network.
19. The method of claim 17, wherein in response to each different type of memory module being accessed, the one or more memory module software drivers each include information regarding the respective pins of the memory module, logic signals to communicate with the memory module, and signal timing to communicate with the memory module.
20. The method of claim 16, wherein the adapting of each pin includes assigning additional functionality to underused or unused pins so that a communication protocol between one or more memory modules and the programmable heterogeneous memory controller may be extended.
21. The method of claim 20, wherein address and control signal lines are used in a different manner to address additional memory to increase memory capacity.
22. The method of claim 20, wherein pre-existing address pins are used over multiple cycles to form a larger address to address additional memory and increase memory capacity.
23. The method of claim 20, wherein a feedback pin is defined so that the programmable heterogeneous memory controller can receive status information from the memory module.
24. The method of claim 16, wherein the generating of logic signals includes generating active high logic signals or active low logic signals in response to the type of memory module being accessed.
25. The method of claim 16, wherein the initializing of the programmable heterogeneous memory controller includes
polling each socket in the memory channel for a memory module; reading a memory module identification from each memory module to determine the type of memory module coupled into each socket; and loading a memory module software driver into the programmable heterogeneous memory controller for each different type of memory module coupled into the memory channel.
26. The method of claim 25, wherein the initializing of the programmable heterogeneous memory controller further includes
storing each memory module identifier associated with each socket into the programmable heterogeneous memory controller.
27. The method of claim 26, wherein the initializing of the programmable heterogeneous memory controller further includes
loading a state machine with the memory module software driver to access the memory module in a given socket.
28. A method of communicating with a non-volatile memory module in a memory channel, the method comprising: signaling to a non- volatile memory module to perform an operation; signaling back to a memory controller using a feedback status control signal to indicate that the non- volatile memory module is busy; waiting for the non-volatile memory module to finish the operation after the feedback status control signal indicates the non- volatile memory module is busy; and signaling back to the memory controller using the feedback status control signal to indicate that the non- volatile memory module is now ready to perform another operation.
29. The method of claim 28, wherein the operation the non-volatile memory module is signaled to perform is to erase a sector of non- volatile memory.
30. The method of claim 28, wherein the operation the non-volatile memory module is signaled to perform is to write a word or words of data into non- volatile memory.
31. The method of claim 28, wherein the feedback status control signal from the non- volatile memory module is coupled into the memory controller over a point-to-point wire interconnect in the memory channel bus.
32. The method of claim 28, further comprising: performing the operation into a first bank of non- volatile memory in the non-volatile memory module; and concurrently performing a read operation into a second bank of non- volatile memory in the non-volatile memory module while the operation is pending in the first bank of nonvolatile memory.
33. The method of claim 28, wherein the another operation is initiated by the memory controller to erase a sector of nonvolatile memory in the non- volatile memory module.
34. The method of claim 28, wherein the another operation is initiated by the memory controller to write a word of data into non-volatile memory in the non- volatile memory module.
35. The method of claim 28, further comprising: interrupting a processor to signal that the non-volatile memory module is ready for another operation.
36. A translating memory module comprising: a printed circuit board having a memory module form factor and an edge connector to couple to a socket of a pre-existing memory channel bus of a main memory; at least one memory integrated circuit coupled to the printed board, the at least one memory integrated circuit having memory to store and recall data and a first memory communication protocol to communicate data, address, and control signals to read and write data into the at least one memory integrated circuit; and at least one support chip coupled to the printed circuit board and coupled between the edge connector and the at least one memory integrated circuit, the at least one support chip including a bi-directional translator to translate between the first memory communication protocol for the at least one memory integrated circuit and a second memory communication protocol for the memory channel differing from the first memory communication protocol, the second memory communication protocol to communicate data, address, and control signals over the memory channel bus to read and write data into the memory of the translating memory module.
37. The translating memory module of claim 36, wherein the at least one support chip further includes a data transceiver coupled between the bi-directional translator and the edge connector, the data transceiver to bi-directionally interface the memory module to the memory channel bus and receive and transmit data on the memory channel bus using the second memory communication protocol, and an address and control receiver coupled between the bi-directional translator and the edge connector, the address and control receiver to interface the memory module to the memory channel bus and receive address and controls on the memory channel bus using the second memory communication protocol.
38. The translating memory module of claim 37, wherein the at least one memory integrated circuit is a non-double data rate two (non-DDR2) memory integrated circuit and the first memory communication protocol is a non-DDR2 memory communication protocol, the second memory communication protocol is a DDR2 memory communication protocol with DDR2 address, control, and data signaling, the data transceiver bi-directionally interfaces the memory module to the memory channel bus using DDR2 data signaling, and the address/control receiver receives DDR2 address signaling and DDR2 control signaling to interface the memory module to the memory channel bus.
39. The translating memory module of claim 36, wherein the at least one memory integrated circuit is an unconventional memory integrated circuit, and the at least one support chip includes the bi-directional translator to translate between the first memory communication protocol and the second memory communication protocol such that unconventional memory integrated circuit in the memory module may communicate to a pre-existing memory controller using the pre-existing memory channel bus.
40. The translating memory module of claim 39, wherein the unconventional memory integrated circuit is a non-volatile memory integrated circuit.
41. A memory module comprising: a printed circuit board having a memory module form factor and an edge connector to couple to a socket of a memory channel bus of a main memory; at least one memory integrated circuit coupled to the printed board, the at least one memory integrated circuit having memory to store and recall data; and at least one support chip coupled to the printed circuit board and coupled between the edge connector and the at least one memory integrated circuit, the at least one support chip including a memory module identification (MMID) to provided an identification of the type of memory module and the at least one memory integrated circuit.
42. The memory module of claim 41, wherein the memory module identification (MMID) to identify the memory module as a nonvolatile memory module and the at least one memory integrated circuit as at least one nonvolatile memory integrated circuit.
43. The memory module of claim 41, wherein the at least one support chip further including an input/output port coupled to the edge connector to form a communication port to communicate the memory module identification (MMID) to a memory controller.
44. The memory module of claim 43, wherein the input/output port is a serial input/output port and the communication port is a serial communication port to serially communicate the memory module identification (MMID) to the memory controller.
45. The memory module of claim 41, wherein the at least one support chip further including a register to store status information regarding the at least one memory integrated circuit, the register to communicate the status information to a memory controller over a memory channel bus in response to a request.
46. The memory module of claim 41, wherein the at least one support chip to receive status information from the at least one memory integrated circuit and generate a status flag for communication to a memory controller over a memory channel bus.
47. A programmable heterogeneous memory controller comprising: a processor interface to couple to a processor; and one or more memory channel controllers coupled to the processor interface and to one or more respective memory channels of a main memory, each of the one or more memory channel controllers including a memory channel interface to couple to a memory channel bus; a common memory module controller coupled to the memory channel interface and the processor interface, the common memory module controller to generate common control signals on the memory channel bus for a plurality of differing memory modules coupled into a respective plurality of memory module sockets; and a plurality of memory module controllers coupled to the memory channel interface and the processor interface, the plurality of memory module controllers to generate differing control signals for each of the plurality of differing memory modules coupled into the respective plurality of memory module sockets, each of the plurality of memory module controllers being programmable by a memory module software driver in response to the type of memory module coupled into the respective memory module socket.
48. The programmable heterogeneous memory controller of claim 47, wherein a non- volatile memory module is coupled into one memory module socket of a first memory channel bus coupled to a first memory chancel controller; a dynamic random access memory module is coupled into another memory module socket of the first memory channel bus; and the main memory is a heterogeneous main memory.
49. The programmable heterogeneous memory controller of claim 48, wherein a first memory module controller is programmed by a memory module software driver to generate first control signals for controlling the non- volatile memory module; and a second memory module controller is programmed by a different memory module software driver to generate second control signals for controlling the dynamic random access memory module.
50. The programmable heterogeneous memory controller of claim 48, wherein the common memory module controller generates common control signals on the first memory channel bus for the non-volatile memory module and the dynamic random access memory module.
51. A programmable heterogeneous memory controller comprising: a system interface to couple to a processor and allow access to a main memory; a memory interface with pins of one or more flexible input/output (I/O) ports, the memory interface to couple to different memory modules in sockets of one or more respective memory channels; and one or more input/output (I/O) state machines coupled between the system interface and the memory interface, the I/O state machines to program the pin configuration and generate logic signals for the pins of the memory interface in response to the type of memory module being accessed in a given socket and its respective memory module software driver.
52. The programmable heterogeneous memory controller of claim 51 , wherein a memory module software driver includes memory type, pin configuration, signal timing, and signal logic levels associated with a memory module identification of a memory module.
53. The programmable heterogeneous memory controller of claim 51, further comprising: an input/output (I/O) buffer coupled between the system interface and the one or more
VO state machines, the I/O buffer to buffer addresses, controls, and data received from a processor for the I/O state machine and to buffer data from the I/O state machine to be written out to a processor.
54. The programmable heterogeneous memory controller of claim 51 , further comprising: a flexible port controller coupled between the I/O state machine and the memory interface, the flexible port controller to select the functionality pins of the one or more flexible input/output (I/O) ports in response to the pin configuration.
55. The programmable heterogeneous memory controller of claim 51, further comprising: a memory module socket register coupled to the I/O state machine, the memory module socket register to store the memory module identification (ID) of each memory module plugged into each socket in each memory channel; a micro-coded memory coupled to the memory module socket register, the micro- coded memory to store the memory module software drivers for each different type of memory module indicated by the memory module socket register and supply memory module software drivers to the I/O state machine.
56. The programmable heterogeneous memory controller of claim 51 , wherein each of the one or more input/output (I/O) state machines include a memory channel state machine for each memory channel coupled to the programmable heterogeneous memory controller, each memory channel state machine includes one or more memory module state machines for each memory module and each rank of memory therein, wherein to read and write data over the memory channel bus into each memory module coupled thereto, the one or more memory module state machines to configure the memory interface with an appropriate pin out in response to the type of memory module being accessed, to generate appropriate logic levels of signals in response to the type of memory module being accessed, and to read and generate signals on the memory channel bus at the appropriate time in response to the type of memory module being accessed; a controller coupled to the one or more memory module state machines, the controller to control which one of the one or more memory module state machines is active; and a bus arbiter coupled to the controller and the one or more memory module state machines, the bus arbiter to arbitrate access by the one or more memory module state machines to the memory channel bus.
57. The programmable heterogeneous memory controller of claim 56, wherein the controller further to control what operational mode the one or more memory module state machines are operating in response to the type of memory access requested and the location in the memory channel of the memory module being accessed.
58. The programmable heterogeneous memory controller of claim 56, wherein the operational mode may be one of a read (R) access, a write (W) access, or an initialization/erasure (I).
59. The programmable heterogeneous memory controller of claim 56, wherein the location of the memory module is the socket into which the memory module is coupled.
PCT/US2007/080015 2006-09-28 2007-09-28 Systems, methods, and apparatus with programmable memory control for heterogeneous main memory WO2008040028A3 (en)

Priority Applications (8)

Application Number Priority Date Filing Date Title
US82742106 true 2006-09-28 2006-09-28
US60/827,421 2006-09-28
US86259706 true 2006-10-23 2006-10-23
US60/862,597 2006-10-23
US95668107 true 2007-08-17 2007-08-17
US60/956,681 2007-08-17
US11/864,763 2007-09-28
US11864763 US8051253B2 (en) 2006-09-28 2007-09-28 Systems and apparatus with programmable memory control for heterogeneous main memory

Publications (2)

Publication Number Publication Date
WO2008040028A2 true true WO2008040028A2 (en) 2008-04-03
WO2008040028A3 true WO2008040028A3 (en) 2008-10-23

Family

ID=39231035

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2007/080015 WO2008040028A3 (en) 2006-09-28 2007-09-28 Systems, methods, and apparatus with programmable memory control for heterogeneous main memory

Country Status (2)

Country Link
US (1) US8051253B2 (en)
WO (1) WO2008040028A3 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2010117878A1 (en) * 2009-04-08 2010-10-14 Google Inc. Command and interrupt grouping for a data storage device
US8239713B2 (en) 2009-04-08 2012-08-07 Google Inc. Data storage device with bad block scan command

Families Citing this family (49)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7761623B2 (en) * 2006-09-28 2010-07-20 Virident Systems, Inc. Main memory in a system with a memory controller configured to control access to non-volatile memory, and related technologies
US20080082750A1 (en) * 2006-09-28 2008-04-03 Okin Kenneth A Methods of communicating to, memory modules in a memory channel
US7761626B2 (en) * 2006-09-28 2010-07-20 Virident Systems, Inc. Methods for main memory in a system with a memory controller configured to control access to non-volatile memory, and related technologies
US7761625B2 (en) * 2006-09-28 2010-07-20 Virident Systems, Inc. Methods for main memory with non-volatile type memory modules, and related technologies
US7761624B2 (en) * 2006-09-28 2010-07-20 Virident Systems, Inc. Systems and apparatus for main memory with non-volatile type memory modules, and related technologies
US8074022B2 (en) * 2006-09-28 2011-12-06 Virident Systems, Inc. Programmable heterogeneous memory controllers for main memory with different memory modules
WO2008051940A3 (en) 2006-10-23 2008-08-14 Virident Systems Inc Methods and apparatus of dual inline memory modules for flash memory
US20080114924A1 (en) * 2006-11-13 2008-05-15 Jack Edward Frayer High bandwidth distributed computing solid state memory storage system
US8347005B2 (en) * 2007-07-31 2013-01-01 Hewlett-Packard Development Company, L.P. Memory controller with multi-protocol interface
US8230145B2 (en) * 2007-07-31 2012-07-24 Hewlett-Packard Development Company, L.P. Memory expansion blade for multiple architectures
US8589729B1 (en) * 2007-09-28 2013-11-19 Emc Corporation Data preservation system and method
US20090248919A1 (en) * 2008-03-25 2009-10-01 Jerzy Szwagrzyk Method for external fifo acceleration
US8745314B1 (en) 2008-06-24 2014-06-03 Virident Systems, Inc. Methods for a random read and read/write block accessible memory
US9513695B2 (en) 2008-06-24 2016-12-06 Virident Systems, Inc. Methods of managing power in network computer systems
JP2010282511A (en) * 2009-06-05 2010-12-16 Elpida Memory Inc Memory module and memory system including the same
US8295056B2 (en) * 2009-07-22 2012-10-23 International Business Machines Corporation Silicon carrier structure and method of forming same
WO2011087820A8 (en) * 2009-12-21 2012-03-22 Sanmina-Sci Corporation Method and apparatus for supporting storage modules in standard memory and/or hybrid memory bus architectures
JP5570619B2 (en) * 2010-02-23 2014-08-13 ラムバス・インコーポレーテッド Time division multiplexing at different speeds to access different memory types
US9448938B2 (en) * 2010-06-09 2016-09-20 Micron Technology, Inc. Cache coherence protocol for persistent memories
US8694737B2 (en) 2010-06-09 2014-04-08 Micron Technology, Inc. Persistent memory for processor main memory
US9063849B2 (en) 2010-09-17 2015-06-23 Aplus Flash Technology, Inc. Different types of memory integrated in one chip by using a novel protocol
US8613074B2 (en) 2010-09-30 2013-12-17 Micron Technology, Inc. Security protection for memory content of processor main memory
CN103946813B (en) 2011-09-30 2017-08-25 英特尔公司 Based on the generated usage statistics tracking far memory access signal
EP2761464A4 (en) 2011-09-30 2015-06-17 Intel Corp Apparatus and method for implementing a multi-level memory hierarchy having different operating modes
US9529708B2 (en) 2011-09-30 2016-12-27 Intel Corporation Apparatus for configuring partitions within phase change memory of tablet computer with integrated memory controller emulating mass storage to storage driver based on request from software
WO2013048491A1 (en) 2011-09-30 2013-04-04 Intel Corporation Apparatus, method and system that stores bios in non-volatile random access memory
US9600416B2 (en) 2011-09-30 2017-03-21 Intel Corporation Apparatus and method for implementing a multi-level memory hierarchy
EP2761480A4 (en) * 2011-09-30 2015-06-24 Intel Corp Apparatus and method for implementing a multi-level memory hierarchy over common memory channels
US9342453B2 (en) 2011-09-30 2016-05-17 Intel Corporation Memory channel that supports near memory and far memory access
CN103975287B (en) 2011-12-13 2017-04-12 英特尔公司 Enhanced support server system sleep states nonvolatile random access memory in
CN103999067A (en) 2011-12-21 2014-08-20 英特尔公司 High-performance storage structures and systems featuring multiple non-volatile memories
KR101572403B1 (en) 2011-12-22 2015-11-26 인텔 코포레이션 Power conservation by way of memory channel shutdown
CN103186178A (en) * 2011-12-29 2013-07-03 鸿富锦精密工业(深圳)有限公司 Main board
US20160342510A1 (en) * 2012-01-17 2016-11-24 Google Inc. Remote management of data planes and configuration of networking devices
US8554963B1 (en) 2012-03-23 2013-10-08 DSSD, Inc. Storage system with multicast DMA and unified address space
US9330736B2 (en) * 2012-11-09 2016-05-03 Qualcomm Incorporated Processor memory optimization via page access counting
US20140137119A1 (en) * 2012-11-15 2014-05-15 Elwha LLC, a limited liability corporation of the State of Delaware Multi-core processing in memory
US9323499B2 (en) 2012-11-15 2016-04-26 Elwha Llc Random number generator functions in memory
US9442854B2 (en) 2012-11-15 2016-09-13 Elwha Llc Memory circuitry including computational circuitry for performing supplemental functions
US9582465B2 (en) 2012-11-15 2017-02-28 Elwha Llc Flexible processors and flexible memory
US9218291B2 (en) * 2013-07-25 2015-12-22 International Business Machines Corporation Implementing selective cache injection
JP6165008B2 (en) * 2013-09-25 2017-07-19 キヤノン株式会社 Memory controller, a memory control method, information equipment, and program
GB201404173D0 (en) 2014-03-10 2014-04-23 Ibm Storage device with 2D configuration of phase change memory integrated circuits
US9367467B2 (en) * 2014-08-22 2016-06-14 Nvidia Corporation System and method for managing cache replacements
US9489136B2 (en) * 2014-10-27 2016-11-08 Facebook, Inc. Interrupt driven memory signaling
KR20170014567A (en) * 2015-07-30 2017-02-08 에스케이하이닉스 주식회사 Semiconductor device
WO2017065802A1 (en) * 2015-10-16 2017-04-20 Hewlett Packard Enterprise Development Lp Scrubbing data in a memory device
US9792224B2 (en) 2015-10-23 2017-10-17 Intel Corporation Reducing latency by persisting data relationships in relation to corresponding data in persistent memory
US9830086B2 (en) 2016-03-03 2017-11-28 Samsung Electronics Co., Ltd. Hybrid memory controller for arbitrating access to volatile and non-volatile memories in a hybrid memory group

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020118593A1 (en) * 2001-02-27 2002-08-29 Fujitsu Limited Memory system
US20020133684A1 (en) * 2001-01-17 2002-09-19 Honeywell International, Inc. Enhanced memory module architecture
US6970968B1 (en) * 1998-02-13 2005-11-29 Intel Corporation Memory module controller for providing an interface between a system memory controller and a plurality of memory devices on a memory module

Family Cites Families (66)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4757533A (en) * 1985-09-11 1988-07-12 Computer Security Corporation Security system for microcomputers
US5012408A (en) * 1990-03-15 1991-04-30 Digital Equipment Corporation Memory array addressing system for computer systems with multiple memory arrays
US5430859A (en) * 1991-07-26 1995-07-04 Sundisk Corporation Solid state memory system including plural memory chips and a serialized bus
US5224070A (en) * 1991-12-11 1993-06-29 Intel Corporation Apparatus for determining the conditions of programming circuitry used with flash EEPROM memory
US5375222A (en) * 1992-03-31 1994-12-20 Intel Corporation Flash memory card with a ready/busy mask register
US5404485A (en) * 1993-03-08 1995-04-04 M-Systems Flash Disk Pioneers Ltd. Flash file system
US7137011B1 (en) * 1993-09-01 2006-11-14 Sandisk Corporation Removable mother/daughter peripheral card
US5898857A (en) * 1994-12-13 1999-04-27 International Business Machines Corporation Method and system for interfacing an upgrade processor to a data processing system
US5701438A (en) * 1995-09-29 1997-12-23 Intel Corporation Logical relocation of memory based on memory device type
US5710733A (en) * 1996-01-22 1998-01-20 Silicon Graphics, Inc. Processor-inclusive memory module
US6564326B2 (en) * 1999-07-06 2003-05-13 Walter A. Helbig, Sr. Method and apparatus for enhancing computer system security
US6185704B1 (en) * 1997-04-11 2001-02-06 Texas Instruments Incorporated System signaling schemes for processor and memory module
US6336180B1 (en) * 1997-04-30 2002-01-01 Canon Kabushiki Kaisha Method, apparatus and system for managing virtual memory with virtual-physical mapping
US6446173B1 (en) * 1997-09-17 2002-09-03 Sony Corporation Memory controller in a multi-port bridge for a local area network
DE69836437D1 (en) * 1997-12-05 2006-12-28 Intel Corp Memory system with memory module with a memory module-tax modular
US20040236877A1 (en) * 1997-12-17 2004-11-25 Lee A. Burton Switch/network adapter port incorporating shared memory resources selectively accessible by a direct execution logic element and one or more dense logic devices in a fully buffered dual in-line memory module format (FB-DIMM)
US6207474B1 (en) * 1998-03-09 2001-03-27 Micron Technology, Inc. Method of forming a stack of packaged memory die and resulting apparatus
US6549959B1 (en) * 1999-08-30 2003-04-15 Ati International Srl Detecting modification to computer memory by a DMA device
US7702831B2 (en) * 2000-01-06 2010-04-20 Super Talent Electronics, Inc. Flash memory controller for electronic data flash card
US7017002B2 (en) * 2000-01-05 2006-03-21 Rambus, Inc. System featuring a master device, a buffer device and a plurality of integrated circuit memory devices
US7404032B2 (en) * 2000-01-05 2008-07-22 Rambus Inc. Configurable width buffered module having switch elements
JP3955712B2 (en) * 2000-03-03 2007-08-08 株式会社ルネサステクノロジ Semiconductor device
US6477598B1 (en) * 2000-07-20 2002-11-05 Lsi Logic Corporation Memory controller arbitrating RAS, CAS and bank precharge signals
US6785780B1 (en) * 2000-08-31 2004-08-31 Micron Technology, Inc. Distributed processor memory module and method
JP2002132402A (en) * 2000-10-20 2002-05-10 Mitsubishi Electric Corp Load adjusting board and data processor
US7034955B2 (en) * 2000-12-11 2006-04-25 Texas Instruments Incorporated Using a processor enhanced memory module to accelerate hardcopy image processing within existing printer controller
US6779049B2 (en) * 2000-12-14 2004-08-17 International Business Machines Corporation Symmetric multi-processing system with attached processing units being able to access a shared memory without being structurally configured with an address translation mechanism
WO2002057921A9 (en) * 2001-01-19 2004-05-13 Hitachi Ltd Electronic circuit device
EP1229549A1 (en) * 2001-02-01 2002-08-07 Alcatel Asynchronous flash-eeprom behaving like a synchronous ram/rom
US20020138600A1 (en) * 2001-03-26 2002-09-26 International Business Machines Corporation Method, apparatus and program for multi-machine network install using writeable media
US6629225B2 (en) * 2001-05-31 2003-09-30 Intel Corporation Method and apparatus for control calibration of multiple memory modules within a memory channel
US20030090879A1 (en) * 2001-06-14 2003-05-15 Doblar Drew G. Dual inline memory module
US6721195B2 (en) * 2001-07-12 2004-04-13 Micron Technology, Inc. Reversed memory module socket and motherboard incorporating same
US6707756B2 (en) * 2002-03-12 2004-03-16 Smart Modular Technologies, Inc. System and method for translation of SDRAM and DDR signals
US7096377B2 (en) * 2002-03-27 2006-08-22 Intel Corporation Method and apparatus for setting timing parameters
KR100929143B1 (en) * 2002-12-13 2009-12-01 삼성전자주식회사 Computer and its control method
KR100506062B1 (en) * 2002-12-18 2005-08-05 주식회사 하이닉스반도체 Composite Memory Device
JP3959039B2 (en) * 2003-02-28 2007-08-15 株式会社エヌ・ティ・ティ・ドコモ The image coding apparatus, image coding method, image encoding program, image decoding apparatus, image decoding method, and image decoding program
US6950919B2 (en) * 2003-03-26 2005-09-27 Hewlett-Packard Development Company, L.P. Computer system with operating system to dynamically adjust the main memory
DE10330593B4 (en) * 2003-07-07 2010-11-04 Qimonda Ag Integrated clock supply device for a memory module, memory module, which includes the integrated clock supply module, as well as methods for operating the memory module under test conditions
US7657706B2 (en) * 2003-12-18 2010-02-02 Cisco Technology, Inc. High speed memory and input/output processor subsystem for efficiently allocating and using high-speed memory and slower-speed memory
US7269708B2 (en) * 2004-04-20 2007-09-11 Rambus Inc. Memory controller for non-homogenous memory system
US20050251617A1 (en) * 2004-05-07 2005-11-10 Sinclair Alan W Hybrid non-volatile memory system
US7206915B2 (en) * 2004-06-03 2007-04-17 Emc Corp Virtual space manager for computer having a physical address extension feature
US7779215B2 (en) * 2004-06-24 2010-08-17 Via Technologies Inc. Method and related apparatus for accessing memory
US20060004953A1 (en) * 2004-06-30 2006-01-05 Vogt Pete D Method and apparatus for increased memory bandwidth
US7324352B2 (en) * 2004-09-03 2008-01-29 Staktek Group L.P. High capacity thin module system and method
US7613870B2 (en) * 2004-11-18 2009-11-03 International Business Machines Corporation Efficient memory usage in systems including volatile and high-density memories
US7212408B2 (en) * 2004-12-28 2007-05-01 Intel Corporation Multi-slot socket for mounting integrated circuits on circuit board
US20060195631A1 (en) * 2005-01-31 2006-08-31 Ramasubramanian Rajamani Memory buffers for merging local data from memory modules
US7702839B2 (en) * 2005-04-12 2010-04-20 Nokia Corporation Memory interface for volatile and non-volatile memory devices
US7464225B2 (en) * 2005-09-26 2008-12-09 Rambus Inc. Memory module including a plurality of integrated circuit memory devices and a plurality of buffer devices in a matrix topology
US7640386B2 (en) * 2006-05-24 2009-12-29 International Business Machines Corporation Systems and methods for providing memory modules with multiple hub devices
US7550834B2 (en) * 2006-06-29 2009-06-23 Sandisk Corporation Stacked, interconnected semiconductor packages
US7411757B2 (en) * 2006-07-27 2008-08-12 Hitachi Global Storage Technologies Netherlands B.V. Disk drive with nonvolatile memory having multiple modes of operation
WO2008014494A3 (en) * 2006-07-28 2008-11-06 Drc Comp Corp Fpga co-processor for accelerated computation
US8327104B2 (en) * 2006-07-31 2012-12-04 Google Inc. Adjusting the timing of signals associated with a memory system
US7761625B2 (en) * 2006-09-28 2010-07-20 Virident Systems, Inc. Methods for main memory with non-volatile type memory modules, and related technologies
US7761623B2 (en) * 2006-09-28 2010-07-20 Virident Systems, Inc. Main memory in a system with a memory controller configured to control access to non-volatile memory, and related technologies
US7761626B2 (en) * 2006-09-28 2010-07-20 Virident Systems, Inc. Methods for main memory in a system with a memory controller configured to control access to non-volatile memory, and related technologies
US20080082750A1 (en) * 2006-09-28 2008-04-03 Okin Kenneth A Methods of communicating to, memory modules in a memory channel
US7761624B2 (en) * 2006-09-28 2010-07-20 Virident Systems, Inc. Systems and apparatus for main memory with non-volatile type memory modules, and related technologies
US8074022B2 (en) * 2006-09-28 2011-12-06 Virident Systems, Inc. Programmable heterogeneous memory controllers for main memory with different memory modules
WO2008051940A3 (en) * 2006-10-23 2008-08-14 Virident Systems Inc Methods and apparatus of dual inline memory modules for flash memory
WO2009102821A3 (en) * 2008-02-12 2009-12-17 Virident Systems, Inc. Methods and apparatus for two-dimensional main memory
US8806116B2 (en) * 2008-02-12 2014-08-12 Virident Systems, Inc. Memory modules for two-dimensional main memory

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6970968B1 (en) * 1998-02-13 2005-11-29 Intel Corporation Memory module controller for providing an interface between a system memory controller and a plurality of memory devices on a memory module
US20020133684A1 (en) * 2001-01-17 2002-09-19 Honeywell International, Inc. Enhanced memory module architecture
US20020118593A1 (en) * 2001-02-27 2002-08-29 Fujitsu Limited Memory system

Cited By (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2010117878A1 (en) * 2009-04-08 2010-10-14 Google Inc. Command and interrupt grouping for a data storage device
WO2010117877A1 (en) * 2009-04-08 2010-10-14 Google Inc. Data storage device
US8205037B2 (en) 2009-04-08 2012-06-19 Google Inc. Data storage device capable of recognizing and controlling multiple types of memory chips operating at different voltages
US8239713B2 (en) 2009-04-08 2012-08-07 Google Inc. Data storage device with bad block scan command
US8239729B2 (en) 2009-04-08 2012-08-07 Google Inc. Data storage device with copy command
US8239724B2 (en) 2009-04-08 2012-08-07 Google Inc. Error correction for a data storage device
US8244962B2 (en) 2009-04-08 2012-08-14 Google Inc. Command processor for a data storage device
US8250271B2 (en) 2009-04-08 2012-08-21 Google Inc. Command and interrupt grouping for a data storage device
US8327220B2 (en) 2009-04-08 2012-12-04 Google Inc. Data storage device with verify on write command
US8380909B2 (en) 2009-04-08 2013-02-19 Google Inc. Multiple command queues having separate interrupts
US8433845B2 (en) 2009-04-08 2013-04-30 Google Inc. Data storage device which serializes memory device ready/busy signals
US8447918B2 (en) 2009-04-08 2013-05-21 Google Inc. Garbage collection for failure prediction and repartitioning
US8566507B2 (en) 2009-04-08 2013-10-22 Google Inc. Data storage device capable of recognizing and controlling multiple types of memory chips
US8566508B2 (en) 2009-04-08 2013-10-22 Google Inc. RAID configuration in a flash memory data storage device
US8578084B2 (en) 2009-04-08 2013-11-05 Google Inc. Data storage device having multiple removable memory boards
US8595572B2 (en) 2009-04-08 2013-11-26 Google Inc. Data storage device with metadata command
US8639871B2 (en) 2009-04-08 2014-01-28 Google Inc. Partitioning a flash memory data storage device
US9244842B2 (en) 2009-04-08 2016-01-26 Google Inc. Data storage device with copy command

Also Published As

Publication number Publication date Type
WO2008040028A3 (en) 2008-10-23 application
US8051253B2 (en) 2011-11-01 grant
US20080082766A1 (en) 2008-04-03 application

Similar Documents

Publication Publication Date Title
US7133960B1 (en) Logical to physical address mapping of chip selects
US6530007B2 (en) Method and apparatus for supporting heterogeneous memory in computer systems
US6108730A (en) Memory card adapter insertable into a motherboard memory card socket comprising a memory card receiving socket having the same configuration as the motherboard memory card socket
US5995405A (en) Memory module with flexible serial presence detect configuration
US6683372B1 (en) Memory expansion module with stacked memory packages and a serial storage unit
US5335329A (en) Apparatus for providing DMA functionality to devices located in a bus expansion chassis
US5938750A (en) Method and apparatus for a memory card bus design
US7194593B2 (en) Memory hub with integrated non-volatile memory
US20010000822A1 (en) Dynamic configuration of memory module using presence detect data
US6771526B2 (en) Method and apparatus for data transfer
US20090157950A1 (en) NAND flash module replacement for DRAM module
US20100250793A1 (en) Adjusting access of non-volatile semiconductor memory based on access time
US20050108469A1 (en) Buffered memory module with implicit to explicit memory command expansion
US5038320A (en) Computer system with automatic initialization of pluggable option cards
US5822251A (en) Expandable flash-memory mass-storage using shared buddy lines and intermediate flash-bus between device-specific buffers and flash-intelligent DMA controllers
US20050027928A1 (en) SDRAM memory device with an embedded NAND flash controller
US20100110748A1 (en) Hybrid volatile and non-volatile memory device
US6968419B1 (en) Memory module having a memory module controller controlling memory transactions for a plurality of memory devices
US7007130B1 (en) Memory system including a memory module having a memory module controller interfacing between a system memory controller and memory devices of the memory module
US6970968B1 (en) Memory module controller for providing an interface between a system memory controller and a plurality of memory devices on a memory module
US7277988B2 (en) System, method and storage medium for providing data caching and data compression in a memory subsystem
US20070013704A1 (en) Memory controller interface for micro-tiled memory access
US7389375B2 (en) System, method and storage medium for a multi-mode memory buffer device
US6446184B2 (en) Address re-mapping for memory module using presence detect data
US6209074B1 (en) Address re-mapping for memory module using presence detect data

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 07853700

Country of ref document: EP

Kind code of ref document: A2

NENP Non-entry into the national phase in:

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 07853700

Country of ref document: EP

Kind code of ref document: A2