USRE36191E - Configuration data loopback in a bus bridge circuit - Google Patents

Configuration data loopback in a bus bridge circuit Download PDF

Info

Publication number
USRE36191E
USRE36191E US08/772,015 US77201596A USRE36191E US RE36191 E USRE36191 E US RE36191E US 77201596 A US77201596 A US 77201596A US RE36191 E USRE36191 E US RE36191E
Authority
US
United States
Prior art keywords
bus
access cycle
circuit
over
address
Prior art date
Legal status (The legal status 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 status listed.)
Expired - Lifetime
Application number
US08/772,015
Inventor
Gary Solomon
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Intel Corp
Original Assignee
Intel Corp
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
Application filed by Intel Corp filed Critical Intel Corp
Priority to US08/772,015 priority Critical patent/USRE36191E/en
Application granted granted Critical
Publication of USRE36191E publication Critical patent/USRE36191E/en
Anticipated expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/38—Information transfer, e.g. on bus
    • G06F13/40—Bus structure
    • G06F13/4004—Coupling between buses
    • G06F13/4027—Coupling between buses using bus bridges

Definitions

  • This invention relates to the field of computer system architecture. More particularly, this invention relates to accessing configuration registers in a bus bridge circuit.
  • peripheral components such as disk drive controllers, network controllers, and graphics controllers, may be coupled to peripheral component buses separate from a host, or CPU bus.
  • peripheral component buses separate from a host, or CPU bus.
  • an intelligent peripheral component may have a local peripheral component bus.
  • the system may have more peripheral components than can be reliably placed on the host bus, due to electrical loading effects.
  • a host bridge circuit enables communication between the peripheral component bus and the host bus.
  • the host bridge circuit enables an access request that initiates on the host bus to have a destination on the peripheral component bus, and enables an access request that initiates on the peripheral component bus to have a destination on the host bus.
  • the host bridge circuit can also enable access to a shared resource from both buses.
  • the host bridge circuit contains a set of configuration registers that define parameters for processing access cycles between the buses, and for controlling the shared resource.
  • System I/O software performs reads and writes to the configuration registers in order to define the parameters.
  • the present method and apparatus reduces cost and complexity of devices for a bus bridge circuit by dividing address and data paths between separate devices to reduce pin count, and by looping back "bridged" configuration data to access configuration registers.
  • a method and apparatus for reducing cost and complexity of devices in a bus bridge circuit by dividing address and data paths between separate devices to reduce pin count, and by looping back "bridged" configuration data to access configuration registers.
  • the bridge circuit is comprised primarily of two integrated circuit devices: a cache DRAM controller (CDC), and a data path unit (DPU).
  • the host bridge circuit "bridges" all I/O accesses received over a host bus directly to a peripheral component bus without the need for any address decoding.
  • the CDC receives addresses for I/O accesses over an address portion of the host bus, and the DPU receives corresponding data for the I/O accesses over a data portion of the host bus.
  • the CDC also receives control signals over the host bus indicating an I/O access cycle.
  • the host bridge circuit To bridge I/O access cycles, the host bridge circuit translates the host bus I/O access cycles into I/O access cycles for the peripheral component bus.
  • the CDC generates an I/O access cycle on the peripheral component bus by assuming the role of bus initiator on the peripheral component bus, generating control signals indicating an I/O access cycle, and transferring the address received over the address portion of the host bus to the peripheral component bus.
  • the CDC also generates control signals, which cause the DPU to transfer data received over the data portion of the host bus to the peripheral component bus.
  • the host bridge circuit "bridges" the host bus I/O access cycles targeted for the configuration registers of the CDC.
  • the CDC bus initiator on the peripheral component bus initiates and drives the I/O access cycle targeted for the configuration registers.
  • the CDC also monitors the peripheral component bus as a bus target.
  • the CDC decodes the control signals on the peripheral component bus indicating an I/O access, and decodes the address transmitted on the peripheral component bus. If the address corresponds to a configuration register, the CDC receives the data as a target on the peripheral component bus.
  • the CDC is both initiator and target for the peripheral component bus I/O access cycle.
  • FIG. 1 illustrates an example computer system employing the teachings of the present invention, including a hierarchical arrangement of buses comprising a host bus, a host bridge circuit, a peripheral component bus, and an ISA bus.
  • FIG. 2 is a more detailed illustration of the host bridge circuit, which is comprised primarily of two integrated circuit devices: a cache DRAM controller (CDC), and a data path unit (DPU).
  • CDC cache DRAM controller
  • DPU data path unit
  • FIG. 3 shows the coupling of the host bridge circuit to the host bus and the memory bus, and shows the bus signals implemented on the peripheral component bus.
  • FIG. 4 illustrates the timing of an I/O write cycle targeted for a configuration register of the CDC.
  • the I/O write cycle originates on the host bus and is looped back over the peripheral component bus to the CDC.
  • a method and apparatus for reducing cost and complexity of devices in a bus bridge circuit by dividing address and data paths between separate devices to reduce pin count, and by looping back "bridged" configuration data to access configuration registers.
  • specific circuit devices, circuit architectures and components are set forth in order to provide a more thorough understanding of the present invention. However, it will be apparent to one skilled in the art that the present invention may be practiced without these specific details. In other instances, well known circuits and devices are shown in schematic form in order not to obscure the present invention unnecessarily.
  • FIG. 1 an example computer system employing the teachings of the present invention is illustrated.
  • a CPU 15 and a cache subsystem 16 are shown coupled for communication over a host bus 18.
  • the host bus 18 provides a 32 bit memory address space and a 16 bit I/O address space.
  • a host bridge circuit 30 enables communication between bus agents coupled to the host bus 18, and bus agents coupled to a peripheral component bus 19.
  • An ISA bridge circuit 35 enables communication between bus agents coupled to the peripheral component bus 19, and bus agents coupled to an ISA bus 20.
  • Peripheral components 40-42 are bus agents coupled for communication over the peripheral component bus 19.
  • the host bridge circuit 30 and the ISA bridge circuit 35 are coupled as bus agents for communication over the peripheral component bus 19.
  • the host bridge circuit 30 and the ISA bridge circuit 35 have the capability to be initiators and targets for access cycles over the peripheral component bus 19.
  • the peripheral component bus 19 comprises 32 bit memory address and 32 bit I/O address spaces, with the addresses and data multiplexed over the same bus lines.
  • a peripheral component bus consistent with the teachings of the present invention, refer to related U.S application Ser. No. 07/876,577, filed on Apr. 30, 1992, entitled A Signalling Protocol for a Peripheral Component Interconnect, and incorporated fully herein by reference.
  • Bridge circuits such as the host bridge circuit 30 and the ISA bridge circuit 35, are each coupled to a primary bus and a secondary bus.
  • a bridge circuit enables an access request that initiates on the primary bus to have a destination on the secondary bus, and enables an access request that initiates on the secondary bus to have a destination on the primary bus.
  • the host bridge circuit 30 receives access requests over the host bus 18, and initiates peripheral component bus 19 access requests to communicate with the peripheral components 40-42, and bus agents on the ISA bus 20 through the ISA bridge circuit 35. Also, the host bridge circuit 30 receives access requests over the peripheral component bus 19, and initiates host bus 18 access requests to communicate over the host bus 18.
  • the ISA bridge circuit 35 receives access requests over the ISA bus 20, and initiates peripheral component bus 19 access requests to communicate with the peripheral components 40-42, and the host bridge circuit 30. Also, the ISA bridge circuit 35 receives access requests over the peripheral component bus 19, and initiates ISA bus 20 access requests to communicate over the ISA bus 20.
  • the host bridge circuit 30 enables access to a shared DRAM subsystem 36.
  • the host bridge circuit 30 receives access requests for the DRAM subsystem 36 over the host bus 18, and the peripheral component bus 19.
  • Bus initiators coupled to the peripheral component bus 19 access the DRAM subsystem 36 by initiating an access cycle on the peripheral component bus 19, and by broadcasting an address within a range of addresses allocated to the DRAM subsystem 36.
  • the peripheral components 40-42, and the ISA bridge circuit 35 can each assume the role of bus initiator and access the DRAM subsystem 36 over the peripheral component bus 19, through the host bridge circuit 30.
  • FIG. 2 is a more detailed illustration of the host bridge circuit 30, which is comprised primarily of two integrated circuit devices: a cache DRAM controller (CDC) 41, and a data path unit (DPU) 42.
  • CDC cache DRAM controller
  • DPU data path unit
  • the CDC 41 is coupled to transfer addresses for memory and I/O accesses over the address portion of the host bus 18, and the DPU 42 is coupled to transfer data for memory and I/O access over the data portion of the host bus 18.
  • the CDC 41 is also coupled to transfer control signals over a control portion (not shown) of the host bus 18.
  • the CDC 41 is a full function initiator and target on she peripheral component bus 19.
  • the CDC 41 is coupled to transfer addresses, data and control signals for memory and I/O accesses over the peripheral component bus 19.
  • the DPU 42 is coupled to transfer data for memory and I/O accesses over the peripheral component bus 19.
  • the DPU 42 drives out the data during the data phase of the bus cycle.
  • the DPU 42 also receives data during the data phase of bus cycles over the peripheral component bus 19 when the host bridge circuit 30 is the target for the bus cycle.
  • the CDC 41 receives data during the data phase of bus cycles over the peripheral component bus 19 for internal configuration of the CDC 41.
  • the CDC 41 is a memory controller for the DRAM subsystem 36, and a cache controller for the cache subsystem 16.
  • the DPU 42 switches data flow through the host bridge circuit 30 according to control signals 51 received from the CDC 41.
  • the CDC 41 contains a set of configuration registers which define parameters for host bridge circuit 30 functions.
  • the CDC 41 contains registers defining a memory address mapping for the DRAM subsystems 36 and the cache subsystem 16, as well as control parameter information for the DRAM and cache controller of the CDC 41.
  • the CDC 41 also contains registers for controlling the bandwidth of burst accesses of the DRAM subsystem 36 over the peripheral component bus 19.
  • the CDC 41 and the DPU 42 enable dual port access to the DRAM subsystem 36 from the host bus 18 and the peripheral component bus 19.
  • the CPU 15, or another bus initiator coupled to the host bus 18 broadcasts a memory address over the address portion of the host bus 18 within the range of memory address mapped to the DRAM subsystem 36.
  • the CDC 41 receives the memory addresses over the address portion of the host bus 18. If the memory addresses are allocated to the DRAM subsystem 36, the CDC 41 issues control signals 51, which cause the DPU 42 to transfer data between the data portion of the host bus 18 and the DRAM subsystem 36.
  • control signals on the control bus of the host bus 18 indicated a read memory cycle
  • the control signals 51 cause the DPU 42 to read data from the DRAM subsystem 36 over the memory bus 22, and transfer the data over the data portion of the host bus 18.
  • the control signals on the control bus of the host bus 18 indicated a write memory cycle
  • the control signals 51 cause the DPU 42 to transfer data from the data portion of the host bus 18 to the DRAM subsystem 36.
  • bus initiators coupled to the peripheral component bus 19 access the DRAM subsystem 36 by initiating a memory access cycle on the peripheral component bus 19, and by broadcasting an address within a range of addresses mapped to the DRAM subsystem 36.
  • the CDC 41 receives the memory addresses over a multiplexed address/data portion (AD) of the peripheral component bus 19.
  • the AD portion of the peripheral component bus 19 has an address phase and a data phase. If the memory address broadcast in the address phase is allocated to the DRAM subsystem 36, the CDC 41 issues control signals 51, which cause the DPU 42 to transfer data between the DRAM subsystem 36 and the AD portion of the peripheral component bus 19 during the data phases.
  • control signals 51 cause the DPU 42 to read data from the DRAM subsystem 36 over the memory bus 22, and transfer the data over the peripheral component bus 19 during the data phase.
  • control signals 51 cause the DPU 42 to transfer data from the AD portion of the peripheral component bus 19 during the data phase to the DRAM subsystem 36.
  • the host bridge circuit 30 "bridges" all I/O accesses received over the host bus 18 directly to the peripheral component bus 19 without any address decoding.
  • the host bridge circuit 30 translates the host bus 18 I/O accesses into I/O accesses for the peripheral component bus 19.
  • the CDC 41 receives the addresses for I/O accesses over the address portion of the host bus 18, and the DPU 42 receives the corresponding data for the I/O accesses over the data portion of the host bus 18.
  • the CDC 41 also receives control signals over the host bus 18 indicating an I/O access cycle.
  • the host bridge circuit 30 generates corresponding I/O access cycles over the peripheral component bus 19.
  • the CDC 41 assumes the role of bus initiator on the peripheral component bus 19, generates control signals indicating an I/O access cycle on the peripheral component bus 19, and transfers the addresses for I/O accesses received over the address portion of the host bus 18 to the multiplexed AD portion of the peripheral component bus 19 during the address phase.
  • the CDC 41 generates control signals 51, which causes the DPU 42 to transfer data corresponding to the I/O accesses received over the data portion of the host bus 18 to the multiplexed AD portion of the peripheral component bus 19 during the data phase.
  • system I/O software executed by the CPU 15 controls the host bridge 30 functions by programming the configuration registers of the CDC 41.
  • the configuration registers of the CDC 41 are mapped to the I/O address space of the host bus 18.
  • the system I/O software allocates an address mapping for the DRAM subsystem 36 by programming the appropriate configuration registers in the CDC 41 using I/O write cycles over the host bus 18.
  • the host bridge circuit 30 "bridges" the host bus 18 I/O access cycles targeted for the configuration registers of the CDC 41 to the peripheral component bus 19 as corresponding I/O access cycles.
  • the CDC 41 bus initiator on the peripheral component bus 19 initiates and drives the I/O access cycle targeted for the configuration registers.
  • the CDC 41 also monitors the peripheral component bus 19 as a bus target.
  • the CDC 41 decodes the control signals on the peripheral component bus 19 indicating an I/O access or configuration space access, and decodes the address transmitted on the AD portion of the peripheral component bus 19 during the address phase. If the address corresponds to a configuration register of the CDC 41, then the CDC 41 receives the data as a target on the peripheral component bus 19.
  • the CDC 41 is both initiator and target for the peripheral component bus 19 I/O access cycle.
  • FIG. 3 shows the coupling of the host bridge circuit 30 to the host bus 18 and the memory bus 22, and shows the bus signals implemented on the peripheral component bus 19.
  • Bus signals 110 comprise the peripheral component bus 19. Addresses and data are multiplexed over the 32 AD bus lines.
  • the C/BE bus lines indicate bus command and byte enable information.
  • Basic control information is transferred over a FRAME#, a TRDY#, an IRDY#, a STOP#, and a LOCK# bus signal.
  • Bus arbitration and selection functions are provided by a REQ#, a GNT#, an IDSEL# and a DEVSEL# bus signal. Synchronization is provided by a CLK bus signal.
  • CLK clock signal
  • FIG. 4 illustrates the timing of an I/O write cycle targeted for a configuration register of the CDC 41.
  • the I/O write cycle originates on the host bus 18 and is looped back over the peripheral component bus 19 to the CDC 41.
  • I/O access cycles targeted for the configuration registers of the CDC 41 are generated by system I/O software executed by the CPU 15.
  • the host bridge circuit 30 translates the I/O write cycle on the host bus 18 into an I/O access or configuration space access cycle on the peripheral component bus 19, and the host bridge circuit 30 loops back the cycle on the peripheral component bus 19 into the appropriate configuration register of the CDC 41.
  • the I/O write cycle on the host bus 18 begins between times 1 and 2 when the CPU 15 transmits an address (ADDR) corresponding to an internal configuration register of the CDC 41, over the address portion of the host bus 18. Between times 2 and 3, the CPU 15 asserts an address strobe signal (ADS) indicating that a valid address is being transmitted over the address portion of the host bus 18. The CPU 15 also asserts control signals (not shown) over the host bus 18 indicating an I/O write cycle.
  • ADDR address corresponding to an internal configuration register of the CDC 41
  • the CPU 15 transmits the data (DATA) for the I/O write cycle over the data portion of the host bus 18.
  • the CDC 41 translates the I/O write cycle on the host bus 18 into an I/O write cycle on the peripheral component bus 19 by first asserting the FRAME# signal to indicate the start of an access cycle on the peripheral component bus 19.
  • the CDC 41 signals an I/O write cycle over the C/BE# signal lines of the peripheral component bus 19.
  • the CDC 41 transfers the address received over the address portion of the host bus 18 to the AD portion of the peripheral component bus 19 during the address phase.
  • the CDC 41 asserts the IRDY#signal between times 4 and 5, and the TRDY#signal between times 5 and 6 to signal both "initiator ready to send" and "target ready to receive” during the data phase portion of the peripheral component bus 19. Also between times 5 and 6, the CDC 41 issues control signals 51, which causes the DPU 42 to transfer the data received over the data portion of the host bus 18 to the AD portion of the peripheral component bus 19 during the data phase. The CDC 41 then transfers the data from the AD portion of the peripheral component bus 19 to the appropriate configuration register. Also between times 5 and 6, the CDC 41 asserts an RDY signal on the control portion of the host bus 18 to signal the CPU 15 that data for the I/O write cycle has been accepted.

