From: Ian Campbell <ijc+uboot@hellion.org.uk>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH 1/2] sunxi: retrieve FEL-provided values to environment variables
Date: Sat, 12 Sep 2015 12:58:07 +0100 [thread overview]
Message-ID: <1442059087.24382.49.camel@hellion.org.uk> (raw)
In-Reply-To: <55F1CD2C.9080803@redhat.com>
On Thu, 2015-09-10 at 20:34 +0200, Hans de Goede wrote:
> [...]
>
> What if the user interrupts auto-boot with a fel provided boot.scr
> and then does "saveenv" ?
This is an interesting question which is more generic than just these
variable, i.e. it applies to some extent to "ipaddr" when someone does
"dhcp ; saveenv" too.
Grepping around to see if there was any special handling for ipaddr I
came across "Vendor Parameter Protection" in the top-level README as
well as "CONFIG_ENV_FLAGS_LIST_DEFAULT" (and _STATIC) and various
default settings in include/env_flags.h.
I think CONFIG_ENV_FLAGS_LIST_* are what we want, and we want fel* to
be flagged "r" for read only and perhaps given an appropriate type
(either "d" or "x" for decimal or hex respectively, I suppose).
Ian.
next prev parent reply other threads:[~2015-09-12 11:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 14:11 [U-Boot] [RFC PATCH 0/2] sunxi: support FEL-provided environment vars and "fel" boot target Bernhard Nortmann
2015-09-03 14:11 ` [U-Boot] [RFC PATCH 1/2] sunxi: retrieve FEL-provided values to environment variables Bernhard Nortmann
2015-09-10 18:34 ` Hans de Goede
2015-09-11 9:08 ` Bernhard Nortmann
2015-09-12 11:58 ` Ian Campbell [this message]
2015-09-12 12:24 ` Hans de Goede
2015-09-14 13:12 ` Bernhard Nortmann
2015-09-03 14:12 ` [U-Boot] [RFC PATCH 2/2] sunxi: add "fel" boot target Bernhard Nortmann
2015-09-10 18:36 ` Hans de Goede
2015-09-11 9:31 ` Bernhard Nortmann
2015-09-12 12:48 ` Hans de Goede
2015-09-13 7:15 ` Ian Campbell
2015-09-14 10:33 ` Siarhei Siamashka
2015-09-14 11:42 ` Hans de Goede
2015-09-14 11:46 ` Hans de Goede
2015-09-26 21:03 ` Siarhei Siamashka
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=1442059087.24382.49.camel@hellion.org.uk \
--to=ijc+uboot@hellion.org.uk \
--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