From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Warren Date: Mon, 29 Sep 2014 11:17:26 -0600 Subject: [U-Boot] environment expectations of config_distro_bootcmd.h In-Reply-To: <1411914651.23482.29.camel@hellion.org.uk> References: <1411914651.23482.29.camel@hellion.org.uk> Message-ID: <54299426.5020408@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 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.