Hi Hannes, On Tue, Sep 6, 2016 at 12:33 PM, Hannes Schmelzer <[email protected]> wrote: > "U-Boot" <[email protected]> schrieb am 06.09.2016 03:54:52: > >> Von: Bin Meng <[email protected]> >> An: Joe Hershberger <[email protected]>, >> Kopie: u-boot <[email protected]>, Hannes Schmelzer > <[email protected]>, Joe >> Hershberger <[email protected]> >> Datum: 06.09.2016 03:57 >> Betreff: Re: [U-Boot] [PATCH] net: write enetaddr down to hardware on > env_callback >> Gesendet von: "U-Boot" <[email protected]> >> >> Hi, > Hi Bin, > >> >> On Fri, Sep 2, 2016 at 9:00 PM, Joe Hershberger >> <[email protected]> wrote: >> > On Fri, Sep 2, 2016 at 7:48 AM, Hannes Schmelzer <[email protected]> > wrote: >> >> If mac-address is changed using "setenv ethaddr ...." command the new >> >> mac-adress also must be written into the responsible ethernet driver. >> >> >> >> Signed-off-by: Hannes Schmelzer <[email protected]> >> > >> > Acked-by: Joe Hershberger <[email protected]> >> >> Why is this needed? The MAC address is supposed to be programmed in >> the driver's probe routine. > > For example on my custom ZYNQ board. > The Ethernetcontroller within the ZYNQ has no ROM to store his own > MAC-Address, further no MAC is stored within environment. > So Ethernet gets probed with a "random MAC-Address" if configured. > > Later somebody (like me) oder something (my bootscript) runs "setenv > ethaddr ...." on the console. > Result is (was before this patch), that all networking infrastructre is > running this new mac, but hardware is running the old (random) one and > networking is simple not functional. >
This indicates that your ethernet driver does not program the latest MAC address everyone when it gets probed. The driver should be fixed. > ok? > Regards, Bin _______________________________________________ U-Boot mailing list [email protected] http://lists.denx.de/mailman/listinfo/u-boot
