From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] MAC address question...
Date: Thu, 26 Aug 2004 21:38:21 +0200 [thread overview]
Message-ID: <20040826193826.573AEC109F@atlas.denx.de> (raw)
In-Reply-To: Your message of "Thu, 26 Aug 2004 10:25:50 PDT." <6.1.1.1.0.20040826093807.01de9258@wheresmymailserver.com>
In message <6.1.1.1.0.20040826093807.01de9258@wheresmymailserver.com> you wrote:
>
> Since this will eventually sold at Digikey & Farnell, it will be used by a
> variety of people at different skill levels (from pros to beginners), I
> want to ensure that if someone erases the entire Flash, it will still have
> a valid MAC address. Therefore, it will ship to people with valid MAC
> addresses (purchased from the IEEE) in the EEPROM connected to the
> SMC91111, and no environment variable (ethaddr) set.
OK. This is fine.
> If someone wants to change the MAC address, they add the environment
> variable (ethaddr), and this will be used. (but it will print warning
> messages that the MACs do not match).
OK again. All this is exactly what the README says.
> I have had a few beta users who had to change the MAC address, (to get DHCP
> working on their networks), but then started calling for help when they get
Why do you need to change a MAC address to get DHCP working??? I
never heard such a thing before - of course I assume that you are
distributing your boxes with valid MAC addresses only!?
> The "solution" was add some functionality somewhere, to change the MAC
> address in the SROM. I thought U-boot might be the best bet - because that
> is where MAC addresses should be managed - in the boot loader. I know that
> this should be programmed during manufacturing (and it is), but there is no
> way to re-program the SROM MAC. (unless I am missing something?)
Such functionality has been added before, but not as (statically
linked) part of U-Boot. Please see examples/82559_eeprom.c and
examples/eepro100_eeprom.c for examples.
> Today on my board, I have 4 Meg of Flash - If I define things as 4Meg + 6
> bytes, in the board/specific/flash.c in write_buff() - I can trap these +6
> bytes, and actually program the MAC in the SROM. This is bad form because I
> know I should not be accessing a device outside the /driver/smc9111.c file.
I will not allow such dirty hacks in the public U-Boot source tree.
> The other option I had was make a similar patch to what Ladis did (thanks
> by the way) - but I expected Wolfgang to have a similar reaction to what he
> did.
:-)
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
Karl's version of Parkinson's Law: Work expands to exceed the time
alloted it.
next prev parent reply other threads:[~2004-08-26 19:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-26 17:25 [U-Boot-Users] MAC address question Robin Getz
2004-08-26 19:17 ` Ladislav Michl
2004-08-26 19:38 ` Wolfgang Denk [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-26 20:26 Robin Getz
2004-08-26 21:42 ` Wolfgang Denk
2004-08-26 8:30 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 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
2004-08-26 22:40 ` Ladislav Michl
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=20040826193826.573AEC109F@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