On Sun, Jan 11, 2015 at 10:54:03AM -0700, Stephen Warren wrote: > On 01/11/2015 02:45 AM, Ian Campbell wrote: > > On Sun, 2014-12-28 at 09:26 +0000, Ian Campbell wrote: > >>> +boot_scripts: > >>> + > >>> + The name of U-Boot style boot.scr files that $bootcmd searches for. > >>> + > >>> + Example: boot.scr.uimg boot.scr > >>> + > >>> + (Typically we expect extlinux.conf to be used, but execution of > >>> boot.scr is > >>> + maintained for backwards-compatibility.) > >> > >> I'm slightly concerned by the implied deprecation of the boot.scr method > >> here, since at least Debian uses boot.scr exclusively and not the > >> extlinux stuff. Will boot.scr be maintained going forward or are there > >> plans to eventually remove it? > > > > Can someone confirm that there is no long term plan to drop boot.scr > > support? > > extlinux.conf *is* the standard Linux boot process that > config_distro_bootcmd.h enables. boot.scr is *not*. The whole point is > to introduce a new simple standard that works the same everywhere (for > Linux: across boards, across distros, across bootloaders).
Well, the only problem I see with this statement is that, uh, do we have buy-in from Debian? > I would expect boot.scr support to be maintained indefinitely for any > board the currently supports it. I certainly know of no plan to remove > any existing support for it, and am not going to make such a plan. "boot.scr" is just a "boot script" with the appropriate legacy image header on it. That won't go away until U-Boot no longer supports legacy images, and there is currently no plan to actually drop that support. -- Tom
signature.asc
Description: Digital signature
_______________________________________________ U-Boot mailing list [email protected] http://lists.denx.de/mailman/listinfo/u-boot
