From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: distrokit@pengutronix.de,
"Marc Kleine-Budde" <mkl@pengutronix.de>,
"Jan Lübbe" <jlu@pengutronix.de>,
"Lucas Stach" <l.stach@pengutronix.de>
Subject: Re: [DistroKit] [PATCH] platform-v8a: kernelconfig: cleanup
Date: Thu, 25 Jan 2024 11:38:37 +0100 [thread overview]
Message-ID: <jsdwiyrqw47wih4oe2n4t4ykthv6l4to3nfh2yxub7ooqtltjk@gotw63pr5yay> (raw)
In-Reply-To: <f5bf1ee1-26c6-438d-9f81-cd4f8f9a2c81@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 1471 bytes --]
On Thu, Jan 25, 2024 at 09:48:28AM +0100, Ahmad Fatoum wrote:
> Hello Michael,
>
> On 22.01.24 16:57, 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.
>
> It was suggested by Jan IIRC. Maybe he can chime in.
Being able to boot a Debian system is something I like to do. Most of
the time I do that with a Debian kernel (so it's more important that
barebox has support for initrd), but still I think it valuable to be
able to boot into a Debian rootfs to quickly test things.
Even though it doesn't happen often (for me), it's still nice enough to
keep it enabled.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | https://www.pengutronix.de/ |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-01-25 10:38 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 [this message]
2024-01-25 10:43 ` Jan Lübbe
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=jsdwiyrqw47wih4oe2n4t4ykthv6l4to3nfh2yxub7ooqtltjk@gotw63pr5yay \
--to=u.kleine-koenig@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=distrokit@pengutronix.de \
--cc=jlu@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=mkl@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