On 04/17/2013 12:44 AM, Wolfgang Denk wrote: > Dear Simon Glass, > > In message <[email protected]> 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. Rob _______________________________________________ U-Boot mailing list [email protected] http://lists.denx.de/mailman/listinfo/u-boot
