Issue #415 has been updated by Nico Huber.
Subject changed from RESOURCE_ALLOCATION_TOP_DOWN breaks edk2 to RESOURCE_ALLOCATION_TOP_DOWN breaks booting (-edk2-)
It turned out that there are a lot of platforms in the tree that still don't report their fixed resources correctly. These should be added inside `.read_resources` of device drivers. This commit[1] provides an example how it can look like. Sometimes * `.read_resources` is simply missing for a device, or * the device driver is not considered because a PCI device ID is missing, or * the device driver is accidentally disabled in the mainboard devicetree.
One common mistake is not to reserve the memory-mapped "BIOS" flash. Integrated resources that are handled by blobs can also be easily forgotten (at least Intel provides documentation about the complete memory map, though).
When resources are not reported, the allocator can cause conflicts with them. This can happen already by chance; chances are higher when space is tight. Also, the OS needs to be made aware of such resources or might run into the same problem (alas, this is not tied to `.read_resources` in coreboot but needs additional ACPI code at the moment).
[1] https://review.coreboot.org/c/coreboot/+/64077
---------------------------------------- Bug #415: RESOURCE_ALLOCATION_TOP_DOWN breaks booting (-edk2-) https://ticket.coreboot.org/issues/415#change-1090
* Author: Sean Rhodes * Status: New * Priority: Low * Target version: none * Start date: 2022-09-07 * Affected versions: master ---------------------------------------- CB:41957 enabled RESOURCE_ALLOCATION_TOP_DOWN by default, which stopped edk2 from booting. The commit has been reverted, so this ticket is just to post logs.
---Files-------------------------------- resource_allocatorv4.txt (94 KB)