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.r...@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
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
