Yes, ridiculous in the complexity of the workarounds for not having a
generic way to set the mac address from the command line. :-/
Which means that the non-volatile storage must be available through a
Linux driver before the MAC address is set. AFAIK there is no guarantee
that the MTD layer will be ready to use by that time. And that is
assuming that there actually is a MTD driver available, usually when I
work on a Linux port for a reference board, the first thing I do is to
get a NFS root up and running, then I can put a have a complete Debian
system with all nice debugging tools available. When I have that up and
running I start porting the other drivers, such as the MTD driver.
Also, I don't really want to spend time on reverse engineering some
random non-volatile storage format, that's quite fragile.
Which is actually what I'm doing, except that it's easier to hack that
into the ethernet driver each time it is needed.
Yes, that why I'd want that in a generic piece of code instead of having
to hack it into each device driver. Would a generic command line
option, something like "ethaddrs=eth0=00:de:ad:be:ef:01" which assigns
addresses to network cards be acceptable?
Next time I have to port something to an embedded platform with this
kind of problem, I might try to do something more generic instead of the
simple hack I usually do now.
/Christer
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html