From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Default environment file
Date: Wed, 12 Jun 2019 10:16:27 -0400 [thread overview]
Message-ID: <20190612141627.GR7115@bill-the-cat> (raw)
In-Reply-To: <40cbe316-3556-2551-75e7-a0a0777dc792@denx.de>
On Wed, Jun 12, 2019 at 10:43:26AM +0200, Stefano Babic wrote:
> Hi Pascal,
>
> On 12/06/19 10:20, Linder Pascal wrote:
> > Hi everyone,
> >
> >
> > I am currently moving the configurations of the KM boards from header files to Kconfig. But for the customly defined environment variables I did not found a decent solution until I have come across the default environment file, which seems very interesting to me.
> >
> >
> > To this day, nevertheless, it appears that noone made use of the CONFIG_USE_DEFAULT_ENV_FILE configuration defined in env/Kconfig. Does anyone still have an example for this kind of environment definition or knows how to create it?
> >
> >
> > In my opinion, this could be highly relevant for the transition away from the header files in include/configs.
> >
>
> Fully agree. Rather, I do not think there is a relevant example. But the
> environment is something like data and should not be part of the header
> file as it is for histoical reason. I added some times ago a way to
> extract the environment from the header and make the transition easy
> (see make u-boot-initial-env). And if the environment is split from the
> header as CONFIG_USE_DEFAULT_ENV_FILE allows, it is also easier to set
> an own environment via OE BSP layer without pushing for each small
> change to U-Boot. Not only, environments often conflict, and what is
> good for a project becomes evil for another one.
With the high-level goal of being able to eliminate the include/configs
file, we need to figure out a better solution to dealing with the
default environment. Shuffling things into include/environment/ has
been the first step I've tried but I'm absolutely not tied down to this
and if people are motivated to push in a new solution to this overall
problem I'm happy to see it happen. This sounds like a good overall
idea.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190612/27e72a5e/attachment.sig>
next prev parent reply other threads:[~2019-06-12 14:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 8:20 [U-Boot] Default environment file Linder Pascal
2019-06-12 8:41 ` Lukasz Majewski
2019-06-12 8:43 ` Stefano Babic
2019-06-12 9:17 ` Rasmus Villemoes
2019-06-12 14:16 ` Tom Rini [this message]
2019-06-12 16:30 ` Stefano Babic
2019-06-12 21:33 ` Vladimir Oltean
2019-06-13 10:59 ` Stefano Babic
2019-06-12 16:05 ` Frank Wunderlich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190612141627.GR7115@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox