The case I am personally dealing with is one where there is no persistent storage for ethaddr. Booting from and SD card and a script is run that sets the ethaddr.
Currently eth_init updates dev->enetaddr for each device but does not call dev-write_hwaddr. This seems like a bug not a policy change. On Tue, Sep 7, 2010 at 10:23 PM, Mike Frysinger <vap...@gentoo.org> wrote: > On Tuesday, September 07, 2010 18:50:26 John Rigby wrote: >> When eth_init updates dev->enetaddr it does not >> call dev->write_hwaddr. Fix that so when ethaddr >> is set after eth_initialize the change will propagate >> to the hw. > > current policy is that the driver init() is supposed to be taking care of > this. if you're going to change that, you'll have to update the documentation > and actual drivers. > -mike > _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
