diff options
| author | Alexandru Gagniuc <mr.nuke.me@gmail.com> | 2013-12-28 15:42:31 -0500 |
|---|---|---|
| committer | Alexandru Gagniuc <mr.nuke.me@gmail.com> | 2014-01-14 14:15:25 +0100 |
| commit | 1b4cbafe1d88a2ae4a4e8a3cfe71adca563f755d (patch) | |
| tree | da05737815729ee4a998a7300fc327df852ddd55 | |
| parent | 93b600ded7aa847649a175b2a56f154e434fb10c (diff) | |
cpu/allwinner/a10: Clarify positioning of boot stages
This fixes a number of potential issues, such as generating a build
failure if the bootblock is too large, and making sure romstage and
ramstage cannot overlap in memory.
Change-Id: I4ca9ad097b145445316bcd962e007731b08a7fda
Signed-off-by: Alexandru Gagniuc <mr.nuke.me@gmail.com>
Reviewed-on: http://review.coreboot.org/4687
Tested-by: build bot (Jenkins)
| -rw-r--r-- | src/cpu/allwinner/a10/Kconfig | 12 |
1 files changed, 8 insertions, 4 deletions
diff --git a/src/cpu/allwinner/a10/Kconfig b/src/cpu/allwinner/a10/Kconfig index b782b9a92e..fab0022c5d 100644 --- a/src/cpu/allwinner/a10/Kconfig +++ b/src/cpu/allwinner/a10/Kconfig @@ -34,14 +34,18 @@ config CBFS_HEADER_ROM_OFFSET hex default 0x10 +# This is the maximum size bootblock that the BROM will load. If the bootblock +# gets larger, this will generate a build failure, rather than a silent +# "coreboot won't run" failure. +# Normally, we would place romstage at 0x5fe0, but we place it a little lower to +# satisfy the 64 byte alignment. config CBFS_ROM_OFFSET - # Calculated by BL1 + max bootblock size. - default 0x4c00 + default 0x5fc0 -# FIXME: untested +# 16 MiB above ramstage, so there is no overlap config ROMSTAGE_BASE hex - default SYS_SDRAM_BASE + default 0x41000000 # Keep the stack in SRAM block A2. # SRAM blocks A1 (0-16KiB) and A2 (16KiB-32KiB) are always accessible to the |