From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] omap5: Allow use of a plain text env file
Date: Fri, 22 Mar 2013 21:03:48 -0400 [thread overview]
Message-ID: <514CFF74.2040208@ti.com> (raw)
In-Reply-To: <1363992223-1628-1-git-send-email-nm@ti.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 03/22/2013 06:43 PM, Nishanth Menon 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 OMAP5evm/uevm boards are used primarily for
> development, we allow 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.
>
> Inspired by commit: d70f54808dfa83b574e1239c3eccbcf3317343e1
> (omap4: allow the use of a plain text env file instead boot
> scripts)
>
> Signed-off-by: Nishanth Menon <nm@ti.com>
OK, Sricharan is also working on something like this, with a few other
changes as well (Use zImage, load fdt). I suspect we'll be taking
that in.
- --
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJRTP9zAAoJENk4IS6UOR1WtFcP/2f9sqpaf9lyUQNNLN0IjV8v
3Bk1ykqcduRb4RElnnr/7g2EFu3MEdXYiZm8Rh7AN1ByFc69Zf5iGZFmZ3N2ZSRe
UGNR2i2tYCdft1SFUHsbxopfwfmGddWDosxHbcbvYgTpwKelABdw8TURHK8DIyx9
gWcwBygAKz1dQrCFljZW4Ev8v0ORQiJq++eMUO6SS0zxmr4D5hVorvt0xrzs91r5
J7igypwLM6mX1Lpz/1P3Sf5IC2ZeK6hsvbiuE1FAFsnc0K14DU+MvFa9lDCq/RO1
Jfz5LTAbBE36J5+sSkiNouw3fdRbPAZ/noqYRLHGu4GQKACJzp0/dwJrlZUJ7Fvq
MnT+OPbB/WxEM8y12JD1WbJWKnee5oL1zB24N/pwc24VALwBrlhgLn7wzzp7uk1+
VHgihciomPkzxDk9toCx1IAtYlOoabC5pPeB83AJ3JpCv5J1HnuUqG7UABc2BSn/
xrVKV+qVAjP1DKLOJ84MST0jcjhjp9XyVo8+MXgfxi66UuUMjatUdB4RyXvJfJfF
Ooqze4jxkFAq9G9PKp5t0TFbPgWVwYZYEleyp7ClGTMMLrHcbFDQ2vCHoQPJaeaT
wEng+cz350zY1tezj2JwE91cn9L+NUYvSxfV+SgXuasCtmyI86ziFgGBE2Juyk/P
MwBBZPuF58cSbGK4Z1bp
=0lCX
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-03-23 1:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-22 22:43 [U-Boot] [PATCH] omap5: Allow use of a plain text env file Nishanth Menon
2013-03-23 0:23 ` Wolfgang Denk
2013-03-23 1:07 ` Tom Rini
2013-03-23 1:03 ` Tom Rini [this message]
2013-03-23 15:27 ` Nishanth Menon
2013-03-24 4:20 ` Sricharan R
2013-03-25 2:39 ` Nishanth Menon
2013-03-25 4:46 ` Sricharan R
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=514CFF74.2040208@ti.com \
--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 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.