public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jeroen Hofstee <dasuboot@myspectrum.nl>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 5/5] Add env var giving the board revision
Date: Sun, 12 Aug 2012 23:21:39 +0200	[thread overview]
Message-ID: <50281E63.4060902@myspectrum.nl> (raw)
In-Reply-To: <20120812210644.7B554202C07@gemini.denx.de>

On 08/12/2012 11:06 PM, Wolfgang Denk wrote:
> Dear =?utf-8?Q?Beno=C3=AEt_Th=C3=A9baudeau?=,
>
> In message <1323086777.2324156.1344780597072.JavaMail.root@advansee.com> you wrote:
>> Anyway, when you will have implemented read-only and volatile flags for env
>> vars, this patch will no longer be needed. But with the current code, there is
>> no way board-specific code can create a board revision env var and make it
>> read-only, except with this patch.
> Correct, so far we don't support custom read-only variables.  But if
> we add these, then in a generic way, and definitely not for a single,
> specific variable.   This is a lesson we learned form experience.
>
I didn't follow this thread, but would it be an option to create a command
for these kind of things, instead of read-only variables? e.g. some like

if get revision out; then;
     echo $out;
else;
     echo revision not supported
fi;

Just a though, regards,

Jeroen

  reply	other threads:[~2012-08-12 21:21 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-10 17:44 [U-Boot] [PATCH 0/5] Cleanup and extend env vars Benoît Thébaudeau
2012-08-10 17:45 ` [U-Boot] [PATCH 1/5] fw_env: Add env vars describing U-Boot target board Benoît Thébaudeau
2012-09-18 19:04   ` [U-Boot] [U-Boot, " Tom Rini
2012-08-10 17:45 ` [U-Boot] [PATCH 2/5] env_common: Add missing ethprime Benoît Thébaudeau
2012-09-18 19:05   ` [U-Boot] [U-Boot,2/5] " Tom Rini
2012-08-10 17:45 ` [U-Boot] [PATCH 3/5] env import/export: Remove from help if disabled Benoît Thébaudeau
2012-08-11 17:48   ` Mike Frysinger
2012-09-18 19:05   ` [U-Boot] [U-Boot, " Tom Rini
2012-08-10 17:45 ` [U-Boot] [PATCH 4/5] README: The ver env var is not read-only Benoît Thébaudeau
2012-08-11 17:48   ` Mike Frysinger
2012-08-11 18:07     ` Benoît Thébaudeau
2012-08-12 11:54       ` Wolfgang Denk
2012-08-12 13:58         ` Benoît Thébaudeau
2012-08-12 14:49           ` Mike Frysinger
2012-08-13 13:01             ` [U-Boot] [PATCH] README: Update ver env var description Benoît Thébaudeau
2012-08-17  4:20               ` Mike Frysinger
2012-09-02 16:56               ` Wolfgang Denk
2012-08-12 11:49     ` [U-Boot] [PATCH 4/5] README: The ver env var is not read-only Wolfgang Denk
2012-08-10 17:46 ` [U-Boot] [PATCH 5/5] Add env var giving the board revision Benoît Thébaudeau
2012-08-11 17:48   ` Mike Frysinger
2012-08-11 19:11     ` Benoît Thébaudeau
2012-08-12 11:58       ` Wolfgang Denk
2012-08-12 14:02         ` Benoît Thébaudeau
2012-08-12 14:09           ` Benoît Thébaudeau
2012-08-12 21:06             ` Wolfgang Denk
2012-08-12 21:21               ` Jeroen Hofstee [this message]
2012-08-12 14:54           ` Mike Frysinger
2012-08-12 17:11             ` Benoît Thébaudeau
2012-08-12 21:20               ` Wolfgang Denk
2012-08-12 21:35                 ` Benoît Thébaudeau
2012-08-13  9:59                   ` Wolfgang Denk
2012-08-13  0:28               ` Mike Frysinger
2012-08-12 21:05           ` Wolfgang Denk
2012-08-12 11:51   ` Wolfgang Denk

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=50281E63.4060902@myspectrum.nl \
    --to=dasuboot@myspectrum.nl \
    --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