Comment 1 for bug 622429

This is actually the expected behavior for Beagle xM boards.

If you check the system reference manual (http://beagle.s3.amazonaws.com/design/xM-A/BB_xM_SRM_A2_01.pdf - Page 80), you'll see that at Beagle XM uses SMSC LAN9514 as the USB hub and Ethernet adapter.

You can also find more about the SMSC chip at http://www.smsc.com/media/Downloads_Public/Data_Sheets/9514.pdf.

So it's not just a normal ethernet device, it's together with the USB hub, and it uses it structure.

Now regarding the naming, you can check why by looking at the driver smsc95xx (drivers/net/usb/smsc95xx.c). It basically uses the usbnet kernel infrastructure, making 'usbnet' module as a dependency, and then as a consequence the ethernet adapter gets called as 'usb0' instead of 'eth0'.

If you still want to change it, maybe creating a udev rule or something like that, but I'd stuck with 'usb0' as it shows the user that his ethernet device is connected with the USB hub.