experimental edk2 supportHEADmaster

now we can have gop support!

add these to a board's target.cfg to enable:

payload_edk2="edk2_mrchromebox"

and add this to build_depend: coreboot/edk2_mrchromebox

as an example, this patch enables it on dell optiplex 5050 sff.

we don't handle downloads of edk2 or submodules in lbmk. we
use coreboot's logic. coreboot's logic doesn't have redundant
git repository backups, and doesn't properly support patching
submodules like lbmk would.

in a future revision, i will add edk2 git repository and submodules
in lbmk directly, and build it using lbmk's own logic.

because of this design, it's set release=n for now. if you build
for a board that enables edk2 when doing ./mk release, or if
you set XBMK_RELEASE=y, and a board is release=n in target.cfg,
that board is skipped; this extends to everything. edk2_mrchromebox
is set release=n.

when release=n and doing ./mk release, payload_edk2 is emptied at
build time. those boards that use it would still build, but only
have e.g. grub, seabios and u-boot.

the coreboot build system is given a fake coreboot target. it actually
is a QEMU setup, and does boot into QEMU, though edk2 is currently
broken on QEMU in my testing. it works on dell optiplex 5050 sff.

edk2 is multi-tree, naturally because it piggybacks off of coreboot
as in this patch. this means i can add other targets with different
edk2 setups. e.g. config/module/coreboot/edk2_foo, then a given
coreboot tree would set payload_edk2="foo"

so long as edk2 is enabled in the coreboot config, it will build
to a custom_*.rom under bin/

the config for coreboot must be named libgfxinit_corebootfb, but
the edk2 build could be used on fspgop and vgarom setups as
well. it is disabled on text-mode setups.

Signed-off-by: Leah Rowe <leah@libreboot.org>

0 files changed, 0 insertions, 0 deletions