Lines Matching full:space

12 method for accessing PCI config space below it, the address space windows
33 reserving address space.  The static tables are for things the OS needs to
45 describe all the address space they consume.  This includes all the windows
53 space, since it is consumed by the host bridge.
58 spec defines Consumer/Producer only for the Extended Address Space
60 Address Space descriptors.  Consequently, OSes have to assume all
63 Prior to the addition of Extended Address Space descriptors, the failure of
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
71 New architectures should be able to use "Consumer" Extended Address Space
74 ia64 kernels assume all address space descriptors, including "Consumer"
75 Extended Address Space ones, are windows, so it would not be safe to
80 anything else."  So a PNP0C02 _CRS should claim any address space that is
86 ia64 SAL interface [7].  A host bridge consumes ECAM memory address space
88 defines the ECAM address space layout and functionality; only the base of
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
94 a _CBA method in the PNP0A03 device describes the ECAM space of a
137     QWord/DWord/Word Address Space Descriptor (.1, .2, .3)
140     Extended Address Space Descriptor (.4)
167     access to the Configuration Space, the ECAM is required as defined in
191     range specified in _CRS method. An ACPI name space object that contains