From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeroen Hofstee <dasuboot@myspectrum.nl>
Date: Sun, 12 Aug 2012 23:21:39 +0200
Subject: [U-Boot] [PATCH 5/5] Add env var giving the board revision
In-Reply-To: <20120812210644.7B554202C07@gemini.denx.de>
References: <1323086777.2324156.1344780597072.JavaMail.root@advansee.com>
	<20120812210644.7B554202C07@gemini.denx.de>
Message-ID: <50281E63.4060902@myspectrum.nl>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.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