Tegra needs to use a custom bootblock implementation because it starts on a coprocessor which uses ARMv4. It doesn't have the same control registers, caches, etc., and the regular bootblock gets exceptions and dies. Change-Id: Id197db2939bc840ad64244d6e2017fc5c89e0cbd Signed-off-by: Gabe Black <gabeblack@google.com> Reviewed-on: https://chromium-review.googlesource.com/171018 Reviewed-by: Ronald Minnich <rminnich@chromium.org> Commit-Queue: Gabe Black <gabeblack@chromium.org> Tested-by: Gabe Black <gabeblack@chromium.org> (cherry picked from commit a66393fdd6fe68757e394b8a611e610f1938771d) Signed-off-by: Isaac Christensen <isaac.christensen@se-eng.com> Reviewed-on: http://review.coreboot.org/6710 Tested-by: build bot (Jenkins) Reviewed-by: Ronald G. Minnich <rminnich@gmail.com> Reviewed-by: Furquan Shaikh <furquan@google.com>
26 lines
421 B
Plaintext
26 lines
421 B
Plaintext
config ARCH_BOOTBLOCK_ARMV7
|
|
bool
|
|
default n
|
|
select ARCH_ARMV7
|
|
|
|
config ARCH_ROMSTAGE_ARMV7
|
|
bool
|
|
default n
|
|
|
|
config ARCH_RAMSTAGE_ARMV7
|
|
bool
|
|
default n
|
|
|
|
# If a custom bootblock is necessary, this option should be "select"-ed by
|
|
# the thing that needs it, probably the CPU.
|
|
config ARM_BOOTBLOCK_CUSTOM
|
|
bool
|
|
default n
|
|
|
|
config CPU_HAS_BOOTBLOCK_INIT
|
|
bool
|
|
default n
|
|
|
|
config MAINBOARD_HAS_BOOTBLOCK_INIT
|
|
bool
|
|
default n |