From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Warren Date: Thu, 13 Feb 2014 17:32:52 -0700 Subject: [U-Boot] [PATCH V4 2/3] ARM: tegra: rework boot scripts In-Reply-To: <20140213111644.345a78aa@adria.ausil.us> References: <1391617499-15939-1-git-send-email-swarren@wwwdotorg.org> <1391617499-15939-2-git-send-email-swarren@wwwdotorg.org> <20140213051322.45d87415@adria.ausil.us> <52FCF54D.40503@wwwdotorg.org> <20140213111644.345a78aa@adria.ausil.us> Message-ID: <52FD6434.9040505@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 02/13/2014 10:16 AM, Dennis Gilmore wrote: > On Thu, 13 Feb 2014 09:39:41 -0700 > Stephen Warren wrote: > >> On 02/13/2014 04:13 AM, Dennis Gilmore wrote: >>> Hi Stephen, >>> >>> I noticed one issue >>> >>> On Wed, 5 Feb 2014 09:24:58 -0700 >>> Stephen Warren wrote: >>> >>>> From: Stephen Warren >>>> >>>> Update the common Tegra boot scripts in the default environment to >>>> >>>> a) Make use of the new "test -e" shell command to avoid some error >>>> messages. >>>> >>>> b) Allow booting using the sysboot command and extlinux.conf. This >>>> allows easy creation of boot menus, and provides a simple >>>> interface for distros to parameterize/configure the boot process. >> >>>> diff --git a/include/configs/tegra-common-post.h >>>> b/include/configs/tegra-common-post.h index >> >>>> + "do_sysboot_boot=" >>>> \ >>>> + "sysboot ${devtype} ${devnum}:${rootpart} any >>>> " \ >>>> + "${scriptaddr} >>>> ${prefix}extlinux.conf\0" \ >>> >>> extlinux config files are placed into an extlinux directory >>> you will need to use ${prefix}extlinux/extlinux.conf >> >> What places them there? The spec doesn't say anything about placement >> of this file. Since this is a new feature, I don't think there's any >> de-facto standard, is there? I'd prefer that the files be placed in >> the same location as any other boot file, to avoid pointless extra >> directory levels (i.e. / for a partition that's mounted as /boot, or >> in /boot for a partition that's mounted as /). > > > http://www.syslinux.org/wiki/index.php/EXTLINUX > > anaconda and the image creation tools both use /boot/extlinux > according to http://shallowsky.com/linux/extlinux.html debian also uses > it OK. I wasn't aware that people were using these config files for anything yet; I thought it was something new being rolled out to get bootloader-agnostic boot config on ARM, and assumed that non-ARM was still using e.g. grub etc. Neither of those links specify that the extlinux.conf file has to be named (/boot)/extlinux/extlinux.conf. The first link simply specifies that it's possible to put the file in such a sub-directory, and the second that Debian just happens to do so. Still, in the interests of conforming to the de-facto standard, I'll repost the Tegra and bcm2835 boot script patches to adjust to that. > extlinux is not bootloaderspec. bootloaderspec does say where to put > them: > > Inside the $BOOT/loader/entries/ directory each OS vendor may drop one > ... Ah right. I'd meant to say that bootloaderspec doesn't say anything about an "extlinux/" directory, not to say that it didn't say anything about where to put the files.