Searched refs:MCFG (Results 1 – 6 of 6) sorted by relevance
| /linux/Documentation/translations/zh_CN/PCI/ |
| H A D | acpi-info.rst | 34 像MCFG、HPET、ECDT等静态表，不是保留地址空间的机制。静态表是在操作系统在启动初期且在它
71 MCFG表或PNP0A03设备中的_CBA方法中了解基础地址。
73 MCFG表必须描述非热插拔主桥的ECAM空间[8]。由于MCFG是一个静态表，不能通过热插拔更新，
74 PNP0A03设备中的_CBA方法描述了可热插拔主桥的ECAM空间[9]。请注意，对于MCFG和_CBA，
116 如果操作系统不能原生的懂得保留MMCFG区域，MMCFG区域必须由固件保留。在MCFG表中或通
127 MCFG表是一个ACPI表，用于沟通的基础地址对应的非热的可移动的PCI段组范围内的PCI段组在
130 MCFG表仅用于沟通在启动时系统可用的PCI段组对应的基址。
|
| /linux/Documentation/PCI/ |
| H A D | acpi-info.rst | 32 Static tables like MCFG, HPET, ECDT, etc., are *not* mechanisms for
90 from either the static MCFG table or a _CBA method in the PNP0A03 device.
92 The MCFG table must describe the ECAM space of non-hot pluggable host
93 bridges [8]. Since MCFG is a static table and can't be updated by hotplug,
95 hot-pluggable host bridge [9]. Note that for both MCFG and _CBA, the base
155 address range reported in the MCFG table or by _CBA method (see Section
171 The MCFG table is an ACPI table that is used to communicate the base
176 The MCFG table is only used to communicate the base addresses
|
| /linux/drivers/net/ethernet/via/ |
| H A D | via-velocity.h | 1035 volatile __le16 MCFG; member
1160 BYTE_REG_BITS_SET((n),(MCFG_RFT0|MCFG_RFT1),&((regs)->MCFG));\
|
| H A D | via-velocity.c | 510 WORD_REG_BITS_SET(MCFG_PQEN, MCFG_RTGOPT, ®s->MCFG); in velocity_init_cam_filter()
511 WORD_REG_BITS_ON(MCFG_VIDFR, ®s->MCFG); in velocity_init_cam_filter()
|
| /linux/Documentation/arch/arm64/ |
| H A D | acpi_object_usage.rst | 16 - Required: DSDT, FADT, GTDT, MADT, MCFG, RSDP, SPCR, XSDT
269 MCFG Signature Reserved (signature == "MCFG")
273 If the platform supports PCI/PCIe, an MCFG table is required.
|
| H A D | arm-acpi.rst | 196 - If PCI is supported, the MCFG (Memory mapped ConFiGuration
|