x86: Introduce RESET_VECTOR_IN_RAM option
Create a new Kconfig symbol that allows an x86 device to begin execution when its reset vector is in DRAM and not at the traditional 0xfffffff0. The implementation will follow later, this is just to setup various ENV_xxx definitions correctly for the build environment. Change-Id: I098ecf8bf200550db1e15f178f7661c1ac516dc5 Signed-off-by: Marshall Dawson <marshalldawson3rd@gmail.com> Signed-off-by: Kyösti Mälkki <kyosti.malkki@gmail.com> Reviewed-on: https://review.coreboot.org/c/coreboot/+/35004 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Julius Werner <jwerner@chromium.org>
This commit is contained in:
committed by
Kyösti Mälkki
parent
a165c07ed7
commit
8418fd418c
@@ -81,6 +81,13 @@ config AP_IN_SIPI_WAIT
|
||||
default n
|
||||
depends on ARCH_X86 && SMP
|
||||
|
||||
config RESET_VECTOR_IN_RAM
|
||||
bool
|
||||
depends on ARCH_X86
|
||||
help
|
||||
Select this option if the x86 soc implements custom code to handle the
|
||||
reset vector in RAM instead of the traditional 0xfffffff0 location.
|
||||
|
||||
# Aligns 16bit entry code in bootblock so that hyper-threading CPUs
|
||||
# can boot AP CPUs to enable their shared caches.
|
||||
config SIPI_VECTOR_IN_ROM
|
||||
|
Reference in New Issue
Block a user