We think that is because linux is thinking the MAC address is > ff:ff:ff:ff:ff:ff instead of what > it really is. u-boot doesn't seem to have a problem getting the MAC > address out of the ebony board, but > this linux kernel seems to. >
A MAC address of ff:ff:ff:ff:ff:ff is the broadcast address, so that's a problem. I'm not familiar with 440, but the thing is, you've got to find your ethernet specific code in the kernel and see where it's getting the MAC from. u-boot passes a bd_t pointer to the kernel (a struct with a bunch of board data), but there's probably some kind of mis-match between u-boot and the platform config of the kernel. Mark Chambers ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
