From: "Benoît Thébaudeau" <benoit.thebaudeau@advansee.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 5/5] Add env var giving the board revision
Date: Sat, 11 Aug 2012 21:11:32 +0200 (CEST) [thread overview]
Message-ID: <1666183421.2304101.1344712292461.JavaMail.root@advansee.com> (raw)
In-Reply-To: <201208111348.33937.vapier@gentoo.org>
Hi Mike,
On Saturday 11 August 2012 19:48:33 Mike Frysinger wrote:
> On Friday 10 August 2012 13:46:08 Beno?t Th?baudeau wrote:
> > The board revision can be a useful env var, like its serial number.
>
> unless i missed something, there is no standard "rev" variable today,
> which
> means this change can easily break anyone who happens to already be
> using a
> variable named "rev".
I have searched such a usage in the tree, but did not find any, so this should
not break anything.
> i also don't see value here in hardcoding another variable that:
> - no one is setting
Well, I am setting it for my local boards that are not yet ready for upstream,
so I thought that it could also be useful for others.
> - is way too generic (rev of *what* ? cpu ? board ? u-boot ?
> something else ?)
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.
> - adds nothing on top of the existing "serial#"
This is all the contrary. If you think that a rev variable would be useless,
then you can also remove the serial# variable. And if you mean that a rev
variable would duplicate the serial# information, this is wrong: The serial#
variable gives a UID for a board, while the rev variable would give the hardware
revision of that board. These are completely different things, and the board
revision can not always be easily derived from its serial number.
> so NAK from me
> -mike
Best regards,
Beno?t
next prev parent reply other threads:[~2012-08-11 19:11 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 [this message]
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
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=1666183421.2304101.1344712292461.JavaMail.root@advansee.com \
--to=benoit.thebaudeau@advansee.com \
--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