Hi Wolfgang,
On Mon, 18 Oct 2021 at 06:07, Wolfgang Denk wrote:
>
> Dear Simon,
>
> In message <20211016003339.723169-1-...@chromium.org> you wrote:
> >
> > Add a feature that brings in a .env file associated with the board
> > config, if present. To use it, create a file board/.env or
> > use CO
Dear Simon,
In message <20211016003339.723169-1-...@chromium.org> you wrote:
>
> Add a feature that brings in a .env file associated with the board
> config, if present. To use it, create a file board/.env or
> use CONFIG_ENV_SOURCE_FILE to set a filename.
That should be board//.env , right?
Re
One barrier to completing the 7-year-long Kconfig migration is that
the default environment is implemented using ad-hoc CONFIG options.
At present U-Boot environment variables, and thus scripts, are defined
by CONFIG_EXTRA_ENV_SETTINGS.
It is not really feasible to move the environment to Kconfig
3 matches
Mail list logo