summaryrefslogtreecommitdiff
path: root/src/mainboard/google/rush/memlayout.ld
diff options
context:
space:
mode:
authorJulius Werner <jwerner@chromium.org>2016-02-09 22:47:11 -0800
committerJulius Werner <jwerner@chromium.org>2016-02-12 21:58:34 +0100
commitce8c4bfc718afdf82645743fbba41fdd814f6102 (patch)
treefa65643bea7615f33a02601382ec034ecc2aac0b /src/mainboard/google/rush/memlayout.ld
parent8c09377deab1b5a5120889bb6c689ad460381c29 (diff)
downloadcoreboot-ce8c4bfc718afdf82645743fbba41fdd814f6102.tar.xz
tegra132/210: Remove memlayout_vboot2.ld
Having two separate memlayouts is an unnecessary complication. Contributors need to make sure that their code fits into the vboot one (with smaller stage sizes) either way, and the Tegras have plenty of SRAM anyway. Let's just make the vboot layout the default (as it was done on other SoCs) to keep things easier to maintain. The empty SRAM holes on non-vboot systems where the verstage and work buffer would've been won't hurt them. BRANCH=None BUG=None TEST=Ran abuild with and without --chromeos on Foster, Rush, Ryu and Smaug. Change-Id: If37228facb4de1459cc720dca10bf03e04eb9930 Signed-off-by: Julius Werner <jwerner@chromium.org> Reviewed-on: https://review.coreboot.org/13667 Reviewed-by: Aaron Durbin <adurbin@chromium.org> Tested-by: build bot (Jenkins) Reviewed-by: Patrick Georgi <pgeorgi@google.com>
Diffstat (limited to 'src/mainboard/google/rush/memlayout.ld')
-rw-r--r--src/mainboard/google/rush/memlayout.ld4
1 files changed, 0 insertions, 4 deletions
diff --git a/src/mainboard/google/rush/memlayout.ld b/src/mainboard/google/rush/memlayout.ld
index 367a88e48e..ead7f47838 100644
--- a/src/mainboard/google/rush/memlayout.ld
+++ b/src/mainboard/google/rush/memlayout.ld
@@ -1,5 +1 @@
-#if IS_ENABLED(CONFIG_VBOOT_VERIFY_FIRMWARE)
-#include <soc/memlayout_vboot2.ld>
-#else
#include <soc/memlayout.ld>
-#endif