From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, v2, 1/1] omap4: allow the use of a plain text env file instead boot scripts
Date: Fri, 25 Jan 2013 17:11:27 -0500 [thread overview]
Message-ID: <20130125221127.GD30402@bill-the-cat> (raw)
In-Reply-To: <1357566680-29376-1-git-send-email-javier.martinez@collabora.co.uk>
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 <javier.martinez@collabora.co.uk>
> Acked-by: Nishanth Menon <nm@ti.com>
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: <http://lists.denx.de/pipermail/u-boot/attachments/20130125/62e6af43/attachment.pgp>
prev parent reply other threads:[~2013-01-25 22:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 13:51 [U-Boot] [PATCH v2 1/1] omap4: allow the use of a plain text env file instead boot scripts Javier Martinez Canillas
2013-01-11 20:55 ` Nishanth Menon
2013-01-19 14:20 ` Javier Martinez Canillas
2013-01-19 15:16 ` Tom Rini
2013-01-25 22:11 ` Tom Rini [this message]
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=20130125221127.GD30402@bill-the-cat \
--to=trini@ti.com \
--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