From: NZG <ngustavson@emacinc.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] bootloader MAC
Date: Thu, 8 Jun 2006 17:31:49 -0500 [thread overview]
Message-ID: <200606081731.49365.ngustavson@emacinc.com> (raw)
In-Reply-To: <20060608214056.BE69B35265D@atlas.denx.de>
On Thursday 08 June 2006 4:40 pm, Wolfgang Denk wrote:
> Nobody is talking about about dynamical assignemnt.
>
> It's just that the *Linux* *driver* is responsible to initialize ?it,
> no matter which boot loader you use and what the boot loader is doing
> or not doing.
In some cases that would amount to dynamic reassignment, such as in the
Coldfire fec, which does not provide the typical load from eeprom
functionality for it's MAC. It must be assigned by software somewhere, I am
of the opinion that the bootloader should do it.
Why?
Because when we ship a board, we have to program the bootloader into it so
customers can load an OS, the MAC goes into a protected region of flash,
which it's not likely to be accidentally removed. We buy chunks of MAC
addresses and assign them to boards we ship in quantity.
I look at the bootloader like the BIOS of a PC without the system calls. It
initializes the hardware to a minimal point (you've at least got to turn on
the DRAM, an IMHO make sure the MAC is valid) and loads the OS.
The OS will probably change with time, but the BIOS/bootloader is less likely
too.
> This has been discussed many
> times before.
I know, I lurk, but I have yet to see any real discussion other than quick
fixes.
I've pulled out the most relevant ones I can find below, if you know of a
better one please send a link.
I see:
http://lists.arm.linux.org.uk/pipermail/linux-arm/2005-July/010246.html
Which discusses using gen_eth_addrl for generating MAC address, but of course
this is only useful for testing
http://www.denx.de/wiki/bin/view/DULG/EthernetDoesNotWork
I see:
http://lists.arm.linux.org.uk/pipermail/linux-arm-kernel/2004-July/023572.html
Which was never resolved on list
I see:
http://lists.arm.linux.org.uk/pipermail/linux-arm/2004-December/008936.html
In which using ifconfig to set the MAC is recommended in conjunction with
purchasing a block of MAC addresses for at least $550.
This is pretty non-standard. We manufacture boards here and all of them are
shipped with a pre-programmed valid address, Advantech and Aeon and every
other major board manufacturer I know of, do the same.
I also have never seen a Linux distribution that set's it's MAC on bootup
through ifconfig, usually it's set on bootup by reading an EEPROM.
And finally:
http://lists.arm.linux.org.uk/pipermail/linux-arm/2002-October/004300.html
In which the solution was to contact the board manufacturer (rightfully so as
they should be providing the MAC)
NZG
next prev parent reply other threads:[~2006-06-08 22:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-08 16:34 [U-Boot-Users] Help U-Boot NFS filesystem muqiyong
[not found] ` <008501c68b19$639091e0$8ed3fea9@first>
2006-06-08 16:57 ` Wolfgang Denk
2006-06-08 17:57 ` Marco Cavallini
2006-06-08 19:49 ` Wolfgang Denk
2006-06-08 20:22 ` Marco Cavallini
2006-06-08 20:59 ` Wolfgang Denk
2006-06-08 20:40 ` [U-Boot-Users] Help U-Boot NFS filesystem->bootloader MAC NZG
2006-06-08 21:40 ` Wolfgang Denk
2006-06-08 22:31 ` NZG [this message]
2006-06-08 22:58 ` [U-Boot-Users] bootloader MAC Rune Torgersen
2006-06-08 23:16 ` NZG
2006-06-08 23:24 ` Rune Torgersen
2006-06-09 0:49 ` Wolfgang Denk
2006-06-09 0:44 ` Wolfgang Denk
2006-06-09 4:06 ` NZG
2006-06-09 7:44 ` Wolfgang Denk
2006-06-09 14:23 ` NZG
2006-06-09 16:56 ` Wolfgang Denk
2006-06-09 17:14 ` NZG
2006-06-09 17:58 ` NZG
2006-06-09 8:48 ` [U-Boot-Users] Help U-Boot NFS filesystem Alex Zeffertt
2006-06-09 12:22 ` muqiyong
[not found] ` <002401c68bbf$6f7dfd20$8ed3fea9@first>
2006-06-09 13:08 ` Wolfgang Denk
2006-06-10 3:18 ` [U-Boot-Users] Help U-Boot NFS filesystem. (Flash error! maybe I need wait my next board) muqiyong
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=200606081731.49365.ngustavson@emacinc.com \
--to=ngustavson@emacinc.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