Browse Prior Art Database

Mux for PCI-X initialization patterns

IP.com Disclosure Number: IPCOM000011753D
Original Publication Date: 2003-Mar-12
Included in the Prior Art Database: 2003-Mar-12
Document File: 1 page(s) / 40K

Publishing Venue

IBM

Abstract

This disclosure discusses working around PCI-X host bridge problems with initializing PCI-X adapters.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 100% of the total text.

Page 1 of 1

Mux for PCI-X initialization patterns

      In order to guarantee that the correct PCI-X initialization pattern is driven to a PCI-X device coming out of reset, a PCI hot plug controller (HPC) can drive the initialization pattern to each device. Some solutions to this problem have the hot plug controller driving the PCI-X init pattern (comprised of the stop_n, trdy_n, and devsel_n signals) to the entire bus, and not just an individual device. A different method can be used to isolate these signals for each individual device.

  You can place a multiplexor on the init pattern signals. On one input side you can have the stop_n, trdy_n, and devsel_n signals coming from the PCI-X host bridge. On the other side those signals can come from the

  HPC. The HPC would also control the steering of the mux. This would allow the HPC to drive these signals during a hot plug event, and then steer control of the signals
over to the host bridge device.

Disclosed by International Business Machines Corporation

1

[This page contains 1 picture or other non-text object]