Lines Matching +full:motherboard +full:- +full:bus
1 .. SPDX-License-Identifier: GPL-2.0
39 If the OS is expected to manage a non-discoverable device described via
46 they forward down to the PCI bus, as well as registers of the host bridge
48 things like secondary/subordinate bus registers that determine the bus
50 These are all device-specific, non-architected things, so the only way a
52 the device-specific details. The host bridge registers also include ECAM
66 bridge registers (including ECAM space) in PNP0C02 catch-all devices [6].
67 With the exception of ECAM, the bridge register space is device-specific
78 PNP0C02 "motherboard" devices are basically a catch-all. There's no
89 the address space is device-specific. An ACPI OS learns the base address
92 The MCFG table must describe the ECAM space of non-hot pluggable host
95 hot-pluggable host bridge [9]. Note that for both MCFG and _CBA, the base
96 address always corresponds to bus 0, even if the bus range below the bridge
101 For any device that is on a non-enumerable type of bus (for example, an
102 ISA bus), OSPM enumerates the devices' identifier(s) and the ACPI
107 The OS enumerates motherboard devices simply by reading through the
110 Each device enumerated by ACPI includes ACPI-defined objects in the
156 4.1.3) must be reserved by declaring a motherboard resource. For most
157 systems, the motherboard resource would appear at the root of the ACPI
159 the resources in this case should not be claimed in the root PCI bus’s
162 ACPI as a motherboard resource.
165 For systems that are PC-compatible, or that do not implement a
166 processor-architecture-specific firmware interface standard that allows
172 addresses corresponding to the non-hot removable PCI Segment Groups
174 boot. This is required for the PC-compatible systems.
182 an optional ACPI object that returns the 64-bit memory mapped
184 base address returned by _CBA is processor-relative address. The _CBA
190 base address corresponding to the PCI Segment Group for the bus number