From: Stefan Althoefer <stefan.althoefer@web.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] common: nvedit to protect additional ethernet addresses Part 1/1
Date: Tue, 16 Dec 2008 22:34:01 +0100 [thread overview]
Message-ID: <gi96ps$f9o$1@ger.gmane.org> (raw)
In-Reply-To: <20081215225530.2466B832E8A1@gemini.denx.de>
Dear Wolfgang Denx,
>> But your suggested optimizations will only be effective if someone tries to
>> write to "serial#". This is not normally done (attempt can be considered
>> an error).
>
> Can it? What make you think so?
>
> There are lots of boards that come fresh out of production with a
> virgin environment, where setting "serial#" is a perfectly normal
> thing, and not an error at all.
Indeed, in the factory it is normal to set the serial number. Any later
attempt to "overwrite" it is an error (why the code rejects doing it).
-- Stefan
next prev parent reply other threads:[~2008-12-16 21:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-04 12:28 [U-Boot] [PATCH] common: nvedit to protect additional ethernet addresses Part 1/1 stefan.althoefer at web.de
2008-12-04 12:46 ` Jerry Van Baren
2008-12-04 17:57 ` Ben Warren
2008-12-04 20:48 ` Jerry Van Baren
2008-12-05 21:22 ` Stefan Althoefer
2008-12-07 0:43 ` Wolfgang Denk
2008-12-07 2:53 ` Jerry Van Baren
2008-12-07 5:47 ` Ben Warren
2008-12-07 9:33 ` Wolfgang Denk
2008-12-07 13:31 ` Stefan Althoefer
2008-12-07 16:26 ` Wolfgang Denk
2008-12-07 18:54 ` Stefan Althoefer
2008-12-07 21:25 ` Wolfgang Denk
2008-12-07 23:52 ` Stefan Althoefer
2008-12-15 22:55 ` Wolfgang Denk
2008-12-16 21:34 ` Stefan Althoefer [this message]
2008-12-08 20:14 ` Jerry Van Baren
-- strict thread matches above, loose matches on Subject: below --
2008-12-04 20:06 Stefan Althöfer
2008-12-04 21:06 ` Ben Warren
2008-12-15 22:56 ` Wolfgang Denk
2008-12-16 19:15 ` Stefan Althoefer
2008-12-16 19:22 ` Ben Warren
2008-12-16 20:55 ` 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='gi96ps$f9o$1@ger.gmane.org' \
--to=stefan.althoefer@web.de \
--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