From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] Unified u-boot feature set for simpler distro support
Date: Mon, 05 Aug 2013 14:21:58 -0600 [thread overview]
Message-ID: <52000966.8080003@wwwdotorg.org> (raw)
In-Reply-To: <20130805145059.14c35ebf@adria.ausil.us>
On 08/05/2013 01:50 PM, Dennis Gilmore wrote:
> On Mon, 05 Aug 2013 12:39:03 -0600 Stephen Warren <swarren@wwwdotorg.org> wrote:
>> On 08/03/2013 01:11 AM, Dennis Gilmore wrote:
>>> I wanted to start a discussion on defining a unified feature set
>>> that makes it simpler for the different distros to support ARM
>>> systems using u-boot.
...
>>> so this would mean similar partitioning. i.e. /boot on ext4 root and
>>> swap on lvm or as raw partitions. people should be able to have
>>> just / on ext4 also. Down the road xfs /boot support would be a
>>> nice to have.
>>
>> That's only partially relevant for U-Boot. Two things U-Boot needs to
>> support:
>>
>> * Filesystem read for whatever filesystem /boot is part of (it could
>> very well be the / filesystem too, but U-Boot doesn't care, except
>> for / vs. /boot in path names). This is a matter of adding the right
>> flags to each board's U-Boot config file.
>
> right, but at the least it needs to be ext4 not all boards today read
> ext4, btrfs may be something down the road also. u-boot doesnt need to
> care too much. it just needs to look in / and /boot
Well, ext4 is nice, but presumably everything could work just as well
with ext3 or ext2. It's not really an issue other than arguing semantics
though; U-Boot has ext4 support so it's presumably just a matter of
persuading the relevant board maintainers to enable it, or sending them
patches to do so?
...
>> [ Tegra boot.scr discussion ]
>
> While this is a step forward, its still much more than we need to do
> if we enable pxe support and use sysboot to load a config file the
> says load this kernel and initramfs and pass these bootargs. My
> initial post had a fully working example.
Oh, I must have not read your email correctly. I thought the config file
you posted was as example of what you wanted to achieve, rather than
something which already worked.
Is it just a matter of turning on some config options in upstream U-Boot
to enable this on Tegra? If so, I'd be very happy to create a patch to
do so, test it with Fedora's images (got a link/README/...?) and send
the patch to be applied.
next prev parent reply other threads:[~2013-08-05 20:21 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-03 7:11 [U-Boot] Unified u-boot feature set for simpler distro support Dennis Gilmore
2013-08-03 10:08 ` Peter Maydell
2013-08-05 16:25 ` Tom Rini
2013-08-04 19:48 ` Wolfgang Denk
2013-08-04 23:02 ` Dennis Gilmore
2013-08-05 18:39 ` Stephen Warren
2013-08-05 18:48 ` Stephen Warren
2013-08-05 20:26 ` Dennis Gilmore
2013-08-05 20:54 ` Stephen Warren
2013-08-05 19:50 ` Dennis Gilmore
2013-08-05 20:14 ` Tom Rini
2013-08-05 20:21 ` Stephen Warren [this message]
2013-08-05 20:43 ` Wolfgang Denk
2013-08-05 20:49 ` Stephen Warren
2013-08-05 21:00 ` Tom Rini
2013-08-05 21:09 ` Stephen Warren
2013-08-05 21:20 ` Tom Rini
2013-08-05 21:08 ` Dennis Gilmore
2013-08-05 22:06 ` Stephen Warren
2013-08-06 11:34 ` Wolfgang Denk
2013-08-05 19:01 ` Tom Rini
2013-08-05 20:11 ` Dennis Gilmore
2013-08-05 20:25 ` Tom Rini
2013-08-05 20:54 ` Dennis Gilmore
2013-08-05 21:02 ` Tom Rini
2013-08-05 20:45 ` Stephen Warren
2013-08-08 18:48 ` Dirk Müller
2013-08-08 20:01 ` Stephen Warren
2013-08-08 20:37 ` Tom Rini
2013-08-13 12:23 ` Dirk Müller
2013-08-10 21:02 ` Dennis Gilmore
2013-08-09 22:20 ` Stephen Warren
2013-08-09 22:49 ` Wolfgang Denk
2013-08-09 23:00 ` Stephen Warren
2013-08-10 4:35 ` Stephen Warren
2013-08-10 21:07 ` Dennis Gilmore
2013-08-12 13:56 ` Tom Rini
2013-08-10 10:11 ` Wolfgang Denk
2013-08-10 14:29 ` Adam Conrad
2013-08-10 21:05 ` Dennis Gilmore
2013-08-13 13:42 ` Tom Rini
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=52000966.8080003@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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