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] [PATCH 1/3] config: introduce a generic $bootcmd
Date: Tue, 05 Aug 2014 10:11:37 -0600	[thread overview]
Message-ID: <53E10239.4080103@wwwdotorg.org> (raw)
In-Reply-To: <CAPnjgZ3nUjanttPeQnkU2WLoo_Vb+9AQOwPT93nDOMtNx_vQJg@mail.gmail.com>

On 08/05/2014 06:27 AM, Simon Glass wrote:
> On 4 August 2014 12:04, Stephen Warren <swarren@wwwdotorg.org> wrote:
>> On 08/04/2014 04:13 AM, Simon Glass wrote:

>>> As to the question of HW description, I'm not sure I follow. The
>>> devices that are attached to the hardware presumably appear in the DT,
>>> the partition is fixed anyway, all you need to know is whether it is a
>>> bootable device or not. What part of the description is not related to
>>> the hardware?
>>
>> The concept of bootable, and the order in which bootable devices should be
>> searched, are SW policy, not HW definition.
>
> So that is it? I wonder whether if this is the only configuration
> option, we might eventually write this feature in C as a new U-Boot
> command, with an environment variable listing the devices in order?

It would certainly be possible to do that.

In some ways I prefer implementing this all as user-accessible macros. 
That way, if the user wants to tweak them, it's as simple as editing the 
macro and re-saving the environment, rather than rebuilding the 
bootloader from source.

Obviously, if someone changes something it may not work in the same way 
as originally intended, but it's not everybody's goal to boot a 
"standard" distro in a "standard" way - rather they may want to play 
around with their own custom ideas.

  reply	other threads:[~2014-08-05 16:11 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-30 22:37 [U-Boot] [PATCH 1/3] config: introduce a generic $bootcmd Stephen Warren
2014-07-30 22:37 ` [U-Boot] [PATCH 2/3] ARM: tegra: use new " Stephen Warren
2014-08-08 16:02   ` Simon Glass
2014-08-10 22:23   ` [U-Boot] [U-Boot,2/3] " Tom Rini
2014-07-30 22:37 ` [U-Boot] [PATCH 3/3] ARM: rpi_b: " Stephen Warren
2014-08-08  0:18   ` Simon Glass
2014-08-10 22:23   ` [U-Boot] [U-Boot,3/3] " Tom Rini
2014-07-31  1:55 ` [U-Boot] [PATCH 1/3] config: introduce a " Marek Vasut
2014-07-31 10:47 ` Ian Campbell
2014-07-31 15:30   ` Stephen Warren
2014-07-31 22:03 ` Simon Glass
2014-07-31 23:00   ` Stephen Warren
2014-08-04 10:13     ` Simon Glass
2014-08-04 11:58       ` Dennis Gilmore
2014-08-04 18:04       ` Stephen Warren
2014-08-05 12:27         ` Simon Glass
2014-08-05 16:11           ` Stephen Warren [this message]
2014-08-06 16:01 ` Stephen Warren
2014-08-06 16:56   ` Simon Glass
2014-08-08  0:17     ` Simon Glass
2014-08-08 16:00       ` Stephen Warren
2014-08-09 15:02         ` Hans de Goede
2014-08-09 21:55           ` Tom Rini
2014-08-09 22:43           ` Jeroen Hofstee
2014-08-10  3:11             ` Stephen Warren
2014-08-10 16:53               ` Jeroen Hofstee
2014-08-11 16:53                 ` Stephen Warren
2014-08-11 17:51                   ` Jeroen Hofstee
2014-08-11 18:04                     ` Stephen Warren
2014-08-11 18:42                       ` Jeroen Hofstee
2014-08-11 18:55                         ` Stephen Warren
2014-08-11 19:19                           ` Tom Rini
2014-08-11 22:15                             ` Stephen Warren
2014-08-12 17:29                           ` Jeroen Hofstee
2014-08-12 17:46                             ` Stephen Warren
2014-08-12 20:29                             ` Dennis Gilmore
2014-08-10 17:14   ` Dennis Gilmore
2014-08-10 22:23 ` [U-Boot] [U-Boot,1/3] " 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=53E10239.4080103@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