Abstract

A method and apparatus for reducing cost and complexity of devices in a bus bridge circuit by dividing address and data paths between separate devices to reduce pin count, and by looping back "bridged" configuration data to access configuration registers. The host bridge circuit "bridges" all I/O accesses received over a host bus directly to a peripheral component bus without any decoding. The CDC is both initiator and target on the peripheral component bus for I/O access cycles generated by the host bridge circuit that are targeted for a host bridge configuration register.

Description

This is a continuation of U.S. application Ser. No. 07/894,108 filed Jun. 5, 1992, now abandoned.
BACKGROUND OF THE INVENTION
1. Field of the Invention
This invention relates to the field of computer system architecture. More particularly, this invention relates to accessing configuration registers in a bus bridge circuit.
2. Background
In a computer system, peripheral components, such as disk drive controllers, network controllers, and graphics controllers, may be coupled to peripheral component buses separate from a host, or CPU bus. There are several reasons a system might employ peripheral component buses. For example, it may be desirable to isolate slower speed devices from higher bandwidth buses and peripherals. Also, an intelligent peripheral component may have a local peripheral component bus. Moreover, the system may have more peripheral components than can be reliably placed on the host bus, due to electrical loading effects.
In such a system, a host bridge circuit enables communication between the peripheral component bus and the host bus. The host bridge circuit enables an access request that initiates on the host bus to have a destination on the peripheral component bus, and enables an access request that initiates on the peripheral component bus to have a destination on the host bus. The host bridge circuit can also enable access to a shared resource from both buses. Typically, the host bridge circuit contains a set of configuration registers that define parameters for processing access cycles between the buses, and for controlling the shared resource. System I/O software performs reads and writes to the configuration registers in order to define the parameters.
However, integrated circuit subsystems in the host bridge circuit require enough signal lines to communicate address, data, and control information for both the host bus and the peripheral component bus. The resulting large packages sizes of the integrated circuit devices greatly increases the system cost. Moreover, the host bridge devices must process memory accesses to the shared resource as well as I/O access of configuration registers, which increases the complexity of logic implemented in the host bridge devices.
As will be described, the present method and apparatus reduces cost and complexity of devices for a bus bridge circuit by dividing address and data paths between separate devices to reduce pin count, and by looping back "bridged" configuration data to access configuration registers.
SUMMARY OF THE INVENTION
A method and apparatus is disclosed for reducing cost and complexity of devices in a bus bridge circuit by dividing address and data paths between separate devices to reduce pin count, and by looping back "bridged" configuration data to access configuration registers. The bridge circuit is comprised primarily of two integrated circuit devices: a cache DRAM controller (CDC), and a data path unit (DPU).
The host bridge circuit "bridges" all I/O accesses received over a host bus directly to a peripheral component bus without the need for any address decoding. The CDC receives addresses for I/O accesses over an address portion of the host bus, and the DPU receives corresponding data for the I/O accesses over a data portion of the host bus. The CDC also receives control signals over the host bus indicating an I/O access cycle.
To bridge I/O access cycles, the host bridge circuit translates the host bus I/O access cycles into I/O access cycles for the peripheral component bus. The CDC generates an I/O access cycle on the peripheral component bus by assuming the role of bus initiator on the peripheral component bus, generating control signals indicating an I/O access cycle, and transferring the address received over the address portion of the host bus to the peripheral component bus. The CDC also generates control signals, which cause the DPU to transfer data received over the data portion of the host bus to the peripheral component bus.
To loop back configuration data, the host bridge circuit "bridges" the host bus I/O access cycles targeted for the configuration registers of the CDC. The CDC bus initiator on the peripheral component bus initiates and drives the I/O access cycle targeted for the configuration registers. However, the CDC also monitors the peripheral component bus as a bus target. The CDC decodes the control signals on the peripheral component bus indicating an I/O access, and decodes the address transmitted on the peripheral component bus. If the address corresponds to a configuration register, the CDC receives the data as a target on the peripheral component bus. Thus, for I/O access cycles generated by the host bridge circuit and targeted for a configuration register, the CDC is both initiator and target for the peripheral component bus I/O access cycle.
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 illustrates an example computer system employing the teachings of the present invention, including a hierarchical arrangement of buses comprising a host bus, a host bridge circuit, a peripheral component bus, and an ISA bus.
FIG. 2 is a more detailed illustration of the host bridge circuit, which is comprised primarily of two integrated circuit devices: a cache DRAM controller (CDC), and a data path unit (DPU).
FIG. 3 shows the coupling of the host bridge circuit to the host bus and the memory bus, and shows the bus signals implemented on the peripheral component bus.
FIG. 4 illustrates the timing of an I/O write cycle targeted for a configuration register of the CDC. The I/O write cycle originates on the host bus and is looped back over the peripheral component bus to the CDC.
DETAILED DESCRIPTION OF THE INVENTION
A method and apparatus is disclosed for reducing cost and complexity of devices in a bus bridge circuit by dividing address and data paths between separate devices to reduce pin count, and by looping back "bridged" configuration data to access configuration registers. In the following description, for purposes of explanation, specific circuit devices, circuit architectures and components are set forth in order to provide a more thorough understanding of the present invention. However, it will be apparent to one skilled in the art that the present invention may be practiced without these specific details. In other instances, well known circuits and devices are shown in schematic form in order not to obscure the present invention unnecessarily.
Referring now to FIG. 1, an example computer system employing the teachings of the present invention is illustrated. A CPU 15 and a cache subsystem 16 are shown coupled for communication over a host bus 18. In the current embodiment, the host bus 18 provides a 32 bit memory address space and a 16 bit I/O address space.
A host bridge circuit 30 enables communication between bus agents coupled to the host bus 18, and bus agents coupled to a peripheral component bus 19. An ISA bridge circuit 35 enables communication between bus agents coupled to the peripheral component bus 19, and bus agents coupled to an ISA bus 20.
Peripheral components 40-42 are bus agents coupled for communication over the peripheral component bus 19. In addition, the host bridge circuit 30 and the ISA bridge circuit 35 are coupled as bus agents for communication over the peripheral component bus 19. The host bridge circuit 30 and the ISA bridge circuit 35 have the capability to be initiators and targets for access cycles over the peripheral component bus 19.
In the current embodiment, the peripheral component bus 19 comprises 32 bit memory address and 32 bit I/O address spaces, with the addresses and data multiplexed over the same bus lines. For further discussion of a peripheral component bus consistent with the teachings of the present invention, refer to related U.S application Ser. No. 07/876,577, filed on Apr. 30, 1992, entitled A Signalling Protocol for a Peripheral Component Interconnect, and incorporated fully herein by reference.
Bridge circuits, such as the host bridge circuit 30 and the ISA bridge circuit 35, are each coupled to a primary bus and a secondary bus. A bridge circuit enables an access request that initiates on the primary bus to have a destination on the secondary bus, and enables an access request that initiates on the secondary bus to have a destination on the primary bus.
For example, the host bridge circuit 30 receives access requests over the host bus 18, and initiates peripheral component bus 19 access requests to communicate with the peripheral components 40-42, and bus agents on the ISA bus 20 through the ISA bridge circuit 35. Also, the host bridge circuit 30 receives access requests over the peripheral component bus 19, and initiates host bus 18 access requests to communicate over the host bus 18.
Similarly, the ISA bridge circuit 35 receives access requests over the ISA bus 20, and initiates peripheral component bus 19 access requests to communicate with the peripheral components 40-42, and the host bridge circuit 30. Also, the ISA bridge circuit 35 receives access requests over the peripheral component bus 19, and initiates ISA bus 20 access requests to communicate over the ISA bus 20.
In the current embodiment, the host bridge circuit 30 enables access to a shared DRAM subsystem 36. The host bridge circuit 30 receives access requests for the DRAM subsystem 36 over the host bus 18, and the peripheral component bus 19. Bus initiators coupled to the peripheral component bus 19 access the DRAM subsystem 36 by initiating an access cycle on the peripheral component bus 19, and by broadcasting an address within a range of addresses allocated to the DRAM subsystem 36. The peripheral components 40-42, and the ISA bridge circuit 35 can each assume the role of bus initiator and access the DRAM subsystem 36 over the peripheral component bus 19, through the host bridge circuit 30.
FIG. 2 is a more detailed illustration of the host bridge circuit 30, which is comprised primarily of two integrated circuit devices: a cache DRAM controller (CDC) 41, and a data path unit (DPU) 42. To reduce the number of pins for the CDC 41 and the DPU 42, the address and data paths of the host bus 18 are divided. The CDC 41 is coupled to transfer addresses for memory and I/O accesses over the address portion of the host bus 18, and the DPU 42 is coupled to transfer data for memory and I/O access over the data portion of the host bus 18. The CDC 41 is also coupled to transfer control signals over a control portion (not shown) of the host bus 18.
Moreover, the CDC 41 is a full function initiator and target on she peripheral component bus 19. The CDC 41 is coupled to transfer addresses, data and control signals for memory and I/O accesses over the peripheral component bus 19. The DPU 42 is coupled to transfer data for memory and I/O accesses over the peripheral component bus 19.
When the host bridge circuit 30 is the initiator for a bus cycle over the peripheral component bus 19, the DPU 42 drives out the data during the data phase of the bus cycle. The DPU 42 also receives data during the data phase of bus cycles over the peripheral component bus 19 when the host bridge circuit 30 is the target for the bus cycle. However, the CDC 41 receives data during the data phase of bus cycles over the peripheral component bus 19 for internal configuration of the CDC 41.
The CDC 41 is a memory controller for the DRAM subsystem 36, and a cache controller for the cache subsystem 16. The DPU 42 switches data flow through the host bridge circuit 30 according to control signals 51 received from the CDC 41.
The CDC 41 contains a set of configuration registers which define parameters for host bridge circuit 30 functions. For example, in the current embodiment, the CDC 41 contains registers defining a memory address mapping for the DRAM subsystems 36 and the cache subsystem 16, as well as control parameter information for the DRAM and cache controller of the CDC 41. The CDC 41 also contains registers for controlling the bandwidth of burst accesses of the DRAM subsystem 36 over the peripheral component bus 19.
The CDC 41 and the DPU 42 enable dual port access to the DRAM subsystem 36 from the host bus 18 and the peripheral component bus 19. To access the DRAM subsystem 36 over the host bus 18, the CPU 15, or another bus initiator coupled to the host bus 18, broadcasts a memory address over the address portion of the host bus 18 within the range of memory address mapped to the DRAM subsystem 36. The CDC 41 receives the memory addresses over the address portion of the host bus 18. If the memory addresses are allocated to the DRAM subsystem 36, the CDC 41 issues control signals 51, which cause the DPU 42 to transfer data between the data portion of the host bus 18 and the DRAM subsystem 36.
If the control signals on the control bus of the host bus 18 indicated a read memory cycle, then the control signals 51 cause the DPU 42 to read data from the DRAM subsystem 36 over the memory bus 22, and transfer the data over the data portion of the host bus 18. On the other hand, if the control signals on the control bus of the host bus 18 indicated a write memory cycle, then the control signals 51 cause the DPU 42 to transfer data from the data portion of the host bus 18 to the DRAM subsystem 36.
Similarly, bus initiators coupled to the peripheral component bus 19 access the DRAM subsystem 36 by initiating a memory access cycle on the peripheral component bus 19, and by broadcasting an address within a range of addresses mapped to the DRAM subsystem 36. The CDC 41 receives the memory addresses over a multiplexed address/data portion (AD) of the peripheral component bus 19. The AD portion of the peripheral component bus 19 has an address phase and a data phase. If the memory address broadcast in the address phase is allocated to the DRAM subsystem 36, the CDC 41 issues control signals 51, which cause the DPU 42 to transfer data between the DRAM subsystem 36 and the AD portion of the peripheral component bus 19 during the data phases.
During a memory read cycle on the peripheral component bus 19, the control signals 51 cause the DPU 42 to read data from the DRAM subsystem 36 over the memory bus 22, and transfer the data over the peripheral component bus 19 during the data phase. During a write memory cycle on the peripheral component bus 19, the control signals 51 cause the DPU 42 to transfer data from the AD portion of the peripheral component bus 19 during the data phase to the DRAM subsystem 36.
To reduce the complexity of logic implemented in the CDC 41 and the DPU 42, the host bridge circuit 30 "bridges" all I/O accesses received over the host bus 18 directly to the peripheral component bus 19 without any address decoding. The host bridge circuit 30 translates the host bus 18 I/O accesses into I/O accesses for the peripheral component bus 19.
To translate I/O accesses, the CDC 41 receives the addresses for I/O accesses over the address portion of the host bus 18, and the DPU 42 receives the corresponding data for the I/O accesses over the data portion of the host bus 18. The CDC 41 also receives control signals over the host bus 18 indicating an I/O access cycle.
The host bridge circuit 30 generates corresponding I/O access cycles over the peripheral component bus 19. To generate an I/O access cycle on the peripheral component bus 19, the CDC 41 assumes the role of bus initiator on the peripheral component bus 19, generates control signals indicating an I/O access cycle on the peripheral component bus 19, and transfers the addresses for I/O accesses received over the address portion of the host bus 18 to the multiplexed AD portion of the peripheral component bus 19 during the address phase. Also, the CDC 41 generates control signals 51, which causes the DPU 42 to transfer data corresponding to the I/O accesses received over the data portion of the host bus 18 to the multiplexed AD portion of the peripheral component bus 19 during the data phase.
In the current embodiment, system I/O software executed by the CPU 15 controls the host bridge 30 functions by programming the configuration registers of the CDC 41. In the current embodiment, the configuration registers of the CDC 41 are mapped to the I/O address space of the host bus 18. For example, the system I/O software allocates an address mapping for the DRAM subsystem 36 by programming the appropriate configuration registers in the CDC 41 using I/O write cycles over the host bus 18.
To loop back configuration data, the host bridge circuit 30 "bridges" the host bus 18 I/O access cycles targeted for the configuration registers of the CDC 41 to the peripheral component bus 19 as corresponding I/O access cycles. The CDC 41 bus initiator on the peripheral component bus 19 initiates and drives the I/O access cycle targeted for the configuration registers. However, the CDC 41 also monitors the peripheral component bus 19 as a bus target. The CDC 41 decodes the control signals on the peripheral component bus 19 indicating an I/O access or configuration space access, and decodes the address transmitted on the AD portion of the peripheral component bus 19 during the address phase. If the address corresponds to a configuration register of the CDC 41, then the CDC 41 receives the data as a target on the peripheral component bus 19. Thus, for I/O access cycles generated by the host bridge circuit 30 and targeted for a configuration register of the CDC 41, the CDC 41 is both initiator and target for the peripheral component bus 19 I/O access cycle.
FIG. 3 shows the coupling of the host bridge circuit 30 to the host bus 18 and the memory bus 22, and shows the bus signals implemented on the peripheral component bus 19. Bus signals 110 comprise the peripheral component bus 19. Addresses and data are multiplexed over the 32 AD bus lines. The C/BE bus lines indicate bus command and byte enable information. Basic control information is transferred over a FRAME#, a TRDY#, an IRDY#, a STOP#, and a LOCK# bus signal. Bus arbitration and selection functions are provided by a REQ#, a GNT#, an IDSEL# and a DEVSEL# bus signal. Synchronization is provided by a CLK bus signal. For a detailed description of these bus signals refer to related U.S. application Ser. No. 07/876,577, filed on Apr. 30, 1992, entitled A Signalling Protocol for a Peripheral Component Interconnect.
FIG. 4 illustrates the timing of an I/O write cycle targeted for a configuration register of the CDC 41. The I/O write cycle originates on the host bus 18 and is looped back over the peripheral component bus 19 to the CDC 41. In the current embodiment, I/O access cycles targeted for the configuration registers of the CDC 41 are generated by system I/O software executed by the CPU 15. The host bridge circuit 30 translates the I/O write cycle on the host bus 18 into an I/O access or configuration space access cycle on the peripheral component bus 19, and the host bridge circuit 30 loops back the cycle on the peripheral component bus 19 into the appropriate configuration register of the CDC 41.
The I/O write cycle on the host bus 18 begins between times 1 and 2 when the CPU 15 transmits an address (ADDR) corresponding to an internal configuration register of the CDC 41, over the address portion of the host bus 18. Between times 2 and 3, the CPU 15 asserts an address strobe signal (ADS) indicating that a valid address is being transmitted over the address portion of the host bus 18. The CPU 15 also asserts control signals (not shown) over the host bus 18 indicating an I/O write cycle.
Thereafter, between times 3 and 4, the CPU 15 transmits the data (DATA) for the I/O write cycle over the data portion of the host bus 18. The CDC 41 translates the I/O write cycle on the host bus 18 into an I/O write cycle on the peripheral component bus 19 by first asserting the FRAME# signal to indicate the start of an access cycle on the peripheral component bus 19. The CDC 41 signals an I/O write cycle over the C/BE# signal lines of the peripheral component bus 19. Also between times 3 and 4, the CDC 41 transfers the address received over the address portion of the host bus 18 to the AD portion of the peripheral component bus 19 during the address phase.
The CDC 41 asserts the IRDY#signal between times 4 and 5, and the TRDY#signal between times 5 and 6 to signal both "initiator ready to send" and "target ready to receive" during the data phase portion of the peripheral component bus 19. Also between times 5 and 6, the CDC 41 issues control signals 51, which causes the DPU 42 to transfer the data received over the data portion of the host bus 18 to the AD portion of the peripheral component bus 19 during the data phase. The CDC 41 then transfers the data from the AD portion of the peripheral component bus 19 to the appropriate configuration register. Also between times 5 and 6, the CDC 41 asserts an RDY signal on the control portion of the host bus 18 to signal the CPU 15 that data for the I/O write cycle has been accepted.
In the foregoing specification, the invention has been described with reference to specific exemplary embodiments thereof. It will, however, be evident that various modifications and changes may be made thereto without departing from the broader spirit and scope of the invention as set forth in the independent claims. The specification and drawings are accordingly to be regarded as an illustrative, rather than in a restrictive sense.

