On Wed, Sep 8, 2010 at 10:07 AM, Mike Frysinger <vap...@gentoo.org> wrote: > > and if you read the doumentation, you'll see that you're mistaken. whatever > device you're dealing with (today) is missing a call to its own write_hwaaddr > function inside of its own init function. > > if you want to fix your immediate issue, then fix that driver as implied by > the policy. if you want to improve the policy, then you need to update all > the drivers and the common code. > -mike > Apologies, I get it now. I will send a new patch that fixes the driver's init routine.
One more question however, why does eth_initialize call dev->write_hwaddr? Thanks John _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
