From: "Jan Lübbe" <jlu@pengutronix.de>
To: Johannes Zink <j.zink@pengutronix.de>,
Ahmad Fatoum <a.fatoum@pengutronix.de>,
distrokit@pengutronix.de
Cc: patchwork-jzi@pengutronix.de
Subject: Re: [DistroKit] [PATCH 1/5] v8a: enable initrd generation
Date: Tue, 06 Jun 2023 16:59:30 +0200 [thread overview]
Message-ID: <2ce49103c03130f46193c2f235ccbb17da2a8533.camel@pengutronix.de> (raw)
In-Reply-To: <a2c287cf-56e6-d812-1004-e1f855f2b1ab@pengutronix.de>
On Tue, 2023-06-06 at 16:44 +0200, Johannes Zink wrote:
> Hi Ahmad,
>
> On 6/6/23 16:37, Ahmad Fatoum wrote:
> > On 06.06.23 16:31, Johannes Zink wrote:
> > > also generate rootfs as cpio.gz, as this allows loading it as initramfs.
> >
> > You enable both CONFIG_RD_GZIP and CONFIG_RD_ZSTD (which I am fine with),
> > but you decide here for cpio.gz. Any particular reason?
>
> afaik ZSTD support is rather new and I wanted to have maximum flexibility when
> reusing the initramfs, even with older kernels - i.e. being able to mix a
> ptxdist-built initramfs with older kernels. I opted to also support zstd, to
> allow booting future initramfs' on current kernels, should gzip support ever be
> dropped in the future.
>
> However, I think we could probably drop the zstd support, if you are concerned
> about image size.
CONFIG_KERNEL_ZSTD is supported since 5.9:
https://cateee.net/lkddb/web-lkddb/KERNEL_ZSTD.html
In cases where an old kernel should be booted with this new initramfs, you can
just recompress it with gz on the host (which is trivial compared to building it
in the first place).
I'd suggest just going with zstd only.
Jan
--
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:[~2023-06-06 14:59 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 14:31 [DistroKit] [PATCH 0/5] enable uploading kernel, dtb and initramfs over fastboot and boot it on Rock3A Johannes Zink
2023-06-06 14:31 ` [DistroKit] [PATCH 1/5] v8a: enable initrd generation Johannes Zink
2023-06-06 14:37 ` Ahmad Fatoum
2023-06-06 14:44 ` Johannes Zink
2023-06-06 14:59 ` Jan Lübbe [this message]
2023-06-06 15:02 ` Johannes Zink
2023-06-06 14:31 ` [DistroKit] [PATCH 2/5] v8a: kernel: enable initramfs in kernel config Johannes Zink
2023-06-06 14:37 ` Ahmad Fatoum
2023-06-06 14:31 ` [DistroKit] [PATCH 3/5] v8a: images: generate sparse images from rock3a initramfs, kernel and dtb Johannes Zink
2023-06-06 14:41 ` Ahmad Fatoum
2023-06-06 14:42 ` Ahmad Fatoum
2023-06-06 14:49 ` Johannes Zink
2023-06-06 14:54 ` Ahmad Fatoum
2023-06-06 14:47 ` Johannes Zink
2023-06-06 14:51 ` Ahmad Fatoum
2023-06-06 15:04 ` Johannes Zink
2023-06-06 15:26 ` Ahmad Fatoum
2023-06-08 7:28 ` Ahmad Fatoum
2023-06-06 14:31 ` [DistroKit] [PATCH 4/5] v8a: barebox: enable loading kernel, dtb and initrd via fastboot Johannes Zink
2023-06-06 14:44 ` Ahmad Fatoum
2023-06-06 14:54 ` Johannes Zink
2023-06-08 7:36 ` Ahmad Fatoum
2023-06-09 6:26 ` Johannes Zink
2023-06-06 15:04 ` Jan Lübbe
2023-06-06 15:14 ` Johannes Zink
2023-06-06 15:16 ` Jan Lübbe
2023-06-06 14:31 ` [DistroKit] [PATCH 5/5] v8a: barebox: add a boot target for fastboot loaded image files Johannes Zink
2023-06-06 14:47 ` Ahmad Fatoum
2023-06-06 15:07 ` Jan Lübbe
2023-06-06 15:13 ` Johannes Zink
2023-06-09 9:53 ` Johannes Zink
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=2ce49103c03130f46193c2f235ccbb17da2a8533.camel@pengutronix.de \
--to=jlu@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=distrokit@pengutronix.de \
--cc=j.zink@pengutronix.de \
--cc=patchwork-jzi@pengutronix.de \
/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