Claims (28)

What is claimed is:
1. A method for writing a configuration register in a bus bridge circuit, comprising the steps of:
sensing an access cycle on a first bus, and receiving an address over the first bus;
bridging the access cycle sensed on the first bus to an access cycle on a second bus by initiating the access cycle on the second bus and transmitting the address received over the first bus over the second bus without decoding the address received over the first bus:
sensing the access cycle on the second bus, and decoding the address present on the second bus;
receiving a data value over the first bus, the data value corresponding to the access cycle sensed on the first bus;
bridging the data value to the access cycle on the second bus by transmitting the data value received over the first bus over the second bus;
if the address decoded on the second bus selects the configuration register in the bus bridge circuit, then receiving the data value present on the second bus and storing the data value in the configuration register.
2. The method of claim 1, wherein the step of receiving an address over the first bus comprises the step of receiving the address over an address portion of the first bus.
3. The method of claim 2, wherein the step of transmitting the address received over the first bus over the second bus comprises the step of transmitting the address received over the first bus over the second bus during an address phase of the access cycle on the second bus.
4. The method of claim 3, wherein the step of decoding the address present on the second bus comprises the step of decoding the address present on the second bus during the address phase of the access cycle on the second bus.
5. The method of claim 4, wherein the step of bridging the data value to the access cycle on the second bus by transmitting the data value received over the first bus over the second bus comprises the step of transmitting the data value received over the first bus over the second bus during a data phase of the access cycle on the second bus.
6. The method of claim 5, wherein the step of receiving the data value present on the second bus comprises the step of receiving the data value present on the second bus during the data phase of the access cycle on the second bus.
7. A circuit for writing a configuration register in a bus bridge circuit, comprising:
circuit for sensing an access cycle on a first bus, and receiving an address over the first bus;
circuit for bridging the access cycle sensed on the first bus to an access cycle on a second bus by initiating the access cycle on the second bus and transmitting the address received over the first bus over the second bus without decoding the address received over the first bus:
circuit for sensing the access cycle on the second bus, and decoding the address present on the second bus;
circuit for receiving a data value over the first bus, the data value corresponding to the access cycle sensed on the first bus;
circuit for bridging the data value to the access cycle on the second bus by transmitting the data value received over the first bus over the second bus;
circuit for receiving the data value present on the second bus and storing the data value in the configuration register if the address decoded on the second bus selects the configuration register in the bus bridge circuit.
8. The circuit of claim 7, wherein the circuit for receiving an address over the first bus comprises circuit for receiving the address over an address portion of the first bus.
9. The circuit of claim 8, wherein the circuit for transmitting the address received over the first bus over the second bus comprises circuit for transmitting the address received over the first bus over the second during an address phase of the access cycle on the second bus.
10. The circuit of claim 9, wherein the circuit for decoding the address present on the second bus comprises circuit for decoding the address present on the second bus during the address phase of the access cycle on the second bus.
11. The circuit of claim 10, wherein the circuit for bridging the data value to the access cycle on the second bus by transmitting the data value received over the first bus over the second bus comprises circuit for transmitting the data value received over the first bus over the second bus during a data phase of the access cycle on the second bus.
12. The circuit of claim 11, wherein the circuit for receiving the data value present on the second bus comprises circuit for receiving the data value present on the second bus during the data phase of the access cycle on the second bus.
13. A bus bridge circuit, comprising:
control circuit containing at least one configuration register, the control circuit sensing an access cycle on a first bus, and receiving an address over the first bus, the control circuit bridging the access cycle sensed on the first bus to an access cycle on a second bus by initiating the access cycle on the second bus and transmitting the address received over the first bus over the second bus without decoding the address received over the first bus, the control circuit also sensing the access cycle on the second bus, and decoding the address present on the second bus, the control circuit receiving a data value present on the second bus and storing the data value in the configuration register if the address on the second bus selects the configuration register in the bus bridge circuit;
data path circuit receiving the data value over the first bus, the data value corresponding to the access cycle sensed on the first bus, the data path circuit bridging the data value to the access cycle on the second bus by transmitting the data value received over the first bus over the second bus.
14. The bus bridge circuit of claim 13, wherein the control circuit transmits the address received over the first bus over the second bus during an address phase of the access cycle on the second bus.
15. The bus bridge circuit of claim 14, wherein the control circuit decodes the address present on the second bus during the address phase of the access cycle on the second bus.
16. The bus bridge circuit of claim 15, wherein the data path circuit transmits the data value received over the first bus over the second bus during a data phase of the access cycle on the second bus.
17. The bus bridge circuit of claim 16, wherein the control circuit receives the data value present on the second bus during the data phase of the access cycle on the second bus.
18. A computer system, comprising:
central processing means coupled for communication over a first bus;
memory subsystem comprising dynamic random access memory;
a plurality of peripheral components coupled for communication over a second bus;
bus bridge circuit coupled to the memory subsystem and coupled for communication over the first bus and the second bus, the bus bridge circuit enabling access to the memory subsystem from the first bus and the second bus, the bridge circuit containing at least one configuration register for controlling the memory subsystem, the bus bridge circuit enabling a write access to the configuration register by translating an access cycle received over the first bus and targeted for the configuration register into an access cycle on the second bus targeted for the configuration register and writing the configuration register according to the access cycle on the second bus.
19. The computer system of claim 18, wherein the bus bridge circuit comprises:
circuit for sensing the access cycle on the first bus, and receiving an address over the first bus;
circuit for bridging the access cycle sensed on the first bus to an access cycle on a second bus by initiating the access cycle on the second bus and transmitting the address received over the first bus over the second bus without decoding the address received over the first bus;
circuit for sensing the access cycle on the second bus, and decoding the address present on the second bus;
circuit for receiving a data value over the first bus, the data value corresponding to the access cycle sensed on the first bus;
circuit for bridging the data value to the access cycle on the second bus by transmitting the data value received over the first bus over the second bus;
circuit for receiving the data value present on the second bus and storing the data value in the configuration register if the address decoded on the second bus selects the configuration register.
20. The computer system of claim 19, wherein the circuit for receiving an address over the first bus comprises circuit for receiving the address over an address portion of the first bus.
21. The computer system of claim 20, wherein the circuit for transmitting the address received over the first bus over the second bus comprises circuit for transmitting the address received over the first bus over the second bus during an address phase of the access cycle on the second bus.
22. The computer system of claim 21, wherein the circuit for decoding the address present on the second bus comprises circuit for decoding the address present on the second bus during the address phase of the access cycle on the second bus.
23. The computer system of claim 22, wherein the circuit for bridging the data value to the access cycle on the second bus by transmitting the data value received over the first bus over the second bus comprises circuit for transmitting the data value received over the first bus over the second bus during a data phase of the access cycle on the second bus.
24. The computer system of claim 23, wherein the circuit for receiving the data value present on the second bus comprises circuit for receiving the data value present on the second bus during the data phase of the access cycle on the second bus. .Iadd.
25. A bus bridge for coupling between a first bus and a second bus to allow communication between the first bus and the second bus, comprising:
a configuration register; and
a circuit coupled to the configuration register that generates an access cycle transmitted on the second bus and targeted for the configuration register in response to an access cycle received from the first bus, wherein the circuit receives the access cycle from the second bus such that the bus bridge is both initiator and target of the access cycle on the second bus..Iaddend..Iadd.26. A bus bridge for coupling between a first bus and a second bus to allow communication between the first bus and the second bus, comprising:
first means for generating an access cycle transmitted on the second bus and targeted for the bus bridge in response to receiving an access cycle from the first bus; and
second means coupled to the second bus for receiving the access cycle transmitted on the second bus such that the bus bridge is both initiator and target of the access cycle transmitted on the second bus..Iaddend..Iadd.27. A bus bridge for coupling between a first bus and a second bus to allow communication between the first bus and the second bus, comprising:
a configuration register;
first means for generating an access cycle transmitted on the second bus and targeted for the configuration register in response to receiving an access cycle from the first bus; and
second means coupled to the second bus for receiving the access cycle transmitted on the second bus such that the bus bridge is both initiator and target of the access cycle transmitted on the second
bus..Iaddend..Iadd.28. A bus bridge for coupling between a first bus and a second bus to allow communication between the first bus and the second bus, comprising:
a configuration register; and
a first circuit for coupling to address lines of the first bus and to the second bus, the first circuit generating an access cycle transmitted on the second bus and targeted for the configuration register in response to receiving an access cycle from the first bus, the first circuit receiving the second access cycle such that the bus bridge is both initiator and target of the second access cycle..Iaddend..Iadd.29. A method for accessing a configuration register of a bus bridge that couples a first bus to a second bus to enable communication between the first bus and the second bus, the method comprising:
the bus bridge receiving a first access cycle from the first bus;
the bus bridge generating and transmitting a second access cycle targeted for the configuration register on the second bus in response to receiving the first access cycle; and
the bus bridge receiving the second access cycle such that the bus bridge is both initiator and target of the second access cycle..Iaddend..Iadd.30. A bus bridge for coupling between a first bus and a second bus to allow communication between the first bus and the second bus, comprising:
a configuration register; and
a circuit coupled to the configuration register that translates a first access cycle received from the first bus into a second access cycle transmitted on the second bus and targeted for the configuration register, wherein the circuit receives the second access cycle such that the bus bridge is both initiator and target of the second access
cycle..Iaddend..Iadd.31. The bus bridge circuit of claim 30, wherein the configuration register is only accessible from the second bus..Iaddend..Iadd.32. A bus bridge for coupling between a first bus and a second bus to allow communication between the first bus and the second bus, comprising:
first means for translating a first access cycle received from the first bus and targeted for the bus bridge into a second access cycle transmitted on the second bus and targeted for the bus bridge; and
second means coupled to the second bus for receiving the second access cycle such that the bus bridge is both initiator and target of the second access cycle..Iaddend..Iadd.33. A bus bridge for coupling between a first bus and a second bus to allow communication between the first bus and the second bus, comprising:
a configuration register;
first means for translating a first access cycle received from the first bus into a second access cycle transmitted on the second bus and targeted for the configuration register; and
second means coupled to the configuration register and the second bus for receiving the second access cycle such that the bus bridge is both
initiator and target of the second access cycle..Iaddend..Iadd.34. The bus bridge of claim 33, wherein the configuration register is only accessible from the second bus..Iaddend..Iadd.35. The bus bridge of claim 33, wherein the second means is further for accessing the configuration register in response to the second access cycle..Iaddend..Iadd.36. A bus bridge for coupling between a first bus and a second bus to allow communication between the first bus and the second bus, comprising:
a first circuit for coupling to address lines of the first bus and to the second bus, the first circuit translating a first access cycle received from the first bus and targeted for the bus bridge into a second access cycle transmitted on the second bus and targeted for the bus bridge; and
a second circuit coupled to the first circuit for coupling to data lines of the first bus and to the second bus, the second circuit passing data associated with the first access cycle to the second bus in response to a control signal received from the first circuit, wherein the first circuit receives the data such that the bus bridge is both initiator and target of the second access cycle..Iaddend..Iadd.37. A bus bridge for coupling between a first bus and a second bus to allow communication between the first bus and the second bus, comprising:
a configuration register; and
a first circuit coupled to the configuration register and for coupling to address lines of the first bus and to the second bus, the first circuit translating a first access cycle received from the first bus into a second access cycle transmitted on the second bus and targeted for the configuration register, the first circuit receiving the second access cycle such that the bus bridge is both initiator and target of the second access cycle..Iaddend..Iadd.38. The bus bridge of claim 37, further comprising:
a second circuit coupled to the first circuit for coupling to data lines of the first bus and to the second bus, the second circuit passing data associated with the first access cycle to the second bus in response to a control signal received from the first circuit, wherein the first circuit receiving the second access cycle and the data such that the bus bridge is both initiator and target of the second access cycle..Iaddend..Iadd.39. The bus bridge of claim 37, wherein the configuration register is only accessible from the second bus..Iaddend..Iadd.40. A method for accessing a configuration register of a bus bridge that couples a first bus to a second bus to enable communication between the first bus and the second bus, the method comprising:
the bus bridge receiving a first access cycle targeted for the configuration register from the first bus;
the bus bridge translating the first access cycle into a second access cycle targeted for the configuration register and transmitted on the second bus; and
the bus bridge receiving the second access cycle such that the bus bridge is both initiator and target of the second access cycle..Iaddend.
US08/772,015 1992-06-05 1996-12-19 Configuration data loopback in a bus bridge circuit Expired - Lifetime USRE36191E (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US08/772,015 USRE36191E (en) 1992-06-05 1996-12-19 Configuration data loopback in a bus bridge circuit

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US89410892A 1992-06-05 1992-06-05
US08/126,111 US5379384A (en) 1992-06-05 1993-09-23 Configuration data loopback in a bus bridge circuit
US08/772,015 USRE36191E (en) 1992-06-05 1996-12-19 Configuration data loopback in a bus bridge circuit

Related Parent Applications (2)

Application Number Title Priority Date Filing Date
US89410892A Continuation 1992-06-05 1992-06-05
US08/126,111 Reissue US5379384A (en) 1992-06-05 1993-09-23 Configuration data loopback in a bus bridge circuit

Publications (1)

Publication Number Publication Date
USRE36191E true USRE36191E (en) 1999-04-20

Family

ID=25402619

Family Applications (2)

Application Number Title Priority Date Filing Date
US08/126,111 Ceased US5379384A (en) 1992-06-05 1993-09-23 Configuration data loopback in a bus bridge circuit
US08/772,015 Expired - Lifetime USRE36191E (en) 1992-06-05 1996-12-19 Configuration data loopback in a bus bridge circuit

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US08/126,111 Ceased US5379384A (en) 1992-06-05 1993-09-23 Configuration data loopback in a bus bridge circuit

Country Status (1)

Country Link
US (2) US5379384A (en)

Cited By (55)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6542953B2 (en) * 1997-11-19 2003-04-01 Micron Technology, Inc. Method for configuring peer-to-peer bus bridges in a computer system using shadow configuration registers
US20070167874A1 (en) * 2002-04-19 2007-07-19 Dominique Freeman Method and apparatus for penetrating tissue
US7481776B2 (en) 2002-04-19 2009-01-27 Pelikan Technologies, Inc. Method and apparatus for penetrating tissue
US7582063B2 (en) 2000-11-21 2009-09-01 Pelikan Technologies, Inc. Blood testing apparatus having a rotatable cartridge with multiple lancing elements and testing means
US7648468B2 (en) 2002-04-19 2010-01-19 Pelikon Technologies, Inc. Method and apparatus for penetrating tissue
US7666149B2 (en) 1997-12-04 2010-02-23 Peliken Technologies, Inc. Cassette of lancet cartridges for sampling blood
US7674232B2 (en) 2002-04-19 2010-03-09 Pelikan Technologies, Inc. Method and apparatus for penetrating tissue
US7682318B2 (en) 2001-06-12 2010-03-23 Pelikan Technologies, Inc. Blood sampling apparatus and method
US7699791B2 (en) 2001-06-12 2010-04-20 Pelikan Technologies, Inc. Method and apparatus for improving success rate of blood yield from a fingerstick
US7713214B2 (en) 2002-04-19 2010-05-11 Pelikan Technologies, Inc. Method and apparatus for a multi-use body fluid sampling device with optical analyte sensing
US7717863B2 (en) 2002-04-19 2010-05-18 Pelikan Technologies, Inc. Method and apparatus for penetrating tissue
US7731729B2 (en) 2002-04-19 2010-06-08 Pelikan Technologies, Inc. Method and apparatus for penetrating tissue
US7822454B1 (en) 2005-01-03 2010-10-26 Pelikan Technologies, Inc. Fluid sampling device with improved analyte detecting member configuration
US7833171B2 (en) 2002-04-19 2010-11-16 Pelikan Technologies, Inc. Method and apparatus for penetrating tissue
US7841992B2 (en) 2001-06-12 2010-11-30 Pelikan Technologies, Inc. Tissue penetration device
US7850621B2 (en) 2003-06-06 2010-12-14 Pelikan Technologies, Inc. Method and apparatus for body fluid sampling and analyte sensing
US7862520B2 (en) 2002-04-19 2011-01-04 Pelikan Technologies, Inc. Body fluid sampling module with a continuous compression tissue interface surface
US7874994B2 (en) 2002-04-19 2011-01-25 Pelikan Technologies, Inc. Method and apparatus for penetrating tissue
US7892183B2 (en) 2002-04-19 2011-02-22 Pelikan Technologies, Inc. Method and apparatus for body fluid sampling and analyte sensing
US7901362B2 (en) 2002-04-19 2011-03-08 Pelikan Technologies, Inc. Method and apparatus for penetrating tissue
US7909778B2 (en) 2002-04-19 2011-03-22 Pelikan Technologies, Inc. Method and apparatus for penetrating tissue
US7909775B2 (en) 2001-06-12 2011-03-22 Pelikan Technologies, Inc. Method and apparatus for lancet launching device integrated onto a blood-sampling cartridge
US7909777B2 (en) 2002-04-19 2011-03-22 Pelikan Technologies, Inc Method and apparatus for penetrating tissue
US7959582B2 (en) 2002-04-19 2011-06-14 Pelikan Technologies, Inc. Method and apparatus for penetrating tissue
US7976476B2 (en) 2002-04-19 2011-07-12 Pelikan Technologies, Inc. Device and method for variable speed lancet
US7988645B2 (en) 2001-06-12 2011-08-02 Pelikan Technologies, Inc. Self optimizing lancing device with adaptation means to temporal variations in cutaneous properties
US8007446B2 (en) 2002-04-19 2011-08-30 Pelikan Technologies, Inc. Method and apparatus for penetrating tissue
US8079960B2 (en) 2002-04-19 2011-12-20 Pelikan Technologies, Inc. Methods and apparatus for lancet actuation
US8197421B2 (en) 2002-04-19 2012-06-12 Pelikan Technologies, Inc. Method and apparatus for penetrating tissue
US8221334B2 (en) 2002-04-19 2012-07-17 Sanofi-Aventis Deutschland Gmbh Method and apparatus for penetrating tissue
US8267870B2 (en) 2002-04-19 2012-09-18 Sanofi-Aventis Deutschland Gmbh Method and apparatus for body fluid sampling with hybrid actuation
US8282576B2 (en) 2003-09-29 2012-10-09 Sanofi-Aventis Deutschland Gmbh Method and apparatus for an improved sample capture device
US8333710B2 (en) 2002-04-19 2012-12-18 Sanofi-Aventis Deutschland Gmbh Tissue penetration device
US8435190B2 (en) 2002-04-19 2013-05-07 Sanofi-Aventis Deutschland Gmbh Method and apparatus for penetrating tissue
US8439872B2 (en) 1998-03-30 2013-05-14 Sanofi-Aventis Deutschland Gmbh Apparatus and method for penetration with shaft having a sensor for sensing penetration depth
US8652831B2 (en) 2004-12-30 2014-02-18 Sanofi-Aventis Deutschland Gmbh Method and apparatus for analyte measurement test time
US8668656B2 (en) 2003-12-31 2014-03-11 Sanofi-Aventis Deutschland Gmbh Method and apparatus for improving fluidic flow and sample capture
US8702624B2 (en) 2006-09-29 2014-04-22 Sanofi-Aventis Deutschland Gmbh Analyte measurement device with a single shot actuator
US8721671B2 (en) 2001-06-12 2014-05-13 Sanofi-Aventis Deutschland Gmbh Electric lancet actuator
US8828203B2 (en) 2004-05-20 2014-09-09 Sanofi-Aventis Deutschland Gmbh Printable hydrogels for biosensors
US8965476B2 (en) 2010-04-16 2015-02-24 Sanofi-Aventis Deutschland Gmbh Tissue penetration device
US9034639B2 (en) 2002-12-30 2015-05-19 Sanofi-Aventis Deutschland Gmbh Method and apparatus using optical techniques to measure analyte levels
US9072842B2 (en) 2002-04-19 2015-07-07 Sanofi-Aventis Deutschland Gmbh Method and apparatus for penetrating tissue
US9144401B2 (en) 2003-06-11 2015-09-29 Sanofi-Aventis Deutschland Gmbh Low pain penetrating member
US9226699B2 (en) 2002-04-19 2016-01-05 Sanofi-Aventis Deutschland Gmbh Body fluid sampling module with a continuous compression tissue interface surface
US9248267B2 (en) 2002-04-19 2016-02-02 Sanofi-Aventis Deustchland Gmbh Tissue penetration device
US9314194B2 (en) 2002-04-19 2016-04-19 Sanofi-Aventis Deutschland Gmbh Tissue penetration device
US9351680B2 (en) 2003-10-14 2016-05-31 Sanofi-Aventis Deutschland Gmbh Method and apparatus for a variable user interface
US9375169B2 (en) 2009-01-30 2016-06-28 Sanofi-Aventis Deutschland Gmbh Cam drive for managing disposable penetrating member actions with a single motor and motor and control system
US9386944B2 (en) 2008-04-11 2016-07-12 Sanofi-Aventis Deutschland Gmbh Method and apparatus for analyte detecting device
US9427532B2 (en) 2001-06-12 2016-08-30 Sanofi-Aventis Deutschland Gmbh Tissue penetration device
US9560993B2 (en) 2001-11-21 2017-02-07 Sanofi-Aventis Deutschland Gmbh Blood testing apparatus having a rotatable cartridge with multiple lancing elements and testing means
US9795747B2 (en) 2010-06-02 2017-10-24 Sanofi-Aventis Deutschland Gmbh Methods and apparatus for lancet actuation
US9820684B2 (en) 2004-06-03 2017-11-21 Sanofi-Aventis Deutschland Gmbh Method and apparatus for a fluid sampling device
US9839386B2 (en) 2002-04-19 2017-12-12 Sanofi-Aventis Deustschland Gmbh Body fluid sampling device with capacitive sensor

Families Citing this family (71)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3411300B2 (en) * 1992-02-18 2003-05-26 株式会社日立製作所 Information processing device
US5574869A (en) * 1992-03-30 1996-11-12 Intel Corporation Bus bridge circuit having configuration space enable register for controlling transition between various modes by writing the bridge identifier into CSE register
TW276312B (en) * 1992-10-20 1996-05-21 Cirrlis Logic Inc
US6311286B1 (en) * 1993-04-30 2001-10-30 Nec Corporation Symmetric multiprocessing system with unified environment and distributed system functions
US5542055A (en) * 1993-05-28 1996-07-30 International Business Machines Corp. System for counting the number of peripheral buses in each hierarch connected to primary bus for creating map of peripheral buses to locate peripheral devices
US5522050A (en) * 1993-05-28 1996-05-28 International Business Machines Corporation Bus-to-bus bridge for a multiple bus information handling system that optimizes data transfers between a system bus and a peripheral bus
US5799161A (en) * 1993-06-25 1998-08-25 Intel Corporation Method and apparatus for concurrent data routing
US5872945A (en) * 1993-07-26 1999-02-16 Intel Corporation MX bus translation to new system bus protocol
US5594874A (en) * 1993-09-30 1997-01-14 Cirrus Logic, Inc. Automatic bus setting, sensing and switching interface unit
US5568621A (en) * 1993-11-10 1996-10-22 Compaq Computer Corporation Cached subtractive decode addressing on a computer bus
US5613075A (en) * 1993-11-12 1997-03-18 Intel Corporation Method and apparatus for providing deterministic read access to main memory in a computer system
US5519872A (en) * 1993-12-30 1996-05-21 Intel Corporation Fast address latch with automatic address incrementing
US5533200A (en) * 1994-03-18 1996-07-02 Intel Corporation Method and apparatus for transmission of signals over a shared line
US5696917A (en) * 1994-06-03 1997-12-09 Intel Corporation Method and apparatus for performing burst read operations in an asynchronous nonvolatile memory
EP0692764B1 (en) * 1994-06-17 2000-08-09 Advanced Micro Devices, Inc. Memory throttle for PCI master
JP3454294B2 (en) * 1994-06-20 2003-10-06 インターナショナル・ビジネス・マシーンズ・コーポレーション Multiple bus information processing system and bridge circuit
US5794014A (en) * 1994-06-27 1998-08-11 Cirrus Logic, Inc. Method and apparatus for interfacing between peripherals of multiple formats and a single system bus
US5727184A (en) * 1994-06-27 1998-03-10 Cirrus Logic, Inc. Method and apparatus for interfacing between peripherals of multiple formats and a single system bus
WO1996003697A1 (en) * 1994-07-21 1996-02-08 Apple Computer, Inc. Method for semaphore communication between incompatible bus locking architectures
US5623610A (en) * 1994-10-31 1997-04-22 Intel Corporation System for assigning geographical addresses in a hierarchical serial bus by enabling upstream port and selectively enabling disabled ports at power on/reset
US5615404A (en) * 1994-10-31 1997-03-25 Intel Corporation System having independently addressable bus interfaces coupled to serially connected multi-ported signal distributors generating and maintaining frame based polling schedule favoring isochronous peripherals
US5742847A (en) * 1994-10-31 1998-04-21 Intel Corporation M&A for dynamically generating and maintaining frame based polling schedules for polling isochronous and asynchronous functions that guaranty latencies and bandwidths to the isochronous functions
US5621901A (en) * 1994-10-31 1997-04-15 Intel Corporation Method and apparatus for serial bus elements of an hierarchical serial bus assembly to electrically represent data and control states to each other
AU703388B2 (en) * 1994-10-31 1999-03-25 Intel Corporation Method and apparatus for exchanging data, status and commands over an hierarchical serial bus assembly using communication packets
US5790831A (en) * 1994-11-01 1998-08-04 Opti Inc. VL-bus/PCI-bus bridge
US5561820A (en) * 1994-11-30 1996-10-01 International Business Machines Corporation Bridge for interfacing buses in computer system with a direct memory access controller having dynamically configurable direct memory access channels
US5568619A (en) * 1995-01-05 1996-10-22 International Business Machines Corporation Method and apparatus for configuring a bus-to-bus bridge
US5630094A (en) * 1995-01-20 1997-05-13 Intel Corporation Integrated bus bridge and memory controller that enables data streaming to a shared memory of a computer system using snoop ahead transactions
US6212589B1 (en) * 1995-01-27 2001-04-03 Intel Corporation System resource arbitration mechanism for a host bridge
US5737748A (en) * 1995-03-15 1998-04-07 Texas Instruments Incorporated Microprocessor unit having a first level write-through cache memory and a smaller second-level write-back cache memory
US5608877A (en) * 1995-03-24 1997-03-04 Cirrus Logic, Inc. Reset based computer bus identification method and circuit resilient to power transience
US5799207A (en) * 1995-03-28 1998-08-25 Industrial Technology Research Institute Non-blocking peripheral access architecture having a register configure to indicate a path selection for data transfer between a master, memory, and an I/O device
US5664152A (en) * 1995-06-06 1997-09-02 Hewlett-Packard Company Multiple segmenting of main memory to streamline data paths in a computing system
US5978860A (en) * 1995-06-07 1999-11-02 Dell Usa, L.P. System and method for disabling and re-enabling at least one peripheral device in a computer system by masking a device-configuration-space-access-signal with a disable or re-enable signal
US5734847A (en) * 1995-06-15 1998-03-31 Intel Corporation Method and apparatus for enabling intelligent I/O subsystems using PCI I/O devices
US5848249A (en) * 1995-06-15 1998-12-08 Intel Corporation Method and apparatus for enabling intelligent I/O subsystems using PCI I/O devices
EP0834135B1 (en) * 1995-06-15 2003-01-02 Intel Corporation Architecture for an i/o processor that integrates a pci to pci bridge
KR0147703B1 (en) * 1995-06-30 1998-09-15 김주용 Layout circuit for plug/play in pci bus
US5933613A (en) * 1995-07-06 1999-08-03 Hitachi, Ltd. Computer system and inter-bus control circuit
JP3531368B2 (en) * 1995-07-06 2004-05-31 株式会社日立製作所 Computer system and inter-bus control circuit
US5729705A (en) * 1995-07-24 1998-03-17 Symbios Logic Inc. Method and apparatus for enhancing throughput of disk array data transfers in a controller
US5734848A (en) * 1995-07-24 1998-03-31 Symbios Logic Inc. Method and appartus for transferring data in a controller having centralized memory
US5873114A (en) * 1995-08-18 1999-02-16 Advanced Micro Devices, Inc. Integrated processor and memory control unit including refresh queue logic for refreshing DRAM during idle cycles
US5781747A (en) * 1995-11-14 1998-07-14 Mesa Ridge Technologies, Inc. Method and apparatus for extending the signal path of a peripheral component interconnect bus to a remote location
US5715476A (en) * 1995-12-29 1998-02-03 Intel Corporation Method and apparatus for controlling linear and toggle mode burst access sequences using toggle mode increment logic
US5790814A (en) * 1996-01-23 1998-08-04 Dell U.S.A., L.P. Technique for supporting semi-compliant PCI devices behind a PCI-to-PCI bridge
US5640570A (en) * 1996-01-26 1997-06-17 International Business Machines Corporation Information handling system for transmitting contents of line register from asynchronous controller to shadow register in another asynchronous controller determined by shadow register address buffer
US5778194A (en) * 1996-04-08 1998-07-07 Symbios, Inc. Method and apparatus for measuring performance of a computer bus
US5937174A (en) * 1996-06-28 1999-08-10 Lsi Logic Corporation Scalable hierarchial memory structure for high data bandwidth raid applications
US5881254A (en) * 1996-06-28 1999-03-09 Lsi Logic Corporation Inter-bus bridge circuit with integrated memory port
US5748918A (en) * 1996-06-28 1998-05-05 Intel Corporation Method and apparatus for supporting two subtractive decode agents on the same bus in a computer system
US5887144A (en) * 1996-11-20 1999-03-23 International Business Machines Corp. Method and system for increasing the load and expansion capabilities of a bus through the use of in-line switches
US5761461A (en) * 1996-12-13 1998-06-02 International Business Machines Corporation Method and system for preventing peripheral component interconnect (PCI) peer-to-peer access across multiple PCI host bridges within a data processing system
US5761462A (en) * 1996-12-13 1998-06-02 International Business Machines Corporation Method and system for supporting peripheral component interconnect (PCI) peer-to-peer access across multiple PCI host bridges within a data-processing system
US5867728A (en) * 1996-12-17 1999-02-02 Compaq Computer Corp. Preventing corruption in a multiple processor computer system during a peripheral device configuration cycle
US6052133A (en) * 1997-06-27 2000-04-18 S3 Incorporated Multi-function controller and method for a computer graphics display system
US6442632B1 (en) 1997-09-05 2002-08-27 Intel Corporation System resource arbitration mechanism for a host bridge
GB9720811D0 (en) * 1997-09-30 1997-12-03 Sgs Thomson Microelectronics Dual port buffer
US6484065B1 (en) * 1997-12-29 2002-11-19 Kawasaki Microelectronics, Inc. DRAM enhanced processor
GB2334415A (en) * 1998-02-13 1999-08-18 Motorola Ltd Interfacing multiplexed and non- multiplexed busses
US6122677A (en) * 1998-03-20 2000-09-19 Micron Technology, Inc. Method of shortening boot uptime in a computer system
US6233638B1 (en) 1998-03-20 2001-05-15 Micron Electronics, Inc. System for configuring peer devices
US6360289B2 (en) * 1998-04-14 2002-03-19 Micron Technology, Inc. System for autonomous configuration of peer devices
US6266770B1 (en) 1998-04-14 2001-07-24 Micron Technology, Inc. Method for autonomous configuration of peer devices
US6119191A (en) * 1998-09-01 2000-09-12 International Business Machines Corporation Performing PCI access cycles through PCI bridge hub routing
US6243810B1 (en) * 1998-11-25 2001-06-05 Intel Corporation Method and apparatus for communicating a configuration sequence throughout an integrated circuit chip
US6385703B1 (en) * 1998-12-03 2002-05-07 Intel Corporation Speculative request pointer advance for fast back-to-back reads
US6401151B1 (en) * 1999-06-07 2002-06-04 Micron Technology, Inc. Method for configuring bus architecture through software control
US6425029B1 (en) * 1999-06-07 2002-07-23 Micron Technology, Inc. Apparatus for configuring bus architecture through software control
JP2001282704A (en) * 2000-03-31 2001-10-12 Fujitsu Ltd Device, method and system for processing data
KR20020032136A (en) * 2000-10-25 2002-05-03 박성훈 Large capacity auxiliary storage device using memory

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4864496A (en) * 1987-09-04 1989-09-05 Digital Equipment Corporation Bus adapter module for interconnecting busses in a multibus computer system
US4958271A (en) * 1984-12-07 1990-09-18 Nec Corporation Transfer control equipment
US4975838A (en) * 1986-04-09 1990-12-04 Hitachi, Ltd. Duplex data processing system with programmable bus configuration
US5029074A (en) * 1987-06-29 1991-07-02 Digital Equipment Corporation Bus adapter unit for digital processing system
US5083260A (en) * 1988-02-29 1992-01-21 Pfu Limited Bus arbitration system for concurrent use of a system bus by more than one device

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4958271A (en) * 1984-12-07 1990-09-18 Nec Corporation Transfer control equipment
US4975838A (en) * 1986-04-09 1990-12-04 Hitachi, Ltd. Duplex data processing system with programmable bus configuration
US5029074A (en) * 1987-06-29 1991-07-02 Digital Equipment Corporation Bus adapter unit for digital processing system
US4864496A (en) * 1987-09-04 1989-09-05 Digital Equipment Corporation Bus adapter module for interconnecting busses in a multibus computer system
US5083260A (en) * 1988-02-29 1992-01-21 Pfu Limited Bus arbitration system for concurrent use of a system bus by more than one device

Cited By (105)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6587868B2 (en) * 1997-11-19 2003-07-01 Micron Technology, Inc. Computer system having peer-to-peer bus bridges and shadow configuration registers
US6542953B2 (en) * 1997-11-19 2003-04-01 Micron Technology, Inc. Method for configuring peer-to-peer bus bridges in a computer system using shadow configuration registers
US7666149B2 (en) 1997-12-04 2010-02-23 Peliken Technologies, Inc. Cassette of lancet cartridges for sampling blood
US8439872B2 (en) 1998-03-30 2013-05-14 Sanofi-Aventis Deutschland Gmbh Apparatus and method for penetration with shaft having a sensor for sensing penetration depth
US7582063B2 (en) 2000-11-21 2009-09-01 Pelikan Technologies, Inc. Blood testing apparatus having a rotatable cartridge with multiple lancing elements and testing means
US7850622B2 (en) 2001-06-12 2010-12-14 Pelikan Technologies, Inc. Tissue penetration device
US8382683B2 (en) 2001-06-12 2013-02-26 Sanofi-Aventis Deutschland Gmbh Tissue penetration device
US9427532B2 (en) 2001-06-12 2016-08-30 Sanofi-Aventis Deutschland Gmbh Tissue penetration device
US7682318B2 (en) 2001-06-12 2010-03-23 Pelikan Technologies, Inc. Blood sampling apparatus and method
US7699791B2 (en) 2001-06-12 2010-04-20 Pelikan Technologies, Inc. Method and apparatus for improving success rate of blood yield from a fingerstick
US8845550B2 (en) 2001-06-12 2014-09-30 Sanofi-Aventis Deutschland Gmbh Tissue penetration device
US8721671B2 (en) 2001-06-12 2014-05-13 Sanofi-Aventis Deutschland Gmbh Electric lancet actuator
US8679033B2 (en) 2001-06-12 2014-03-25 Sanofi-Aventis Deutschland Gmbh Tissue penetration device
US8641643B2 (en) 2001-06-12 2014-02-04 Sanofi-Aventis Deutschland Gmbh Sampling module device and method
US8622930B2 (en) 2001-06-12 2014-01-07 Sanofi-Aventis Deutschland Gmbh Tissue penetration device
US7841992B2 (en) 2001-06-12 2010-11-30 Pelikan Technologies, Inc. Tissue penetration device
US7988645B2 (en) 2001-06-12 2011-08-02 Pelikan Technologies, Inc. Self optimizing lancing device with adaptation means to temporal variations in cutaneous properties
US9694144B2 (en) 2001-06-12 2017-07-04 Sanofi-Aventis Deutschland Gmbh Sampling module device and method
US8016774B2 (en) 2001-06-12 2011-09-13 Pelikan Technologies, Inc. Tissue penetration device
US8360991B2 (en) 2001-06-12 2013-01-29 Sanofi-Aventis Deutschland Gmbh Tissue penetration device
US8343075B2 (en) 2001-06-12 2013-01-01 Sanofi-Aventis Deutschland Gmbh Tissue penetration device
US9802007B2 (en) 2001-06-12 2017-10-31 Sanofi-Aventis Deutschland Gmbh Methods and apparatus for lancet actuation
US8282577B2 (en) 2001-06-12 2012-10-09 Sanofi-Aventis Deutschland Gmbh Method and apparatus for lancet launching device integrated onto a blood-sampling cartridge
US7909775B2 (en) 2001-06-12 2011-03-22 Pelikan Technologies, Inc. Method and apparatus for lancet launching device integrated onto a blood-sampling cartridge
US8216154B2 (en) 2001-06-12 2012-07-10 Sanofi-Aventis Deutschland Gmbh Tissue penetration device
US8211037B2 (en) 2001-06-12 2012-07-03 Pelikan Technologies, Inc. Tissue penetration device
US8206319B2 (en) 2001-06-12 2012-06-26 Sanofi-Aventis Deutschland Gmbh Tissue penetration device
US8206317B2 (en) 2001-06-12 2012-06-26 Sanofi-Aventis Deutschland Gmbh Tissue penetration device
US8162853B2 (en) 2001-06-12 2012-04-24 Pelikan Technologies, Inc. Tissue penetration device
US8123700B2 (en) 2001-06-12 2012-02-28 Pelikan Technologies, Inc. Method and apparatus for lancet launching device integrated onto a blood-sampling cartridge
US7981055B2 (en) 2001-06-12 2011-07-19 Pelikan Technologies, Inc. Tissue penetration device
US9560993B2 (en) 2001-11-21 2017-02-07 Sanofi-Aventis Deutschland Gmbh Blood testing apparatus having a rotatable cartridge with multiple lancing elements and testing means
US8333710B2 (en) 2002-04-19 2012-12-18 Sanofi-Aventis Deutschland Gmbh Tissue penetration device
US8403864B2 (en) 2002-04-19 2013-03-26 Sanofi-Aventis Deutschland Gmbh Method and apparatus for penetrating tissue
US8007446B2 (en) 2002-04-19 2011-08-30 Pelikan Technologies, Inc. Method and apparatus for penetrating tissue
US7981056B2 (en) 2002-04-19 2011-07-19 Pelikan Technologies, Inc. Methods and apparatus for lancet actuation
US8062231B2 (en) 2002-04-19 2011-11-22 Pelikan Technologies, Inc. Method and apparatus for penetrating tissue
US8079960B2 (en) 2002-04-19 2011-12-20 Pelikan Technologies, Inc. Methods and apparatus for lancet actuation
US7976476B2 (en) 2002-04-19 2011-07-12 Pelikan Technologies, Inc. Device and method for variable speed lancet
US7959582B2 (en) 2002-04-19 2011-06-14 Pelikan Technologies, Inc. Method and apparatus for penetrating tissue
US8197423B2 (en) 2002-04-19 2012-06-12 Pelikan Technologies, Inc. Method and apparatus for penetrating tissue
US8197421B2 (en) 2002-04-19 2012-06-12 Pelikan Technologies, Inc. Method and apparatus for penetrating tissue
US8202231B2 (en) 2002-04-19 2012-06-19 Sanofi-Aventis Deutschland Gmbh Method and apparatus for penetrating tissue
US7938787B2 (en) 2002-04-19 2011-05-10 Pelikan Technologies, Inc. Method and apparatus for penetrating tissue
US7914465B2 (en) 2002-04-19 2011-03-29 Pelikan Technologies, Inc. Method and apparatus for penetrating tissue
US7909774B2 (en) 2002-04-19 2011-03-22 Pelikan Technologies, Inc. Method and apparatus for penetrating tissue
US7909777B2 (en) 2002-04-19 2011-03-22 Pelikan Technologies, Inc Method and apparatus for penetrating tissue
US8221334B2 (en) 2002-04-19 2012-07-17 Sanofi-Aventis Deutschland Gmbh Method and apparatus for penetrating tissue
US7674232B2 (en) 2002-04-19 2010-03-09 Pelikan Technologies, Inc. Method and apparatus for penetrating tissue
US8267870B2 (en) 2002-04-19 2012-09-18 Sanofi-Aventis Deutschland Gmbh Method and apparatus for body fluid sampling with hybrid actuation
US7988644B2 (en) 2002-04-19 2011-08-02 Pelikan Technologies, Inc. Method and apparatus for a multi-use body fluid sampling device with sterility barrier release
US7909778B2 (en) 2002-04-19 2011-03-22 Pelikan Technologies, Inc. Method and apparatus for penetrating tissue
US9248267B2 (en) 2002-04-19 2016-02-02 Sanofi-Aventis Deustchland Gmbh Tissue penetration device
US7901362B2 (en) 2002-04-19 2011-03-08 Pelikan Technologies, Inc. Method and apparatus for penetrating tissue
US8337420B2 (en) 2002-04-19 2012-12-25 Sanofi-Aventis Deutschland Gmbh Tissue penetration device
US8337419B2 (en) 2002-04-19 2012-12-25 Sanofi-Aventis Deutschland Gmbh Tissue penetration device
US7892183B2 (en) 2002-04-19 2011-02-22 Pelikan Technologies, Inc. Method and apparatus for body fluid sampling and analyte sensing
US7874994B2 (en) 2002-04-19 2011-01-25 Pelikan Technologies, Inc. Method and apparatus for penetrating tissue
US8382682B2 (en) 2002-04-19 2013-02-26 Sanofi-Aventis Deutschland Gmbh Method and apparatus for penetrating tissue
US7862520B2 (en) 2002-04-19 2011-01-04 Pelikan Technologies, Inc. Body fluid sampling module with a continuous compression tissue interface surface
US8388551B2 (en) 2002-04-19 2013-03-05 Sanofi-Aventis Deutschland Gmbh Method and apparatus for multi-use body fluid sampling device with sterility barrier release
US9314194B2 (en) 2002-04-19 2016-04-19 Sanofi-Aventis Deutschland Gmbh Tissue penetration device
US8414503B2 (en) 2002-04-19 2013-04-09 Sanofi-Aventis Deutschland Gmbh Methods and apparatus for lancet actuation
US8430828B2 (en) 2002-04-19 2013-04-30 Sanofi-Aventis Deutschland Gmbh Method and apparatus for a multi-use body fluid sampling device with sterility barrier release
US8435190B2 (en) 2002-04-19 2013-05-07 Sanofi-Aventis Deutschland Gmbh Method and apparatus for penetrating tissue
US9226699B2 (en) 2002-04-19 2016-01-05 Sanofi-Aventis Deutschland Gmbh Body fluid sampling module with a continuous compression tissue interface surface
US8579831B2 (en) 2002-04-19 2013-11-12 Sanofi-Aventis Deutschland Gmbh Method and apparatus for penetrating tissue
US7833171B2 (en) 2002-04-19 2010-11-16 Pelikan Technologies, Inc. Method and apparatus for penetrating tissue
US9839386B2 (en) 2002-04-19 2017-12-12 Sanofi-Aventis Deustschland Gmbh Body fluid sampling device with capacitive sensor
US20070167874A1 (en) * 2002-04-19 2007-07-19 Dominique Freeman Method and apparatus for penetrating tissue
US9795334B2 (en) 2002-04-19 2017-10-24 Sanofi-Aventis Deutschland Gmbh Method and apparatus for penetrating tissue
US7731729B2 (en) 2002-04-19 2010-06-08 Pelikan Technologies, Inc. Method and apparatus for penetrating tissue
US8690796B2 (en) 2002-04-19 2014-04-08 Sanofi-Aventis Deutschland Gmbh Method and apparatus for penetrating tissue
US9724021B2 (en) 2002-04-19 2017-08-08 Sanofi-Aventis Deutschland Gmbh Method and apparatus for penetrating tissue
US7717863B2 (en) 2002-04-19 2010-05-18 Pelikan Technologies, Inc. Method and apparatus for penetrating tissue
US7481776B2 (en) 2002-04-19 2009-01-27 Pelikan Technologies, Inc. Method and apparatus for penetrating tissue
US7713214B2 (en) 2002-04-19 2010-05-11 Pelikan Technologies, Inc. Method and apparatus for a multi-use body fluid sampling device with optical analyte sensing
US8905945B2 (en) 2002-04-19 2014-12-09 Dominique M. Freeman Method and apparatus for penetrating tissue
US7648468B2 (en) 2002-04-19 2010-01-19 Pelikon Technologies, Inc. Method and apparatus for penetrating tissue
US9498160B2 (en) 2002-04-19 2016-11-22 Sanofi-Aventis Deutschland Gmbh Method for penetrating tissue
US9186468B2 (en) 2002-04-19 2015-11-17 Sanofi-Aventis Deutschland Gmbh Method and apparatus for penetrating tissue
US9072842B2 (en) 2002-04-19 2015-07-07 Sanofi-Aventis Deutschland Gmbh Method and apparatus for penetrating tissue
US9089294B2 (en) 2002-04-19 2015-07-28 Sanofi-Aventis Deutschland Gmbh Analyte measurement device with a single shot actuator
US9089678B2 (en) 2002-04-19 2015-07-28 Sanofi-Aventis Deutschland Gmbh Method and apparatus for penetrating tissue
US9034639B2 (en) 2002-12-30 2015-05-19 Sanofi-Aventis Deutschland Gmbh Method and apparatus using optical techniques to measure analyte levels
US7850621B2 (en) 2003-06-06 2010-12-14 Pelikan Technologies, Inc. Method and apparatus for body fluid sampling and analyte sensing
US8251921B2 (en) 2003-06-06 2012-08-28 Sanofi-Aventis Deutschland Gmbh Method and apparatus for body fluid sampling and analyte sensing
US9144401B2 (en) 2003-06-11 2015-09-29 Sanofi-Aventis Deutschland Gmbh Low pain penetrating member
US10034628B2 (en) 2003-06-11 2018-07-31 Sanofi-Aventis Deutschland Gmbh Low pain penetrating member
US8282576B2 (en) 2003-09-29 2012-10-09 Sanofi-Aventis Deutschland Gmbh Method and apparatus for an improved sample capture device
US8945910B2 (en) 2003-09-29 2015-02-03 Sanofi-Aventis Deutschland Gmbh Method and apparatus for an improved sample capture device
US9351680B2 (en) 2003-10-14 2016-05-31 Sanofi-Aventis Deutschland Gmbh Method and apparatus for a variable user interface
US8668656B2 (en) 2003-12-31 2014-03-11 Sanofi-Aventis Deutschland Gmbh Method and apparatus for improving fluidic flow and sample capture
US9561000B2 (en) 2003-12-31 2017-02-07 Sanofi-Aventis Deutschland Gmbh Method and apparatus for improving fluidic flow and sample capture
US8296918B2 (en) 2003-12-31 2012-10-30 Sanofi-Aventis Deutschland Gmbh Method of manufacturing a fluid sampling device with improved analyte detecting member configuration
US9261476B2 (en) 2004-05-20 2016-02-16 Sanofi Sa Printable hydrogel for biosensors
US8828203B2 (en) 2004-05-20 2014-09-09 Sanofi-Aventis Deutschland Gmbh Printable hydrogels for biosensors
US9820684B2 (en) 2004-06-03 2017-11-21 Sanofi-Aventis Deutschland Gmbh Method and apparatus for a fluid sampling device
US8652831B2 (en) 2004-12-30 2014-02-18 Sanofi-Aventis Deutschland Gmbh Method and apparatus for analyte measurement test time
US7822454B1 (en) 2005-01-03 2010-10-26 Pelikan Technologies, Inc. Fluid sampling device with improved analyte detecting member configuration
US8702624B2 (en) 2006-09-29 2014-04-22 Sanofi-Aventis Deutschland Gmbh Analyte measurement device with a single shot actuator
US9386944B2 (en) 2008-04-11 2016-07-12 Sanofi-Aventis Deutschland Gmbh Method and apparatus for analyte detecting device
US9375169B2 (en) 2009-01-30 2016-06-28 Sanofi-Aventis Deutschland Gmbh Cam drive for managing disposable penetrating member actions with a single motor and motor and control system
US8965476B2 (en) 2010-04-16 2015-02-24 Sanofi-Aventis Deutschland Gmbh Tissue penetration device
US9795747B2 (en) 2010-06-02 2017-10-24 Sanofi-Aventis Deutschland Gmbh Methods and apparatus for lancet actuation

Also Published As

Publication number Publication date
US5379384A (en) 1995-01-03

Similar Documents

Publication Publication Date Title
USRE36191E (en) Configuration data loopback in a bus bridge circuit
US5579530A (en) Method and apparatus for dynamically allocating access time to a resource shared between a peripheral bus and a host bus by dynamically controlling the size of burst data transfers on the peripheral bus
AU652707B2 (en) Bus interface logic for computer system having dual bus architecture
US6434654B1 (en) System bus with a variable width selectivity configurable at initialization
US5761458A (en) Intelligent bus bridge for input/output subsystems in a computer system
US5664197A (en) Method and apparatus for handling bus master channel and direct memory access (DMA) channel access requests at an I/O controller
US5659696A (en) Method and apparatus for determining address location and taking one of two actions depending on the type of read/write data transfer required
US6189062B1 (en) Apparatus and method for address translation in bus bridge devices
US5469435A (en) Bus deadlock avoidance during master split-transactions
US6397279B1 (en) Smart retry system that reduces wasted bus transactions associated with master retries
US5574869A (en) Bus bridge circuit having configuration space enable register for controlling transition between various modes by writing the bridge identifier into CSE register
CA2266076C (en) Bus interface control circuit
JPH06231075A (en) Method and apparatus for zero-hiding loop arbitration
US5717875A (en) Computing device having semi-dedicated high speed bus
US6000013A (en) Method and apparatus for connecting memory chips to form a cache memory by assigning each chip a unique identification characteristic
US5566304A (en) Method of dynamic selection between immediate and delayed read access acknowledgement
US5933613A (en) Computer system and inter-bus control circuit
EP0784278B1 (en) Interface architecture for connection to a peripheral component interconnect bus
US6425071B1 (en) Subsystem bridge of AMBA's ASB bus to peripheral component interconnect (PCI) bus
US7062588B2 (en) Data processing device accessing a memory in response to a request made by an external bus master
JPH1055331A (en) Programmable read and write access signal and its method
US5802597A (en) SDRAM memory controller while in burst four mode supporting single data accesses
US6370593B1 (en) Apparatus for multiplexing bus interfaces on a computer expansion
US5371863A (en) High speed processor bus extension
EP0184320B1 (en) Improved performance memory bus architecture

Legal Events

Date Code Title Description
FPAY Fee payment

Year of fee payment: 8

FEPP Fee payment procedure

Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

FPAY Fee payment

Year of fee payment: 12