[U-Boot] [PATCH] Allow U-Boot scripts to be placed in a .env file

[Tom Rini <trini@ti.com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 05/06/2013 09:02 AM, Rob Herring wrote:
> On 04/17/2013 12:44 AM, Wolfgang Denk wrote:
>> Dear Simon Glass,
>> 
>> In message <1366155414-6525-1-git-send-email-sjg@chromium.org>
>> you wrote:
>>> At present U-Boot environment variables, and thus scripts, are
>>> defined by CONFIG_EXTRA_ENV_SETTINGS. It is painful to add
>>> large amounts of text to this file and dealing with quoting and
>>> newlines is harder than it should be. It would be better if we
>>> could just type the script into a text file and have it
>>> included by U-Boot.
>>> 
>>> Add a feature that brings in a .env file associated with the
>>> board config, if present. To use it, create a file in
>>> include/configs with the same name as you could board config
>>> file, except with a .env extension instead of a .h extension.
>>> The variables should be separated by \0. Comments are
>>> permitted, using # as the first character in a line.
>> 
>> Please do not litter the include/configs/ directory with such
>> stuff. It's more than big enough already.  Please put such files
>> into the respective board directories.
>> 
>> And if you do something like this, then please go the way to the
>> end. Forget about the \0 termination, make it a plain text file
>> instead, something that can be used with "env import -t" as well
>> (or created with "env export -t").
> 
> What about allowing a binary created with mkenvimage to be
> built-in. This would give us a standard build rule to build a
> separate env binary as well.

With CONFIG_ENV_IS_EMBEDDED you should be able to do this today since
it has to be at a certain spot within the binary, yes?

- -- 
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJRh6zKAAoJENk4IS6UOR1WOT0P/2B1UX74nij7Z+8NJtiA/Ak5
QZlQw/tk7afZCOYPOxLnun6OCH6irWEPykBvtHGa3ww3f2L/lt8Kk3VTZprhhvTz
+s8YzDgFRAzPPbVfA5KSI2PUS0exNjVbQ8/mA+h8tPZ6G3XBsJCrvNyf6zGRUQK9
kr+RrZFUor0Z5xMyTOmba0rkTIKPmGLu+YhUQmFqCM0+5sjP0D+zpN68s89FwVah
Vxuf2Li7QmDp3PLNJphUFb67Vw/+JUCP+TZ/yLnAZlBScxTfNXPBspOlU3CkK4Dl
NgmfwAnd1wp8QCERWQD/jXFhjGY21QbogIvxs4tQWJ0TUxQnrFnCaX6iCwSe+kBE
Aesn/g+NhgQaj3GPJi5SvOwF5gXZPxXzvtywtoIMKeAoNC46JSk1y0wde7xzh4VP
0zrXRqE3SXW1wPKsKEBBUbE5F/tHiE1PxK2SRo5zq0s2gsPFLo2HT4G1sxE1XxVR
nft0TJ8EGaZ9h5B/sg1HFoT6ezMcoKjy/X7zVyBgUChIta9eJAUIwqAK3XNqSwhK
m5aWCqXDe03zufZ9M1dn9yWoKu4esyPdPQzUHcRZnbpVtKNpNN9obkF3s/LBqYme
9qyIf6DNTxBSV4NHB6PAT7ltrO6jau5mqkINtElSII6mf7A1OLUNZ/jLdkee2M07
tvi2uk6coQPwGTKr06aS
=Bk9E
-----END PGP SIGNATURE-----