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, 12 Aug 2014 11:46:19 -0600	[thread overview]
Message-ID: <53EA52EB.1030101@wwwdotorg.org> (raw)
In-Reply-To: <53EA4EDE.7030904@myspectrum.nl>

On 08/12/2014 11:29 AM, Jeroen Hofstee wrote:
> On 11-08-14 20:55, Stephen Warren wrote:
...
>> extlinux.conf is a text file format the defines a menu of bootable
>> OSs. It's a (de-facto I suppose) standard that's implemented by
>> extlinux (if indeed that is a piece of SW:-) and also U-Boot and
>> barebox and likely other bootloaders too.
>>
>> So, when U-Boot locates extlinux.conf on disk and processes it, it's
>> parsing a configuration file/menu, not chain-loading/executing another
>> bootloader.
>>
>
> I see, so shouldn't we document then who is in charge of its format
> at least, before we start making a U-boot/distro specific version of it?

The content of the file is documented at:

http://www.freedesktop.org/wiki/Specifications/BootLoaderSpec/

... although extlinux.conf is a single file containing all the entries, 
rather than a separate *.conf per OS. I'm not sure where that aspect of 
the file is documented. Dennis, do you know where?

FWIW, the concept of a single file rather than many *.conf has been 
embodied in U-Boot's pxe and sysboot commands for some time, and isn't 
anything to do with this patch set.

  reply	other threads:[~2014-08-12 17:46 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
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 [this message]
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=53EA52EB.1030101@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