From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4 0/3] env: Add CONFIG_ENV_FULL_SUPPORT
Date: Tue, 15 Oct 2019 11:28:01 +0200 [thread overview]
Message-ID: <20191015092801.4A8BA240045@gemini.denx.de> (raw)
In-Reply-To: <4f291ed4861b42b0af5a567901d2a9fd@SFHDAG6NODE3.st.com>
Dear Patrick,
In message <4f291ed4861b42b0af5a567901d2a9fd@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: wd at 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.16806@netlabs.com>
prev parent reply other threads:[~2019-10-15 9:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-03 7:24 [U-Boot] [PATCH v4 0/3] env: Add CONFIG_ENV_FULL_SUPPORT Patrick Delaunay
2019-10-03 7:24 ` [U-Boot] [PATCH v4 1/3] env: correct the check of env_flags_validate presence Patrick Delaunay
2019-10-03 13:18 ` Tom Rini
2019-10-03 7:24 ` [U-Boot] [PATCH v4 2/3] env: introduce macro ENV_IS_IN_SOMEWHERE Patrick Delaunay
2020-03-18 16:03 ` Patrick DELAUNAY
2019-10-03 7:24 ` [U-Boot] [PATCH v4 3/3] env: Add CONFIG_ENV_FULL_SUPPORT Patrick Delaunay
2020-03-18 16:06 ` Patrick DELAUNAY
2019-10-07 17:56 ` [U-Boot] [PATCH v4 0/3] " Wolfgang Denk
2019-10-07 22:36 ` Tom Rini
2019-10-08 11:09 ` Wolfgang Denk
2019-10-14 14:46 ` Patrick DELAUNAY
2019-10-15 9:28 ` Wolfgang Denk [this message]
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=20191015092801.4A8BA240045@gemini.denx.de \
--to=wd@denx.de \
--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