[U-Boot] [PATCH 00/11] Introduce variables whitelisting in environment

[Lukasz Majewski]

Hi Quentin,

> 2) Why do we consider ENV_IS_NOWHERE an invalid environment? The only
> place I found a use for it was to just say that if the environment is
> invalid, we should set to default environment (in env_relocate in
> env/common.c). With my patch series I guess that we could remove this
> fallback and force ENV_IS_NOWHERE to be always there.

It is perfectly valid to use ENV_IS_NOWHERE to get envs from hardcoded
board file (for example for production u-boot).

However, some time ago we had extension in the envs to get the support
for envs from different mediums (with set priorities).

Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20171226/1b8894d9/attachment.sig>