Problems with DHCP on the Pi
Pages: 1 2
Jeffrey Lee (213) 6048 posts |
OMAPs have a nice 128bit unique ID which can be hashed down to a MAC address if necessary. In fact EtherUSB already has code to generate a MAC from the (64bit) unique ID returned by OS_ReadSysInfo 2 (See net_default_mac in net.c). I’m not sure why that code isn’t being used for the SMSC driver. I haven’t checked what Linux does for the MAC address on OMAP; perhaps it gets passed through from u-boot as one of the command line args, which is something we could also support if necessary.
EtherUSB configures the MAC the same way for all SMSC devices. It either uses the EtherUSB$MAC_Configured system variable, or a hard-coded default MAC. But with EtherUSB in ROM, there’s no easy way of stopping the hard-coded MAC from being used, which isn’t ideal. |
Raik (463) 2061 posts |
On Beagle it works if you setting the MAC and reinit EtherUSB in Predesk before SetUpNet ist working. |
Steve Pampling (1551) 8170 posts |
I haven’t checked what Linux does for the MAC address on OMAP; perhaps it gets passed through from u-boot as one of the command line args, which is something we could also support if necessary. Following an earlier discussion I rebooted a beagle-xm several times on an Angstrom build and noted the MAC each time. Each boot produced a different MAC so it is either truly random or maybe date/time seeded. |
Pages: 1 2