public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Harald Seiler <hws@denx.de>, isar-users@googlegroups.com
Subject: Re: [PATCH v2 3/3] Add custom isar-initramfs example
Date: Fri, 25 Sep 2020 11:13:06 +0200	[thread overview]
Message-ID: <f1c6deb1-440d-7e57-fb36-5eb81a478a3c@siemens.com> (raw)
In-Reply-To: <20200923162046.206888-3-hws@denx.de>

On 23.09.20 18:20, Harald Seiler wrote:
> isar-initramfs is a custom initramfs which additionally has the
> initramfs-example module installed.
> 
> Signed-off-by: Harald Seiler <hws@denx.de>
> ---
> 
> Notes:
>      Maybe this initramfs should be tested in CI somewhere?  I'm unsure what
>      makes sense, and how to "force" this custom initramfs into a CI target.
> 
>   .../recipes-initramfs/images/isar-initramfs.bb | 18 ++++++++++++++++++
>   1 file changed, 18 insertions(+)
>   create mode 100644 meta-isar/recipes-initramfs/images/isar-initramfs.bb
> 
> diff --git a/meta-isar/recipes-initramfs/images/isar-initramfs.bb b/meta-isar/recipes-initramfs/images/isar-initramfs.bb
> new file mode 100644
> index 000000000000..aaa0350aab20
> --- /dev/null
> +++ b/meta-isar/recipes-initramfs/images/isar-initramfs.bb
> @@ -0,0 +1,18 @@
> +# Example of a custom initramfs image recipe.  The image will be deployed to
> +#
> +#   build/tmp/deploy/images/${MACHINE}/isar-initramfs-${DISTRO}-${MACHINE}.initrd.img
> +#
> +# This software is a part of ISAR.
> +
> +inherit initramfs
> +
> +# Debian packages that should be installed into the system for building the
> +# initramfs.  E.g. the cryptsetup package which contains initramfs scripts for
> +# decrypting a root filesystem.
> +INITRAMFS_PREINSTALL += " \
> +    "
> +
> +# Recipes that should be installed into the initramfs build rootfs.
> +INITRAMFS_INSTALL += " \
> +    initramfs-example \
> +    "
> 

If this recipe is not pulled somewhere, it's dead. Some test-only 
dependencies we had to local.conf in scripts/ci_build.sh. Or you add it 
to meta-isar/conf/local.conf.sample.

If added, will it simply replace the default initramfs? Or is more needed?

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

  reply	other threads:[~2020-09-25  9:13 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-21 10:42 [RFC PATCH] classes: Add initramfs class Harald Seiler
2020-09-21 19:25 ` Jan Kiszka
2020-09-22 10:34   ` Harald Seiler
2020-09-22 11:04     ` Jan Kiszka
2020-09-22 12:10   ` Gylstorff Quirin
2020-09-22 12:18     ` Harald Seiler
2020-09-23 16:20 ` [PATCH v2 1/3] " Harald Seiler
2020-09-25 13:16   ` Henning Schild
2020-10-06 12:24     ` Harald Seiler
2020-09-23 16:20 ` [PATCH v2 2/3] Add example initramfs module recipe Harald Seiler
2020-09-23 16:20 ` [PATCH v2 3/3] Add custom isar-initramfs example Harald Seiler
2020-09-25  9:13   ` Jan Kiszka [this message]
2020-09-25 11:28     ` Harald Seiler
2020-10-13 15:11       ` Jan Kiszka
2021-01-14 10:11         ` [PATCH v3 1/3] classes: Add initramfs class Harald Seiler
2021-01-14 10:11           ` [PATCH v3 2/3] Add example initramfs module recipe Harald Seiler
2021-01-14 10:11           ` [PATCH v3 3/3] Add custom isar-initramfs example Harald Seiler
2021-01-18  9:11           ` [PATCH v3 1/3] classes: Add initramfs class florian.bezdeka
2021-01-18 10:00             ` Harald Seiler

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=f1c6deb1-440d-7e57-fb36-5eb81a478a3c@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=hws@denx.de \
    --cc=isar-users@googlegroups.com \
    /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