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

[Simon Glass]

Hi Otavio,

On Mon, Oct 28, 2013 at 7:34 AM, Otavio Salvador
<otavio at ossystems.com.br> wrote:
> Hello,
>
> On Sat, Oct 26, 2013 at 3:01 AM, Simon Glass <sjg at chromium.org> 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 a board/<vendor>/env
>> directory called <board>.env (or common.env if you want the same
>> environment for all boards).
>>
>> The environment variables should be of the form "var=value". Values can
>> extend to multiple lines. See the README under 'Environment Variables:'
>> for more information and an example.
>>
>> Comments are not permitted in the environment with this commit.
>>
>> Signed-off-by: Simon Glass <sjg at chromium.org>
>
> I think people (or myself) are misunderstanding what this patch does.

Possibly, I'm not sure.

>
> My understand is:
>
>  - it allow moving environment setting to a .env file
>  - it needs to include the environment at /build/ time

Yes

>
> This does improve a lot the current status (and I really appreciate
> it); one missing thing (or I missed it completely) is a way to:
>
>  - build u-boot (binary)
>  - generate a binary version of the environment
>  - glue both together in a way the new environment /replaces/ the
> default environment originally written inside u-boot (binary)
>
> Am I missing something?

This is something that Wolfgang would like to see (as would I), but I
think it is a separate feature. This feature is just trying to
simplify creation of the build-time default environment.

Regards,
Simon