From: Tom Rini Date: Tue, 4 Feb 2014 17:05:36 -0500 Subject: [U-Boot] [PATCH V2 2/2] pxe: implement fdtdir extlinux.conf tag In-Reply-To: <1390945810-26477-2-git-send-email-swarren@wwwdotorg.org> References: <1390945810-26477-1-git-send-email-swarren@wwwdotorg.org> <1390945810-26477-2-git-send-email-swarren@wwwdotorg.org> Message-ID: <20140204220536.GL7049@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Tue, Jan 28, 2014 at 02:50:10PM -0700, Stephen Warren wrote: > From: Stephen Warren > > People who write (or scripts that auto-generate) extlinux.conf don't > want to know about HW-specific information such as FDT filenames. Create > a new extlinux.conf tag "fdtdir" that specifies only the directory where > FDT files are located, and defer all knowledge of the filename to U-Boot. > The algorithm implemented is: > > ========== > if $fdt_addr_r is set: > if "fdt" tag was specified in extlinux.conf: > load the FDT from the filename in the tag > else if "fdtdir" tag was specified in extlinux.conf: > if "fdtfile" is set in the environment: > load the FDT from filename in "$fdtfile" > else: > load the FDT from some automatically generated filename > > if no FDT file was loaded, and $fdtaddr is set: > # This indicates an FDT packaged with firmware > use the FDT at $fdtaddr > ========== > > A small part of an example /boot/extlinux.conf might be: > > ========== > LABEL primary > LINUX zImage > FDTDIR ./ > > LABEL failsafe > LINUX bkp/zImage > FDTDIR bkp/ > ========== > > ... with /boot/tegra20-seaboard.dtb or /boot/bkp/tegra20-seaboard.dtb > being loaded by the sysboot/pxe code. > > Signed-off-by: Stephen Warren Applied to u-boot/master, thanks! -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: Digital signature URL: