erebion/coreboot
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

t132: No need of the Kconfig variable for stacks

Browse source 
With the latest changes to include stack storage within ramstage, we no longer
need to define Kconfig options for ramstage/exception stacks in arm64.

BUG=None
BRANCH=None
TEST=Compiles successfully and boots to kernel on ryu

Change-Id: I93c23ac3fa9adab4eac3c739023cbae3e5135497
Signed-off-by: Furquan Shaikh <furquan@google.com>
Reviewed-on: https://chromium-review.googlesource.com/214607
Tested-by: Furquan Shaikh <furquan@chromium.org>
Reviewed-by: Aaron Durbin <adurbin@chromium.org>
Commit-Queue: Furquan Shaikh <furquan@chromium.org>
This commit is contained in:
Furquan Shaikh 2014-08-27 22:16:34 -07:00 • committed by chrome-internal-fetch
commit 9aaa89115a
1 changed files with 0 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

12
src/soc/nvidia/tegra132/Kconfig
View file

@ -72,18 +72,6 @@ config ROMSTAGE_STACK_BOTTOM
hex
default 0x4001c000
config RAMSTAGE_STACK_TOP
hex
default 0x80020000
config RAMSTAGE_STACK_BOTTOM
hex
default 0x8001c000
config EXCEPTION_STACK_TOP
hex
default 0x80010000
config CBFS_CACHE_ADDRESS
hex "memory address to put CBFS cache data"
default 0x40006000