From: Anton Mikanovich <amikan@ilbers.de>
To: Harald Seiler <hws@denx.de>, isar-users@googlegroups.com
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
"florian . bezdeka @ siemens . com" <florian.bezdeka@siemens.com>
Subject: Re: [PATCH v4 1/3] classes: Add initramfs class
Date: Wed, 10 Feb 2021 12:10:24 +0300 [thread overview]
Message-ID: <b4c144a9-34e0-0a26-bcf5-a8d1265bcfe6@ilbers.de> (raw)
In-Reply-To: <20210118100729.138523-1-hws@denx.de>
18.01.2021 13:07, Harald Seiler wrote:
> Add a new "image" class for generating a custom initramfs. It works
> like this: A new minimal debian rootfs is bootstrapped and all
> dependency packages for the new initramfs are installed. Then, an
> initramfs is generated from this rootfs and deployed like usual.
>
> This new initramfs.bbclass "image" class should be pulled in by an
> "initramfs image" recipe. Said recipe then specifies all dependencies
> of the initramfs via INITRAMFS_INSTALL and INITRAMFS_PREINSTALL (which
> are analogous to the respective IMAGE_* variables).
>
> initramfs.bbclass intentionally does _not_ expose a mechanism to change
> /etc/initramfs-tools/initramfs.conf and /etc/initramfs-tools/modules.
> Changes to their settings are better done via packages that deploy
> conf-hooks to /usr/share/initramfs-tools/conf-hooks.d/ and module
> fragment files to /usr/share/initramfs-tools/modules.d/.
>
> Signed-off-by: Harald Seiler <hws@denx.de>
Patchset applied to next, thanks.
--
Anton Mikanovich
Promwad Ltd.
External service provider of ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn, Germany
+49 (89) 122 67 24-0
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov
prev parent reply other threads:[~2021-02-10 9:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 10:07 Harald Seiler
2021-01-18 10:07 ` [PATCH v4 2/3] Add example initramfs module recipe Harald Seiler
2021-01-18 10:07 ` [PATCH v4 3/3] Add custom isar-initramfs example Harald Seiler
2021-02-10 9:10 ` Anton Mikanovich [this message]
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=b4c144a9-34e0-0a26-bcf5-a8d1265bcfe6@ilbers.de \
--to=amikan@ilbers.de \
--cc=florian.bezdeka@siemens.com \
--cc=hws@denx.de \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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