Dear Patrick,
In message <4f291ed4861b42b0af5a567901d2a...@sfhdag6node3.st.com> you wrote:
>
> Perhaps I not correctly understood the initial issue,
> but I do my best to have the same level of ENV features
> (CONFIG_ENV_FULL_SUPPORT activate the features and
> extensions= attribute / callback / flags)
> between U--Boot proper, SPL and TPL.
You understood correctly: these should always be the same.
> With the serie
> => when read from device (ENV_IS_IN....) is not supported ENV is still
> supported in SPL/TPL with (SPL_TPL_)ENV_IS_NOWHERE with
> same feature level than U-Boot (only the default env is supported)
> => the only remaining issue today after my serie is the size of this default
> environment (default_environment[]) in SPL and TPL.
> The content of this variable need to have the same content in SPL/TPL
> than in U-Boot proper ?
It would feel strange if it had different content, but I did not
spend much time on this thought (and practical use cases) yet.
In the olden days you usually wanted to have the console baud rate
setting from the envrinment, and not much else. Things have changed
a lot. Sorry, I can't really tell...
Best regards,
Wolfgang Denk
--
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: w...@denx.de
If I don't document something, it's usually either for a good reason,
or a bad reason. In this case it's a good reason. :-)
- Larry Wall in <1992jan17.005405.16...@netlabs.com>
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
