On Fri, 2017-01-20 at 15:12 +0100, Patrick Ohly wrote: > There seems to be a consensus that supporting UEFI in OE-core for qemu > would be valuable, and there have been some (stalled) attempts to add > it. For reference, see: > [OE-core] [PATCH V3 0/3] Add UEFI firmware for qemux86* > [OE-core] Add ovmf-native to make qemu-native/runqemu support boot > UEFI image? > https://bugzilla.yoctoproject.org/show_bug.cgi?id=5654 > https://github.com/01org/luv-yocto/issues/38 > > This patch set includes the necessary recipes (ovmf from meta-luv, > acpica from > meta-oe), some improvements to them (in particular, enabling Secure > Boot), and changes to runqemu to make it easier to boot with UEFI. A > special image recipes builds an image which can be used to lock down a > virtual machine by enrolling the "normal" pre-installed certificates. > > In contrast to the first version of this patch series, one can now use > both a single OVMF firmware file as well as set up persistent > variables for a virtual machine by using two files. > > Eduardo promised to add automated testing for this once it is in > OE-core. > As it stands now, ovmf-shell-image and ovmf without Secure Boot > enabled > should at least be part of a world build. > > As discussed on this list, Ricardo and Fathi volunteered to help with > maintaining the ovmf and acpica recipes in OE-core. > > Beware that "git am --keep-cr" must be used to import the ovmf patches > correctly.
This patchset looks good to me. I only had one comment/question in patch 5. If relevant, Acked-by Ricardo Neri <ricardo.neri-calde...@linux.intel.com> Thanks and BR, Ricardo -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
