allow using coreboot's build system to add payload
lbmk must still define payloads, but specific configs may use coreboot's build system instead. you might use this to add your own config with, say, tianocore payload, using coreboot.git to build it, rather than using lbmk's choice of payloads. Signed-off-by: Leah Rowe <leah@libreboot.org>audit2
parent
93a476b4fc
commit
1bc484dbf6
|
@ -90,10 +90,13 @@ mkcorebootbin()
|
|||
|
||||
[ "$payload_memtest" = "y" ] || payload_memtest="n"
|
||||
[ "$(uname -m)" = "x86_64" ] || payload_memtest="n"
|
||||
|
||||
[ "$payload_seabios" = "y" ] && pname="seabios" && $dry add_seabios
|
||||
if grep "CONFIG_PAYLOAD_NONE=y" "$defconfig"; then
|
||||
[ "$payload_seabios" = "y" ] && pname="seabios" && \
|
||||
$dry add_seabios
|
||||
[ "$payload_uboot" = "y" ] && pname="uboot" && $dry add_uboot
|
||||
|
||||
else
|
||||
pname="custom" # coreboot's build system added payloads
|
||||
fi
|
||||
newrom="bin/$target/${pname}_${target}_$initmode$displaymode.rom"
|
||||
$dry x_ mkdir -p "${newrom%/*}"; $dry x_ mv "$tmprom" "$newrom"
|
||||
}
|
||||
|
|
Loading…
Reference in New Issue