Dear =?utf-8?Q?Beno=C3=AEt_Th=C3=A9baudeau?=,
In message <1666183421.2304101.1344712292461.javamail.r...@advansee.com> you
wrote:
>
> I have searched such a usage in the tree, but did not find any, so this should
> not break anything.
You cannot expect to see the real, production environments in the
mainline source tree.
> It could be renamed to hwrev, board_rev or whatever you like. This is not
> really
> an issue. Its purpose is the board hardware revision. The CPU revision can
> often
> be read from the CPU and is printed upon startup. U-Boot's revision already
> has
> the ver env var and the version command. On the contrary, the board revision
> can
> not always be determined by analyzing the hardware (OTP, fuses, EEPROM, GPIOs,
> etc.), so it can be useful to have an official env var to store it in the
> backed
> up env, exactly like for the serial# env var that can not always be stored in
> some dedicated hardware location.
As mentioned before, I don't see need for such a thing in general.
Any such use is highly board specific, and vendors use different ways
to address this.
I don't intend to apply this patch, sorry.
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
PoB = "Prisoner of Bill" -- those held captive, unwillingly or other-
wise, by the contemptible Microsoft monopoly.
-- Tom Christiansen in <6abo45$3lc$2...@csnews.cs.colorado.edu>
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
