On Monday 16 February 2009 17:38:54 Wolfgang Denk wrote:
> In message Mike Frysinger wrote:
> > +Here are the places where MAC addresses might be stored:
> > +
> > + - board-specific location (eeprom, dedicated flash, ...)
> > + Note: only used when mandatory due to hardware design etc...
> > +
> > + - environment ("ethaddr", "eth1addr", ...) (see CONFIG_ETHADDR)
> > + Note: this is the preferred way to permanently store MAC addresses
> > +
> > + - ethernet data (struct eth_device -> enetaddr)
> > + Note: these are temporary copies of the MAC address which exist only
> > + after the respective init steps have run and only to make usage
> > + in other places easier (to avoid constant env lookup/parsing)
>
> - struct bd_info and/or device tree
> Note: these are temporary copies of the MAC address only foir
> the purpose to pass this information to an OS kernel we are
> about to boot
>
> > +The common environment code will take care of passing environment
> > changes to +the global data. This happens automatically whenever
> > setenv() updates the +relevant ethaddr variables.
>
> Didn't we just remove the MAC address information from the global
> data?
>
> > +Any other common code that wishes to access the MAC address should then
> > query +the global data directly. No one should be looking in the
> > environment for any +addresses.
>
> Is this still valid?erm, i updated the file in places i remembered, but didnt give it a complete top-to-bottom look over after the last discussion. ive fixed up the things you pointed out, thanks. -mike
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
