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 V2] add README.distro file
Date: Sun, 11 Jan 2015 10:54:03 -0700	[thread overview]
Message-ID: <54B2B8BB.1070005@wwwdotorg.org> (raw)
In-Reply-To: <1420969535.11796.125.camel@hellion.org.uk>

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).

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.

When adding support for config_distro_bootcmd.h to any board that
doesn't support boot.scr already, I would not expect boards to want to
start supporting boot.scr; it's a legacy method as far as
config_distro_bootcmd.h is concerned.

(config_distro_bootcmd.h should be updated to make the boot.scr support
optional, so it doesn't get enabled unless specifically requested, when
boards add #include <config_distro_bootcmd.h>).

Supporting boot.scr may well be useful for a variety of non-Linux or
legacy environments, so I'm not proposing anyone rip out support for it.
Simply not add support for it if it hasn't been necessary already.

  reply	other threads:[~2015-01-11 17:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-22 20:46 [U-Boot] [PATCH V2] add README.distro file Stephen Warren
2014-12-28  9:26 ` Ian Campbell
2015-01-05 19:50   ` Stephen Warren
2015-01-11  9:45   ` Ian Campbell
2015-01-11 17:54     ` Stephen Warren [this message]
2015-01-11 18:15       ` Tom Rini
2015-01-12 17:34         ` Stephen Warren
2015-01-12 17:57           ` Ian Campbell
2015-01-12 18:47             ` Stephen Warren
2015-01-12 19:57             ` Sjoerd Simons
2015-01-12 22:41               ` Dennis Gilmore
2015-01-23 17:48             ` Rob Herring
2014-12-28 10:09 ` Ian Campbell
2015-01-05 19:55   ` Stephen Warren
2015-01-10 18:44     ` Dennis Gilmore
2015-01-12 17:36       ` Stephen Warren

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=54B2B8BB.1070005@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