From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeroen Hofstee Date: Sun, 10 Aug 2014 18:53:54 +0200 Subject: [U-Boot] [PATCH 1/3] config: introduce a generic $bootcmd In-Reply-To: <53E6E2D0.7090303@wwwdotorg.org> 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> Message-ID: <53E7A3A2.80707@myspectrum.nl> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de 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