0640c281c3
It's possible that some BARs are not got their resource successfully mapped, e.g. when these BARs are too large to fit into the available MMIO window. Not assigned resources might be with base address as 0x0. During global resource search, these not assigned resources should not be picked up. One example is MTRR calculation. MTRR calculation is based on global memory ranges. An unmapped BAR whose base is left as 0x0 will be mistakenly picked up and recognized as an UC range starting from 0x0. Change-Id: I9c3ea302058914f38a13a7739fc28d7f94527704 Signed-off-by: Shuo Liu <shuo.liu@intel.com> Reviewed-on: https://review.coreboot.org/c/coreboot/+/66347 Reviewed-by: Nico Huber <nico.h@gmx.de> Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Jonathan Zhang <jonzhang@fb.com> |
||
|---|---|---|
| .. | ||
| dram | ||
| oprom | ||
| azalia_device.c | ||
| cardbus_device.c | ||
| cpu_device.c | ||
| device.c | ||
| device_const.c | ||
| device_util.c | ||
| gpio.c | ||
| i2c.c | ||
| i2c_bus.c | ||
| Kconfig | ||
| Makefile.inc | ||
| mmio.c | ||
| pci_class.c | ||
| pci_device.c | ||
| pci_early.c | ||
| pci_ops.c | ||
| pci_rom.c | ||
| pciexp_device.c | ||
| pcix_device.c | ||
| pnp_device.c | ||
| resource_allocator_common.c | ||
| resource_allocator_v3.c | ||
| resource_allocator_v4.c | ||
| root_device.c | ||
| smbus_ops.c | ||
| software_i2c.c | ||
| xhci.c | ||