c4c5d85c22
All targets now have the _cbmem_top_ptr symbol populated via calling arguments or in the nvidia/tegra210 case worked around by populating it with cbmem_top_chipset explicitly at the start of ramstage, so the Kconfig guarding this behavior can be removed. Change-Id: Ie7467629e58700e4d29f6e735840c22ed687f880 Signed-off-by: Arthur Heymans <arthur@aheymans.xyz> Reviewed-on: https://review.coreboot.org/c/coreboot/+/36422 Reviewed-by: Nico Huber <nico.h@gmx.de> Reviewed-by: Michael Niewöhner Reviewed-by: Aaron Durbin <adurbin@chromium.org> Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
21 lines
294 B
Plaintext
21 lines
294 B
Plaintext
config ARCH_PPC64
|
|
bool
|
|
|
|
config ARCH_BOOTBLOCK_PPC64
|
|
bool
|
|
select ARCH_PPC64
|
|
select BOOTBLOCK_CUSTOM
|
|
select C_ENVIRONMENT_BOOTBLOCK
|
|
|
|
config ARCH_VERSTAGE_PPC64
|
|
bool
|
|
select ARCH_PPC64
|
|
|
|
config ARCH_ROMSTAGE_PPC64
|
|
bool
|
|
select ARCH_PPC64
|
|
|
|
config ARCH_RAMSTAGE_PPC64
|
|
bool
|
|
select ARCH_PPC64
|