On Friday 25 March 2011, Andy Green wrote:
> I see. It would work OK then. They probably wouldn't want to blow
> their $1750 just on Panda though, so maybe they set 4 bits or whatever
> and let 20 be computed.
Well, if the algorithm is defined well, it could be used for any device
based on OMAP. The marketing department could turn this into a win by
declaring "does not require external EEPROM for ethernet mac address" ;-)
> However, the only practical advantage is that it would show up as a TI
> MAC in an OUI database. The "locally administered" address as used at
> the moment is otherwise legal in every respect AFAIK.
It should work almost always, except in very special corner cases:
* If you have a netboot setup, you want the boot loader to use the
same mac address for requesting the kernel image that you use later,
otherwise the switch might consider it a MAC spoofing attach and disable
the port. The obvious workaround is to put your code into the boot loader
as well.
* Some environments might be configured to disallow locally administered
MAC addresses for "security" reasons. A bit bogus, but not unheard of.
* Some places try to keep a database of all used machines and their MAC
addresses to monitor who connects to the network. This requires the address
to be stable. It also prevents the use of virtualization, so it's becoming
less common.
Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
