From: Cal Sullivan <california.l.sullivan@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] core-image-minimal-initramfs: use initramfs-framework for initialization
Date: Tue, 9 Jan 2018 17:00:03 -0800 [thread overview]
Message-ID: <8686fa07-e2a8-1080-e646-7380437e7338@intel.com> (raw)
In-Reply-To: <20171219221234.21699-1-california.l.sullivan@intel.com>
Anything wrong with this? Haven't seen it hit any mut branches.
Thanks,
Cal
On 12/19/2017 02:12 PM, California Sullivan wrote:
> initramfs-framework is more modular and expandable. This change was
> proposed in commit 28fc6ba761ed4a47efa7c43e7f7dff5e2fe72b5e
> "core-image-minimal-initramfs: use initramfs-framework by default" but
> reverted due to the selftests runqemu.RunqemuTests.test_boot_machine_iso
> and runqemu.RunqemuTests.test_boot_deploy_hddimg failing. Since then,
> the kinks have been worked out, and missing functionality that had been
> missed (non-EFI installation module) has been added.
>
> Since the PACKAGE_INSTALL variable was getting so long with all these
> individual modules getting added, I also introduced a new
> INITRAMFS_SCRIPTS variable to the core-image-minimal-initramfs recipe.
> This variable makes the recipe look much cleaner, and also allows easier
> replacement or additions to the scripts.
>
> Fixes [YOCTO #10987].
>
> Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
> ---
> meta/recipes-core/images/core-image-minimal-initramfs.bb | 10 +++++++++-
> 1 file changed, 9 insertions(+), 1 deletion(-)
>
> diff --git a/meta/recipes-core/images/core-image-minimal-initramfs.bb b/meta/recipes-core/images/core-image-minimal-initramfs.bb
> index 5794a25952a..a9ba91bd310 100644
> --- a/meta/recipes-core/images/core-image-minimal-initramfs.bb
> +++ b/meta/recipes-core/images/core-image-minimal-initramfs.bb
> @@ -3,7 +3,15 @@ DESCRIPTION = "Small image capable of booting a device. The kernel includes \
> the Minimal RAM-based Initial Root Filesystem (initramfs), which finds the \
> first 'init' program more efficiently."
>
> -PACKAGE_INSTALL = "initramfs-live-boot initramfs-live-install initramfs-live-install-efi ${VIRTUAL-RUNTIME_base-utils} udev base-passwd ${ROOTFS_BOOTSTRAP_INSTALL}"
> +INITRAMFS_SCRIPTS ?= "\
> + initramfs-framework-base \
> + initramfs-module-setup-live \
> + initramfs-module-udev \
> + initramfs-module-install \
> + initramfs-module-install-efi \
> + "
> +
> +PACKAGE_INSTALL = "${INITRAMFS_SCRIPTS} ${VIRTUAL-RUNTIME_base-utils} udev base-passwd ${ROOTFS_BOOTSTRAP_INSTALL}"
>
> # Do not pollute the initrd image with rootfs features
> IMAGE_FEATURES = ""
next prev parent reply other threads:[~2018-01-10 1:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-19 22:12 [PATCH] core-image-minimal-initramfs: use initramfs-framework for initialization California Sullivan
2018-01-10 1:00 ` Cal Sullivan [this message]
2018-01-31 22:53 ` Cal Sullivan
2018-02-01 14:03 ` Burton, Ross
2018-02-05 23:34 ` Burton, Ross
2018-02-06 0:15 ` Cal Sullivan
2018-02-06 0:47 ` Khem Raj
2018-02-06 1:52 ` Cal Sullivan
2018-02-06 19:03 ` Cal Sullivan
2018-02-26 20:34 ` Cal Sullivan
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=8686fa07-e2a8-1080-e646-7380437e7338@intel.com \
--to=california.l.sullivan@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