From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH v4 1/2] Kconfig: add btrfs to distro boot
Date: Mon, 27 Jan 2020 16:58:06 -0500 [thread overview]
Message-ID: <20200127215806.GA13444@bill-the-cat> (raw)
In-Reply-To: <20200117195905.26404-1-matthias.bgg@kernel.org>
On Fri, Jan 17, 2020 at 08:59:02PM +0100, matthias.bgg at kernel.org wrote:
> From: Matthias Brugger <mbrugger@suse.com>
>
> Some distributions use btrfs as the default file system.
> Enable btrfs support by default when using distro boot for all
> architectures but riscv, as it breaks compilation due to size problems.
>
> Signed-off-by: Matthias Brugger <mbrugger@suse.com>
This adds around 60kb to many platforms, so I'm not going to take this
right now. But I'm not rejecting it outright. My question however is,
I was under the impression that the direction distributions were taking
was that bootefi would be used to start GRUB2 and that (and its
filesystem modules) would be responsible for doing the next steps. So
we wouldn't need btrfs support here for example as everything would be
picked out of the system partition, which is FAT32. Am I mistaken
about the flow here? Thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200127/dd151e33/attachment.sig>
next prev parent reply other threads:[~2020-01-27 21:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-17 19:59 [PATCH v4 1/2] Kconfig: add btrfs to distro boot matthias.bgg at kernel.org
2020-01-17 19:59 ` [PATCH v4 2/2] configs: Re-sync with CONFIG_DISTRO_DEFAULTS matthias.bgg at kernel.org
2020-01-20 9:34 ` [PATCH v4 1/2] Kconfig: add btrfs to distro boot Matthias Brugger
2020-01-27 21:58 ` Tom Rini [this message]
2020-01-27 23:26 ` Marek Behun
2020-01-27 23:28 ` Tom Rini
2020-01-28 13:06 ` Marek Behun
2020-01-28 13:31 ` Tom Rini
2020-01-28 10:26 ` Matthias Brugger
2020-01-28 13:30 ` Tom Rini
2020-02-03 14:17 ` Petr Vorel
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=20200127215806.GA13444@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.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