From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH v5 0/6] #10073: generic EFI for wic
Date: Thu, 15 Jun 2017 12:43:59 +0300 [thread overview]
Message-ID: <cover.1497519337.git.ed.bartosh@linux.intel.com> (raw)
Hi,
This patchset is an implementation of generic EFI approach for wic images.
Instead of introducing yet another wic plugin it uses existing APIs from
EFI_PROVIDER classes to populate ${WORKDIR}/bootfs directory with EFI artifacts
and bootloader configuration. This directory can be used by wic rootfs plugin
to put into boot partition of the image.
Example kickstart file and 2 test cases were added to wic test suite to better
illustrate the approach.
I personally like this approach much better than duplicating oe image creation
functionality in wic plugins. This way we can have the code in one place and
bootloaders can be configured the same way for oe and wic images.
Changes in v2:
- added patch: fixed default value of GRUB_ROOT
- fixed typo in commit message: timage_types_wic > image_types_wic
Changes in v3:
- scheduled do_prepare_wic_build as earlier as possible
Changes in v4:
- fixed build on platforms that don't support EFI
- fixed non-gpl3 build
- fixed build failure in systemd-boot code caused by rescheduled
do_populate_bootfs to run earlier
Changes in v5:
- yet another fix for scheduling of do_prepare_wic_build: explicitly
added dependencies do_prepare_wic_build -> EFI_PROVIDER:do_deploy
in efi provider classes
NOTE: to make this working on meta-intel we'll need to add dependency
do_prepare_wic_build -> "${MLPREFIX}rmc-db:do_deploy"
I'll send patch for this as soon as this patchset is accepted.
The following changes since commit 6964efddd31c479386d1643c1025bc102710392f:
bitbake: cooker: ensure graceful exit after exception during BuildCompleted handler (2017-06-14 14:54:25 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib ed/wip
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=ed/wip
Ed Bartosh (6):
efi: add efi_bootfs_populate API
image_types_wic: add do_populate_bootfs task
image_types_wic: merged 2 tasks
grub-efi: fixed default value of GRUB_ROOT
image_types_wic: schedule prepare_wic_build correctly
oe-selftest: add wic tests for generic EFI
meta-selftest/wic/test_generic_efi.wks.in | 9 ++++
meta/classes/grub-efi.bbclass | 15 ++++--
meta/classes/image_types_wic.bbclass | 84 +++++++++++++++++++++++--------
meta/classes/systemd-boot.bbclass | 7 +++
meta/lib/oeqa/selftest/cases/wic.py | 36 +++++++++++++
5 files changed, 125 insertions(+), 26 deletions(-)
create mode 100644 meta-selftest/wic/test_generic_efi.wks.in
--
2.1.4
next reply other threads:[~2017-06-15 9:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-15 9:43 Ed Bartosh [this message]
2017-06-15 9:44 ` [PATCH v5 1/6] efi: add efi_bootfs_populate API Ed Bartosh
2017-06-15 9:44 ` [PATCH v5 2/6] image_types_wic: add do_populate_bootfs task Ed Bartosh
2017-06-15 9:44 ` [PATCH v5 3/6] image_types_wic: merged 2 tasks Ed Bartosh
2017-06-15 9:44 ` [PATCH v5 4/6] grub-efi: fixed default value of GRUB_ROOT Ed Bartosh
2017-06-15 9:44 ` [PATCH v5 5/6] image_types_wic: schedule prepare_wic_build correctly Ed Bartosh
2017-06-15 9:44 ` [PATCH v5 6/6] oe-selftest: add wic tests for generic EFI Ed Bartosh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1497519337.git.ed.bartosh@linux.intel.com \
--to=ed.bartosh@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox