From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] MAC address question...
Date: Thu, 26 Aug 2004 23:58:51 +0200 [thread overview]
Message-ID: <20040826215856.A8BD3C109F@atlas.denx.de> (raw)
In-Reply-To: Your message of "Thu, 26 Aug 2004 22:54:39 +0200." <20040826205439.GA2670@umax645sx>
Dear Ladislav,
in message <20040826205439.GA2670@umax645sx> you wrote:
>
> I'm getting clueless now. You don't like new command approach and you
> also don't like setenv ethaddr approach. I think there are people, who
> are solving similar problem. If there is no way to add this feature
> into official U-Boot, just say it directly and I'm fine with keeping
> patches localy.
I'm not against this feature, I just see no sense in adding a new
command. Either you can script this using existing "i2c" or "eeprom"
or "mm" commands, or you can use a separate standalone application as
done for the 82559 and eepro100 cards.
> 1) MAC adress lives in EEPROM connected to SMC ethernet chip. This
> address comes from purchased range.
OK, then there is no need to change it, right?
> 2) User is able to change it in enviroment, but is unable to save it
> together with other enviroment variables and he is also unable to
> store it into serial EEPROM. Think about MAC as a board id.
If I was to configure such a system, the user is NOT able to change
the MAC address.
If you allow to overwrite the "ethaddr" variable this of course gets
saved together with the other enviroment variables.
If you want to allow the user to modify the hardware ID (in the
SROM), then provide a separate tool for it.
And yes, I do think about the MAC as a board ID. This is why I
recommend to make it NOT changable by the user.
> It is posible that board dies (it is hit by flash, etc). In that case
> servician comes to replace it and stores the MAC used by dead board to
> new one, not breaking customers setup and to save MAC addresses from
> purchased range.
This is NEW board, so it has a new board ID - obviously. Sorry, but I
feel this is a constructed example, and not a real problem. You can
be lucky that U-Boot provides the flexibility to do such things, but
this is not a free ticket for misuing it. Just assume the bootloader
does not allow changing the MAC address. This is actually the case
with _most_ boot loaders.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd at denx.de
Never worry about theory as long as the machinery does what it's
supposed to do. - R. A. Heinlein
next prev parent reply other threads:[~2004-08-26 21:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-26 8:30 [U-Boot-Users] MAC address question Getz, Robin
2004-08-26 9:17 ` Ladislav Michl
2004-08-26 15:05 ` Wolfgang Denk
2004-08-26 16:02 ` Ladislav Michl
2004-08-26 9:47 ` R: " Paolo Broggini
2004-08-26 15:06 ` Wolfgang Denk
2004-08-26 15:03 ` Wolfgang Denk
2004-08-26 16:13 ` Ladislav Michl
2004-08-26 16:44 ` Wolfgang Denk
2004-08-26 17:10 ` Ladislav Michl
2004-08-26 19:22 ` Wolfgang Denk
2004-08-26 20:54 ` Ladislav Michl
2004-08-26 21:58 ` Wolfgang Denk [this message]
2004-08-26 22:40 ` Ladislav Michl
-- strict thread matches above, loose matches on Subject: below --
2004-08-26 17:25 Robin Getz
2004-08-26 19:17 ` Ladislav Michl
2004-08-26 19:38 ` Wolfgang Denk
2004-08-26 20:26 Robin Getz
2004-08-26 21:42 ` 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=20040826215856.A8BD3C109F@atlas.denx.de \
--to=wd@denx.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