On 11/05/2014 02:55 AM, Robert Moskowitz wrote:
I am in an IEEE 802 MACaddr debate right now, where there is a PAR proposal that will segment the local scope address space. Quite a mess and I am very depressed.... I use Cubieboards that do not have a registered CID to provide a global MACaddr, and instead leaves it up to the OS to workout a local MACaddr. Is this the common case for ARMv7 (and v8) boards or the exception?
There is usually always a MAC address allocated to the devices' NICs, even if it is on a sticker. From there on it is up to the boot loader and/or the OS to assign it.
For example, I find that on my QNAP TS-421 the MAC address is stored in uboot but the driver doesn't automatically set it. You have to write a script that will set it, and either hard-code the MAC address in the script or have the script extract it from the firmware using whatever method you can.
Various Marvell Kirkwood devices (*Plug) do a similar thing in that the MAC address is set in the uboot variables, but as far as I can tell uboot sets this and the driver figures it out without manually extracting and setting the MAC using a userspace script.
So certainly among the devices I have it doesn't seem that uncommon.
What does the beagle boards do? wandboards? Oh, now Raspberry PI has ethernet and what does it do? Help, please. Meeting runs 30 more minutes, and we have to comment on the PAR tonight....
I guess it's too late, then. _______________________________________________ arm mailing list arm@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/arm
