summaryrefslogtreecommitdiff
path: root/src/arch/ppc64
diff options
context:
space:
mode:
authorArthur Heymans <arthur@aheymans.xyz>2019-10-29 07:32:48 +0100
committerNico Huber <nico.h@gmx.de>2019-11-10 11:46:29 +0000
commitc4c5d85c220b6bd594c1c32f0aa74117c3b68a09 (patch)
treeb6907ab9edeb8262459e5b09f01233439d7cb058 /src/arch/ppc64
parent55069d15d8a6dcd7f8eaaf36e85e5d7a53fdaae6 (diff)
downloadcoreboot-c4c5d85c220b6bd594c1c32f0aa74117c3b68a09.tar.xz
lib/Kconfig: Remove RAMSTAGE_CBMEM_TOP_ARG
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>
Diffstat (limited to 'src/arch/ppc64')
-rw-r--r--src/arch/ppc64/Kconfig1
1 files changed, 0 insertions, 1 deletions
diff --git a/src/arch/ppc64/Kconfig b/src/arch/ppc64/Kconfig
index da9c155917..0699e910ce 100644
--- a/src/arch/ppc64/Kconfig
+++ b/src/arch/ppc64/Kconfig
@@ -1,6 +1,5 @@
config ARCH_PPC64
bool
- select RAMSTAGE_CBMEM_TOP_ARG
config ARCH_BOOTBLOCK_PPC64
bool