Hi, > From: Patrick DELAUNAY <[email protected]> > Sent: jeudi 3 octobre 2019 09:24 > > This patch introduce a macro ENV_IS_IN_SOMEWHERE to check if the the > environment can be saved somewhere, in a storage medium, without assumption > on CONFIG$(SPL_TPL_)ENV_IS_NOWHERE. > > Since the commit 208bd2b85ecc ("env: allow ENV_IS_NOWHERE with other > storage target"), it is allowed to activated ENV_IS_NOWHERE with other > CONFIG_IS_IN... in U-Boot. > It is only allowed for U-Boot but the remaining restriction in Kconfig could > also > removed for SPL and TPL (depends on !SPL_ENV_IS_NOWHERE / depends on > !TPL_ENV_IS_NOWHERE). > > This macro ENV_IS_IN_SOMEWHERE can be used in code to check if the > environment for U-Boot / SPL / TPL is really managed (at least one > CONFIG$(SPL_TPL_)ENV_IS_IN_.. is activated). > > Signed-off-by: Patrick Delaunay <[email protected]> > ---
Hi Tom, I try to solve default environment size issue in patch = http://patchwork.ozlabs.org/patch/1257545/ [RFC RFT PATCH] env: spl: filter the variables in default environment of SPL or TPL But as it is not acceptable and I don't see other solution for this serie. I won't push v5 for this serie and I considere this serie abandoned. http://patchwork.ozlabs.org/patch/1171098/ Thanks Patrick
