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
@ -271,7 +271,7 @@
|
||||
|
||||
#if CONFIG(ARCH_X86)
|
||||
/* Indicates memory layout is determined with arch/x86/car.ld. */
|
||||
#define ENV_CACHE_AS_RAM ENV_ROMSTAGE_OR_BEFORE
|
||||
#define ENV_CACHE_AS_RAM (ENV_ROMSTAGE_OR_BEFORE && !CONFIG(RESET_VECTOR_IN_RAM))
|
||||
/* No .data sections with execute-in-place from ROM. */
|
||||
#define ENV_STAGE_HAS_DATA_SECTION !ENV_CACHE_AS_RAM
|
||||
/* No .bss sections for stage with CAR teardown. */
|
||||
|
Reference in New Issue
Block a user