Kconfig: Create RAMPAYLOAD kconfig
This patch enables coreboot flow to skip ramstage as individual stage to load payload. Instead it is expected to load payload from postcar stage. Change-Id: I839f2d34a93b69ca6bf3de6594e2ad9f66ee7135 Signed-off-by: Subrata Banik <subrata.banik@intel.com> Reviewed-on: https://review.coreboot.org/c/coreboot/+/32618 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: ron minnich <rminnich@gmail.com>
This commit is contained in:
parent
7bc9036d16
commit
7e893a02c0
15
src/Kconfig
15
src/Kconfig
|
@ -277,6 +277,21 @@ config BOOTSPLASH_FILE
|
|||
The path and filename of the file to use as graphical bootsplash
|
||||
screen. The file format has to be jpg.
|
||||
|
||||
config RAMPAYLOAD
|
||||
bool "Enable coreboot flow without executing ramstage"
|
||||
default n
|
||||
depends on ARCH_X86
|
||||
help
|
||||
If this option is enabled, coreboot flow will skip ramstage
|
||||
loading and execution of ramstage to load payload.
|
||||
|
||||
Instead it is expected to load payload from postcar stage itself.
|
||||
|
||||
In this flow coreboot will perform basic x86 initialization
|
||||
(DRAM resource allocation), MTRR programming,
|
||||
Skip PCI enumeration logic and only allocate BAR for fixed devices
|
||||
(bootable devices, TPM over GSPI).
|
||||
|
||||
endmenu
|
||||
|
||||
menu "Mainboard"
|
||||
|
|
Loading…
Reference in New Issue