Re: [U-Boot] [PATCH] fdt: rework fdt_fixup_ethernet() to use env instead of bd_t

Dear Kumar Gala, In message <[EMAIL PROTECTED]> you wrote: > > 74xx_7xx, mpc8xx, ppc4xx -- called regardless of CONFIG_HAS_ETHn > mpc512x -- called only based on HAS_ETH0 > mpc8260, mpc83xx, mpc85xx, mpc86xx -- called if HAS_ETH0 || HAS_ETH1 > || HAS_ETH2 || HAS_ETH3 > > With ETH3 being the ma

Re: [U-Boot] [PATCH] fdt: rework fdt_fixup_ethernet() to use env instead of bd_t

On Aug 18, 2008, at 2:16 PM, Kumar Gala wrote: > > On Aug 18, 2008, at 2:12 PM, Wolfgang Denk wrote: > >> Dear Kumar Gala, >> >> In message <[EMAIL PROTECTED]> >> you wrote: >>> Move to using the environment variables 'ethaddr', 'eth1addr', etc.. >>> instead of bd->bi_enetaddr, bi_enet1addr, etc.

Re: [U-Boot] [PATCH] fdt: rework fdt_fixup_ethernet() to use env instead of bd_t

On Aug 18, 2008, at 2:12 PM, Wolfgang Denk wrote: > Dear Kumar Gala, > > In message <[EMAIL PROTECTED]> > you wrote: >> Move to using the environment variables 'ethaddr', 'eth1addr', etc.. >> instead of bd->bi_enetaddr, bi_enet1addr, etc. >> >> This makes the code a bit more flexible to the num

Re: [U-Boot] [PATCH] fdt: rework fdt_fixup_ethernet() to use env instead of bd_t

Dear Kumar Gala, In message <[EMAIL PROTECTED]> you wrote: > Move to using the environment variables 'ethaddr', 'eth1addr', etc.. > instead of bd->bi_enetaddr, bi_enet1addr, etc. > > This makes the code a bit more flexible to the number of ethernet > interfaces. Right now we assume a max of 10 i

[U-Boot] [PATCH] fdt: rework fdt_fixup_ethernet() to use env instead of bd_t

Move to using the environment variables 'ethaddr', 'eth1addr', etc.. instead of bd->bi_enetaddr, bi_enet1addr, etc. This makes the code a bit more flexible to the number of ethernet interfaces. Right now we assume a max of 10 interfaces. Signed-off-by: Kumar Gala <[EMAIL PROTECTED]> --- common/