Abstract: A host system may couple to a PCIe subsystem. During setup of the PCIe subsystem, the BIOS in the host system may first be informed that the devices to be coupled are not PCIe devices, and certain amount of memory is required for these devices. The BIOS may therefore not attempt to configure the devices, and may instead allocate the required memory space. When the operating system boots up, it may not attempt to configure the devices, loading a custom driver instead of an existing PCI driver to configure the bus. Once loaded, the custom driver may configure the devices, then inform the OS that there are PCIe devices in the system at the specified addresses, which may cause the OS to load and execute existing PCIe device drivers to operate/use the devices. The proprietary driver may also be used to handle traffic between the PCIe drivers and the OS.

Abstract: A host system may couple to a PCIe subsystem. During setup of the PCIe subsystem, the BIOS in the host system may first be informed that the devices to be coupled are not PCIe devices, and certain amount of memory is required for these devices. The BIOS may therefore not attempt to configure the devices, and may instead allocate the required memory space. When the operating system boots up, it may not attempt to configure the devices, loading a custom driver instead of an existing PCI driver to configure the bus. Once loaded, the custom driver may configure the devices, then inform the OS that there are PCIe devices in the system at the specified addresses, which may cause the OS to load and execute existing PCIe device drivers to operate/use the devices. The proprietary driver may also be used to handle traffic between the PCIe drivers and the OS.

Abstract: A host system may couple to a PCIe subsystem. During setup of the PCIe subsystem, the BIOS in the host system may first be informed that the devices to be coupled are not PCIe devices, and certain amount of memory is required for these devices. The BIOS may therefore not attempt to configure the devices, and may instead allocate the required memory space. When the operating system boots up, it may not attempt to configure the devices, loading a custom driver instead of an existing PCI driver to configure the bus. Once loaded, the custom driver may configure the devices, then inform the OS that there are PCIe devices in the system at the specified addresses, which may cause the OS to load and execute existing PCIe device drivers to operate/use the devices. The proprietary driver may also be used to handle traffic between the PCIe drivers and the OS.

Abstract: A host system may couple to a PCIe subsystem. During setup of the PCIe subsystem, the BIOS in the host system may first be informed that the devices to be coupled are not PCIe devices, and certain amount of memory is required for these devices. The BIOS may therefore not attempt to configure the devices, and may instead allocate the required memory space. When the operating system boots up, it may not attempt to configure the devices, loading a custom driver instead of an existing PCI driver to configure the bus. Once loaded, the custom driver may configure the devices, then inform the OS that there are PCIe devices in the system at the specified addresses, which may cause the OS to load and execute existing PCIe device drivers to operate/use the devices. The proprietary driver may also be used to handle traffic between the PCIe drivers and the OS.

Abstract: Enumerating an expanded bus system in a system. The expanded bus system may include a first bus, a bridge coupled to the first bus, and a second bus coupled to the bridge, where the second bus includes one or more downstream bus ports. One or more of the downstream bus ports may initially be masked. An initial bus enumeration may be performed during system boot, which may not include enumerating the masked bus ports. After the initial bus enumeration, the masked bus ports may be unmasked. An operating system may re-enumerate the bus system, which may include enumerating the no-longer-masked bus ports.

Abstract: Enumerating an expanded bus system in a system. The expanded bus system may include a first bus, a bridge coupled to the first bus, and a second bus coupled to the bridge, where the second bus includes one or more downstream bus ports. One or more of the downstream bus ports may initially be masked. An initial bus enumeration may be performed during system boot, which may not include enumerating the masked bus ports. After the initial bus enumeration, the masked bus ports may be unmasked. An operating system may re-enumerate the bus system, which may include enumerating the no-longer-masked bus ports.

Abstract: System and method for configuring a second system in a split bridge distributed environment. A host computer system (host) includes a memory operable to store host driver software (drivers) and a CPU operable to execute the drivers. A serial bus couples the host to the second system. The host saves configuration information for the second system. The second system receives user input requesting a power down condition. The drivers enters a quiescent state, generating an indication of a power down condition. The user powers down and reconfigures the second system. The host detects a link down condition between the host and the second system, and monitors a link status between the host and second system. The user powers up the second system. The host detects a link up condition, restores second system configuration, and performs a discovery process on the second system.

Abstract: System and method for configuring a second system in a split bridge distributed environment. A host computer system (host) includes a memory operable to store host driver software (drivers) and a CPU operable to execute the drivers. A serial bus couples the host to the second system. The host saves configuration information for the second system. The second system receives user input requesting a power down condition. The drivers enters a quiescent state, generating an indication of a power down condition. The user powers down and reconfigures the second system. The host detects a link down condition between the host and the second system, and monitors a link status between the host and second system. The user powers up the second system. The host detects a link up condition, restores second system configuration, and performs a discovery process on the second system.