public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jeroen Hofstee <jeroen@myspectrum.nl>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/3] config: introduce a generic $bootcmd
Date: Sun, 10 Aug 2014 18:53:54 +0200	[thread overview]
Message-ID: <53E7A3A2.80707@myspectrum.nl> (raw)
In-Reply-To: <53E6E2D0.7090303@wwwdotorg.org>

Hello Stephan,

On 10-08-14 05:11, Stephen Warren wrote:
> The entire point of this series is to prevent distros from having to
> install bootloader-specific boot configuration files.
I fail to see why this is something to pursue. Since the distro knows
the boot path, why should u-boot be polling all possible options?

> As such, relying exclusively on boot.scr wouldn't be useful.
Seems like a logical thing to me, as long as the scripts itself
does not have to bother about board details, but is handed
those info.
> If we need to support other OSs, I think it'd be best to extend
> extlinux.conf to allow it to support booting OSs besides Linux.
It is not an OS issue.

> FWIW, if extlinux.conf isn't found on the media, this patch does fall
> back to searching for boot.scr (a uImage of a U-Boot script) so it's
> certainly possible to make custom things happen if you want.

Yes, and the order is wrong in my mind. If anything, it should fallback
to extlinux, but at least use a general boot.scr first. (or 
/boot/u-boot.conf
or whatever)

Regards,
Jeroen

  reply	other threads:[~2014-08-10 16:53 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
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 [this message]
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=53E7A3A2.80707@myspectrum.nl \
    --to=jeroen@myspectrum.nl \
    --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