diff options
| author | Furquan Shaikh <furquan@google.com> | 2014-08-27 22:16:34 -0700 |
|---|---|---|
| committer | Patrick Georgi <pgeorgi@google.com> | 2015-03-27 08:04:33 +0100 |
| commit | 7565f7b00073b9bb618550cabcec438f81d6175a (patch) | |
| tree | 9f7c1c98619d237f2d98efe1372dcc1de37f5b81 /src/soc/nvidia | |
| parent | b31001f4b6ff524cf68a84a7f4f152a2756e0ac1 (diff) | |
| download | coreboot-7565f7b00073b9bb618550cabcec438f81d6175a.tar.xz | |
tegra132: No need for Kconfig variables for stacks
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: I7361d8f567453e775240151fd1180c49025141b3
Signed-off-by: Patrick Georgi <pgeorgi@chromium.org>
Original-Commit-Id: 9aaa89115a67606fcb66eb354741043f7f2094bf
Original-Change-Id: I93c23ac3fa9adab4eac3c739023cbae3e5135497
Original-Signed-off-by: Furquan Shaikh <furquan@google.com>
Original-Reviewed-on: https://chromium-review.googlesource.com/214607
Original-Tested-by: Furquan Shaikh <furquan@chromium.org>
Original-Reviewed-by: Aaron Durbin <adurbin@chromium.org>
Original-Commit-Queue: Furquan Shaikh <furquan@chromium.org>
Reviewed-on: http://review.coreboot.org/9023
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
Diffstat (limited to 'src/soc/nvidia')
| -rw-r--r-- | src/soc/nvidia/tegra132/Kconfig | 12 |
1 files changed, 0 insertions, 12 deletions
diff --git a/src/soc/nvidia/tegra132/Kconfig b/src/soc/nvidia/tegra132/Kconfig index 19215a4082..edb51ba597 100644 --- a/src/soc/nvidia/tegra132/Kconfig +++ b/src/soc/nvidia/tegra132/Kconfig @@ -73,18 +73,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 |