allocator_v4: Re-enable top-down allocation for edk2
Commit a959f0ad76 ("allocator_v4: Disable top-down allocation for
EDK2") disabled top-down allocation for edk2 due to a bug which broke
display init with Intel IGD. A workaround has been implemented in
MrChromebox's fork (and others) while the issue is being resolved
upstream, so re-enable top-down allocation unless upstream edk2
is being used.
TEST=build/boot various Google mainboards with edk2 payload selected.
Change-Id: I0e9b0d02bbf30878aef37a97d6a743a402700fc7
Signed-off-by: Matt DeVillier <matt.devillier@gmail.com>
Reviewed-on: https://review.coreboot.org/c/coreboot/+/87504
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: Paul Menzel <paulepanter@mailbox.org>
Reviewed-by: Sean Rhodes <sean@starlabs.systems>
This commit is contained in:
parent
4d7b56cdaa
commit
d2b0220a38
1 changed files with 5 additions and 3 deletions
|
|
@ -994,14 +994,16 @@ config I2C_TRANSFER_TIMEOUT_US
|
|||
|
||||
config RESOURCE_ALLOCATION_TOP_DOWN
|
||||
bool "Allocate resources from top down"
|
||||
default n if PAYLOAD_EDK2
|
||||
default n if PAYLOAD_EDK2 && EDK2_REPO_OFFICIAL
|
||||
default y
|
||||
help
|
||||
Top-down allocation is required to place resources above 4G by
|
||||
default (i.e. even when there is still space below). On some
|
||||
platforms, it might make a difference because of conflicts with
|
||||
undeclared resources. EDK2 is currently reported to also have
|
||||
problems on some platforms, at least with Intel's IGD.
|
||||
undeclared resources.
|
||||
|
||||
Upstream EDK2 is currently reported to also have problems on some
|
||||
platforms at least with Intel's IGD; MrChromebox's fork works fine.
|
||||
|
||||
config ALWAYS_ALLOW_ABOVE_4G_ALLOCATION
|
||||
bool
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue