From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Warren Date: Tue, 12 Aug 2014 11:46:19 -0600 Subject: [U-Boot] [PATCH 1/3] config: introduce a generic $bootcmd In-Reply-To: <53EA4EDE.7030904@myspectrum.nl> References: <1406759836-556-1-git-send-email-swarren@wwwdotorg.org> <53E25145.2090706@wwwdotorg.org> <53E4F400.6060508@wwwdotorg.org> <53E63816.60703@redhat.com> <53E6A3FE.6080807@myspectrum.nl> <53E6E2D0.7090303@wwwdotorg.org> <53E7A3A2.80707@myspectrum.nl> <53E8F50A.1060606@wwwdotorg.org> <53E90294.7060604@myspectrum.nl> <53E905AC.9050903@wwwdotorg.org> <53E90E90.4020204@myspectrum.nl> <53E911AF.4080908@wwwdotorg.org> <53EA4EDE.7030904@myspectrum.nl> Message-ID: <53EA52EB.1030101@wwwdotorg.org> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de 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.