PCI Bus Numbering in a Microsoft Windows NT Environment
Configuration A - Test 2 - Adding a Device
The example in Table 7 illustrates the PCI BIOS discovery and bus number assignment process in
the same ProLiant ML530 server. However, the configuration changes slightly by adding a
bridged PCI network controller on the Tertiary Bus.
Table 7. PCI BIOS bus detection in a ProLiant ML530-after adding a bridged controller
Detection
5th
6th
7th
8th
9
10th
11th
*Bus number is different than previous configuration
13UK-1200A-WWEN
Number
Controller
Bus (O)
Bridge
Empty
Bus (2)
Bridge
Empty
Slot 8
Empty
Tertiary
Host to PCI
Bus (5)
Slot 6
NC3131
Slot 4
Empty
Slot 2
Empty
Slot 5
NC3132 (non-
bridged)
Description of PCI BIOS Discovery
Assignment
Process
The PCI BIOS discovers the Primary Bus
and assigns it bus 0.
Discovery process continues to PCI slot 1.
No PCI controller detected, no bus number
N/A
assigned.
The PCI BIOS discovers the Secondary
Bus and increments the bus number to 2.
Discovery process continues to PCI slots 7
and 8. No PCI controller detected, no bus
N/A
number assigned.
N/A
The PCI BIOS discovers the Tertiary Bus
Bus 5
and increments the bus number to 5.
Discovery process continues to PCI slot 6,
and detects a bridged NIC, incrementing
Bus 6
the bus number by one to become bus 6.
Discovery process continues to PCI slots
N/A
4, 3, and 2. No PCI controller detected, no
bus number assigned.
N/A
PCI BIOS detects a NIC (no PCI bridge) in
Bus 5
slot 5, it is assigned the same bus number
as the PCI Bus where it resides.
22