From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Simon Glass <sjg@chromium.org>, linux-arm-kernel@lists.infradead.org
Cc: "Chen-Yu Tsai" <wenst@chromium.org>,
"J . Neuschäfer" <j.ne@posteo.net>,
"Masahiro Yamada" <masahiroy@kernel.org>,
"Tom Rini" <trini@konsulko.com>,
linux-kernel@vger.kernel.org,
"Pengutronix Kernel Team" <kernel@pengutronix.de>
Subject: Re: [PATCH 1/2] scripts/make_fit: Support an initial ramdisk
Date: Mon, 22 Sep 2025 09:14:55 +0200 [thread overview]
Message-ID: <9cafbc70-7235-4e49-928c-4d68a57b7d46@pengutronix.de> (raw)
In-Reply-To: <20250919211000.1045267-1-sjg@chromium.org>
Hello Simon,
On 19.09.25 23:09, Simon Glass wrote:
> FIT (Flat Image Tree) allows an ramdisk to be included in each
> configuration. Add support for this to the script.
>
> This feature is not available via 'make image.fit' since the ramdisk
> likely needs to be built separately anyway, e.g. using modules from
> the kernel build.
AFAIK the kernel supports multiple concatenated separately compressed
initramfs just fine, so it may still be useful to add a target which
builds a cpio with all modules inside and the rest can be then
concatenated.
What do you think?
> + fsw.property_string('compression', args.compress)
compression should be none as the kernel would take of decompression.
Both U-Boot and barebox should warn about ramdisk compression property
that is != "none".
Cheers,
Ahmad
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2025-09-22 7:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 21:09 [PATCH 1/2] scripts/make_fit: Support an initial ramdisk Simon Glass
2025-09-19 21:09 ` [PATCH 2/2] scripts/make_fit: Speed up operation Simon Glass
2025-09-22 7:14 ` Ahmad Fatoum [this message]
2025-09-22 13:58 ` [PATCH 1/2] scripts/make_fit: Support an initial ramdisk Tom Rini
2025-09-22 22:49 ` Simon Glass
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=9cafbc70-7235-4e49-928c-4d68a57b7d46@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=j.ne@posteo.net \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=wenst@chromium.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