From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Date: Fri, 25 Jan 2013 17:11:27 -0500 Subject: [U-Boot] [U-Boot, v2, 1/1] omap4: allow the use of a plain text env file instead boot scripts In-Reply-To: <1357566680-29376-1-git-send-email-javier.martinez@collabora.co.uk> References: <1357566680-29376-1-git-send-email-javier.martinez@collabora.co.uk> Message-ID: <20130125221127.GD30402@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 Mon, Jan 07, 2013 at 03:51:20AM -0000, Javier Martinez Canillas wrote: > For production systems it is better to use script images since > they are protected by checksums and carry valuable information like > name and timestamp. Also, you can't validate the content passed to > env import. > > But for development, it is easier to use the env import command and > plain text files instead of script-images. > > Since both OMAP4 supported boards (Panda and TI SDP4430) are used > primarily for development, this patch allows U-Boot to load env var > from a text file in case that an boot.scr script-image is not present. > > The variable uenvcmd (if existent) will be executed (using run) after > uEnv.txt was loaded. If uenvcmd doesn't exist the default boot sequence > will be started. > > Signed-off-by: Javier Martinez Canillas > Acked-by: Nishanth Menon Applied to u-boot-ti/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: