From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] environment expectations of config_distro_bootcmd.h
Date: Mon, 29 Sep 2014 11:17:26 -0600 [thread overview]
Message-ID: <54299426.5020408@wwwdotorg.org> (raw)
In-Reply-To: <1411914651.23482.29.camel@hellion.org.uk>
On 09/28/2014 08:30 AM, Ian Campbell wrote:
> Is there any documentation as to what environment variables a platform
> must provide if it uses config_distro_bootcmd.h. ${scriptaddr} seems
> clear but what about e.g. kernel_addr_r and friends? I suppose the use
> of the pxe commands has some implicit dependencies (pxe_addr_r?)
>
> Along the same lines is there any documentation regarding which
> variables a boot.scr which expects to be called via this mechanism can
> rely on. e.g. devtype/devnum/bootpart/prefix etc. Also foo_addr_r again
> I suppose?
>
> There is some info in the README but it says things like "these
> variables don't have to be defined for all boards" and worse "some
> boards use these variables for other purposes." ;-)
Dennis did write the following when he first sent the patch to create
include/config_distro_bootcmd.h:
http://patchwork.ozlabs.org/patch/332412/
[U-Boot,1/6] add README.distro file
However, I only cleaned up and resent patch 2 in that series:
http://patchwork.ozlabs.org/patch/332413/
[U-Boot,2/6] add header with a generic set of boot commands defined.
... so the README isn't in place at present.
next prev parent reply other threads:[~2014-09-29 17:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-28 14:30 [U-Boot] environment expectations of config_distro_bootcmd.h Ian Campbell
2014-09-29 17:17 ` Stephen Warren [this message]
2014-09-29 17:33 ` Otavio Salvador
2014-09-30 7:11 ` Ian Campbell
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=54299426.5020408@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.