public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
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 16:06:28 -0600	[thread overview]
Message-ID: <520021E4.4070500@wwwdotorg.org> (raw)
In-Reply-To: <20130805160846.74d29cea@adria.ausil.us>

On 08/05/2013 03:08 PM, Dennis Gilmore wrote:
> Hi Wolfgang,
> 
> On Mon, 05 Aug 2013 22:43:39 +0200
> Wolfgang Denk <wd@denx.de> wrote:
> 
>> Dear Dennis,
>>
>> In message <20130805145059.14c35ebf@adria.ausil.us> you wrote:
>>>
>>> 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 
>>
>> Where exactly do you raw the line here?  Do we have to support RAID /
>> DM devices, too?  What about LVM?  If you look for "regular system
>> usage", using such technologies is more or less standard today.  Will
>> we need that?
>
> I think not supporting dm or lvm is fine. raid1 mdraid for /boot would
> be nice down the road. I say this from the view of an enterprise arm
> based server hardware with a pair of sas drives for the filesystem. I
> would think that the vendor that produces said hardware would be on the
> hook for writing the support. what we need to ensure is that the
> installer know what valid options it can support are. if we can't
> do /boot on raid we cant do it. 

Do we even know this on x86?

Perhaps so, since the distro installs grub, and knows which version of
grub is installed, and hence knows if it supports RAID-1?

Pluggable protocol modules a la UEFI would solve that;-)

  reply	other threads:[~2013-08-05 22:06 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
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 [this message]
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=520021E4.4070500@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