All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Khem Raj <raj.khem@gmail.com>,
	Richard Purdie <richard.purdie@linuxfoundation.org>,
	 Armin Kuster <akuster808@gmail.com>,
	Jerome Neanne <jneanne@baylibre.com>,
	 Quentin Schulz <quentin.schulz@streamunlimited.com>
Cc: Bartosz Golaszewski <bgolaszewski@baylibre.com>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [RFC PATCH 0/2] image.bbclass: support two-stage deployment of image artifacts
Date: Thu, 19 Mar 2020 17:49:50 +0100	[thread overview]
Message-ID: <CAMRc=MfAE42E=+CnMfuh_29QWOJACQnyJgbdRVXjm8EvhxHwsQ@mail.gmail.com> (raw)
In-Reply-To: <20200319164403.29605-1-brgl@bgdev.pl>

czw., 19 mar 2020 o 17:44 Bartosz Golaszewski <brgl@bgdev.pl> napisał(a):
>
> From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
>
> This is a follow-up to the discussion I started on the OE-core mailing
> list a couple days ago[1]. These patches propose to split the deployment
> of image artifacts into two stages where the first one includes all
> "regular" images and takes place before do_image_complete and the second
> is mostly aimed at wic right now and happens after do_image_complete.
>
> These patches work but I'm sending them as RFC mostly to continue the
> discussion about possible solutions for the circular dependencies between
> the rootfs and initramfs.
>
> [1] http://lists.openembedded.org/pipermail/openembedded-core/2020-March/294094.html
>
> Bartosz Golaszewski (2):
>   image.bbclass: add an intermediate deploy task
>   image.bbclass: deploy artifacts in two stages
>
>  meta/classes/image.bbclass                    | 54 ++++++++++++++-----
>  meta/classes/image_types.bbclass              |  3 ++
>  meta/classes/image_types_wic.bbclass          |  4 +-
>  .../images/build-appliance-image_15.0.0.bb    |  2 +-
>  4 files changed, 47 insertions(+), 16 deletions(-)
>
> --
> 2.19.1
>

Just for clarity: this what the task order would look like for a
standard beaglebone-yocto image with these patches:

do_prepare_recipe_sysroot (32199): log.do_prepare_recipe_sysroot.32199
do_deploy_source_date_epoch (32201): log.do_deploy_source_date_epoch.32201
do_rootfs (32246): log.do_rootfs.32246
do_write_qemuboot_conf (8655): log.do_write_qemuboot_conf.8655
do_image_qa (8657): log.do_image_qa.8657
do_image (8661): log.do_image.8661
do_image_ext4 (35128): log.do_image_ext4.35128
do_image_tar (35133): log.do_image_tar.35133
do_image_jffs2 (35136): log.do_image_jffs2.35136
do_image_deploy (35246): log.do_image_deploy.35246
do_image_complete (35262): log.do_image_complete.35262
do_rootfs_wicenv (35264): log.do_rootfs_wicenv.35264
do_populate_lic_deploy (35267): log.do_populate_lic_deploy.35267
do_image_wic (35283): log.do_image_wic.35283
do_image_deploy_late (35448): log.do_image_deploy_late.35448

Bart


  parent reply	other threads:[~2020-03-19 16:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-19 16:44 [RFC PATCH 0/2] image.bbclass: support two-stage deployment of image artifacts Bartosz Golaszewski
2020-03-19 16:44 ` [RFC PATCH 1/2] image.bbclass: add an intermediate deploy task Bartosz Golaszewski
2020-03-19 16:44 ` [RFC PATCH 2/2] image.bbclass: deploy artifacts in two stages Bartosz Golaszewski
2020-03-19 16:49 ` Bartosz Golaszewski [this message]
2020-03-19 17:12 ` [RFC PATCH 0/2] image.bbclass: support two-stage deployment of image artifacts Richard Purdie
2020-03-19 18:20   ` Bartosz Golaszewski
2020-03-19 23:38     ` Richard Purdie
2020-03-20 13:11       ` Bartosz Golaszewski

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='CAMRc=MfAE42E=+CnMfuh_29QWOJACQnyJgbdRVXjm8EvhxHwsQ@mail.gmail.com' \
    --to=brgl@bgdev.pl \
    --cc=akuster808@gmail.com \
    --cc=bgolaszewski@baylibre.com \
    --cc=jneanne@baylibre.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=quentin.schulz@streamunlimited.com \
    --cc=raj.khem@gmail.com \
    --cc=richard.purdie@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.