[U-Boot] [PATCHv2] scripts: Add script to extract default environment

[Simon Glass]

Hi,

On 27 September 2016 at 07:37, Lukasz Majewski <l.majewski at majess.pl> wrote:
> Hi Simon,
>
>> Hi Lukasz,
>>
>> On 16 September 2016 at 22:57, Lukasz Majewski <l.majewski at majess.pl>
>> wrote:
>> > This script looks for env_common.o object file and extracts from it
>> > default u-boot environment, which is afterwards printed on standard
>> > output.
>> >
>> > Usage example:
>> > get_default_envs.sh > u-boot-env-default.txt
>> >
>> > The generated text file can be used as input for mkenvimage.
>> >
>> > Signed-off-by: Lukasz Majewski <l.majewski at majess.pl>
>> >
>> > ---
>> > Changes for v2:
>> > - Sort uniquely entries
>> > - Exclude env_common.o generated for SPL
>> > ---
>> >  scripts/get_default_envs.sh | 34 ++++++++++++++++++++++++++++++++++
>> >  1 file changed, 34 insertions(+)
>> >  create mode 100755 scripts/get_default_envs.sh
>>
>> Reviewed-by: Simon Glass <sjg at chromium.org>
>>
>> But why is this needed?
>
> Some boards for production u-boot have all the envs hardcoded in
> their ./include/configs/<board>.h file.
>
> Also, they support envs stored on persistent memory - like eMMC.
>
> During flashing both u-boot and envs are stored on the target memory.
> Such script allows having the same data in both places.
>
> I do know that I could also use external file, which I could include to
> u-boot during compilation and compile the boot.scr file with mkimage.
>
> Or maybe there is any other way?

Seems OK to me, I was just curious.

>
> Best regards,
> Łukasz Majewski

[...]