Dear =?utf-8?Q?Beno=C3=AEt_Th=C3=A9baudeau?=,
In message <2098801045.2303154.1344708456703.javamail.r...@advansee.com> you
wrote:
>
> I had thought about that, but there is an issue. main_loop() sets this env
> var,
> so if ver is made read-only and the env is stored somewhere (NVRAM, etc.),
> then
> after an update of U-Boot with a newer version (stored env untouched), ver
> will
> still indicate the older version. See commit 155cb01, which forgot to update
> the
No. main_loop() will always set this variable to the right value, no
matter what might be stored in the environment. Only if you then
change i later you may (temporarily) see a different value. But again
only until you reset the board.
The correct fix for this would be the introduction of variable types,
including flags like "read-only" (as for serial# or ethaddr) or
"volatile" (i. e. not included in saveenv, as for filesize etc.)
I have been thinking about this for a long time already, I just didn't
find time yet to implement it.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: w...@denx.de
A Vulcan can no sooner be disloyal than he can exist without
breathing.
-- Kirk, "The Menagerie", stardate 3012.4
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
