diff options
| author | Patrick Ohly <patrick.ohly@intel.com> | 2016-12-20 08:47:21 +0100 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2017-03-01 11:17:44 +0000 |
| commit | 3ee86f53266ba9fef1b61b6e790eddc3b6b1a944 (patch) | |
| tree | 41328f19bd6684a7f3abca9291b6c25660ab34c0 /meta/recipes-core/psplash | |
| parent | e404935ca91ab1a73ff9683c92d1a232dd5e3d49 (diff) | |
| download | poky-3ee86f53266ba9fef1b61b6e790eddc3b6b1a944.tar.gz | |
ovmf_git.bb: enable Secure Boot
When enabled via PACCKAGECONFIG = "secureboot" (off by default because
of the extra work and license change), the recipe compiles OVMF twice,
once without Secure Boot, once with. This is the same approach as in
https://src.fedoraproject.org/cgit/rpms/edk2.git/tree/edk2.spec
The results are "ovmf.qcow2" and "ovmf.secboot.qcow2" in the
image deploy directory, so
runqemu <machine> <image> ovmf.secboot
will boot with Secure Boot enabled.
ovmf.secboot.code.qcow2 is provided for those who want separate code
and variable flash drives. The normal ovmf.vars.qcow2 can be used with
it.
In contrast to Fedora, no attempt is made to strip potentially patent
encumbered algorithms out of the OpenSSL archive. OVMF does not use
the ones considered problematic for Fedora, so this shouldn't be a
problem.
Fixes: luv-yocto/#38
(From OE-Core rev: d493f0b4760808f880a0fd6dedf918a3b85006b7)
Signed-off-by: Patrick Ohly <patrick.ohly@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-core/psplash')
0 files changed, 0 insertions, 0 deletions