From: "Jan Lübbe" <jlu@pengutronix.de>
To: Michael Olbrich <m.olbrich@pengutronix.de>,
Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: "Marc Kleine-Budde" <mkl@pengutronix.de>,
distrokit@pengutronix.de, "Uwe Kleine-König" <ukl@pengutronix.de>,
"Lucas Stach" <l.stach@pengutronix.de>
Subject: Re: [DistroKit] [PATCH] platform-v8a: kernelconfig: cleanup
Date: Thu, 25 Jan 2024 11:43:18 +0100 [thread overview]
Message-ID: <a536fed888b70f15e8c0fed83d2903fe7760101b.camel@pengutronix.de> (raw)
In-Reply-To: <Za6QTVmjaqHUPUa2@pengutronix.de>
On Mon, 2024-01-22 at 16:57 +0100, Michael Olbrich wrote:
> On Mon, Jan 22, 2024 at 04:01:36PM +0100, Ahmad Fatoum wrote:
> > On 17.01.24 14:56, Michael Olbrich wrote:
> > > -CONFIG_BLK_DEV_INITRD=y
> > > -CONFIG_INITRAMFS_SOURCE=""
> > > -# CONFIG_RD_GZIP is not set
> > > -# CONFIG_RD_BZIP2 is not set
> > > -# CONFIG_RD_LZMA is not set
> > > -# CONFIG_RD_XZ is not set
> > > -# CONFIG_RD_LZO is not set
> > > -# CONFIG_RD_LZ4 is not set
> > > -CONFIG_RD_ZSTD=y
> > > +# CONFIG_BLK_DEV_INITRD is not set
> >
> > We want to keep CONFIG_BLK_DEV_INITRD, so DistroKit systems can easily
> > boot common distros like Debian that ship with an initramfs.
>
> I was not aware that this is a use-case for DistroKit. I'm not sure how
> that is supposed to work but fine.
On some boards, we've configured barebox's fastboot to allow upload of kernel,
initramfs and oftree to ramfs. That way, one can quickly boot a small test setup
via USB (such as those produced by kernelci). There's no need to write anything
to flash, which would take time and potentially overwrite another useful rootfs.
In the medium term, I'd like to have fastboot configured this way on all
DistroKit boards with USB OTG, so that one can quickly boot a multi-arch kernel
on many boards.
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:[~2024-01-25 10:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 13:56 Michael Olbrich
2024-01-19 16:24 ` Michael Olbrich
2024-01-22 15:01 ` Ahmad Fatoum
2024-01-22 15:57 ` Michael Olbrich
2024-01-25 8:48 ` Ahmad Fatoum
2024-01-25 10:38 ` Uwe Kleine-König
2024-01-25 10:43 ` Jan Lübbe [this message]
2024-01-25 10:57 ` Michael Olbrich
2024-01-22 16:08 ` Uwe Kleine-König
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=a536fed888b70f15e8c0fed83d2903fe7760101b.camel@pengutronix.de \
--to=jlu@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=distrokit@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=m.olbrich@pengutronix.de \
--cc=mkl@pengutronix.de \
--cc=ukl@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