On Friday 11 March 2011, Roger Quadros wrote: > > A udev rule would solve the problem at hand, but I'd consider that > > an ugly workaround as well. The naming in the kernel is really > > bogus -- any USB device that has a fixed address gets treated > > as eth0, while others become usb0, with the same driver, > > see the code fragment below. > > but isn't that sensible? a real ethernet hardware will have a MAC > address. no? I have just verified with my Pandaboard that the pins on the SMSC9514 usb ethernet that are meant to be connected to a serial EEPROM are indeed not connected anywhere. Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html