Re: [U-Boot] [PATCH 2/3 v3] Add bb_miiphy_init call before any ethernet bring-up code.

On Mon, Oct 5, 2009 at 10:18 PM, Ben Warren wrote: ... >> >> The board specifc code will be contained into the hook .init filed >> into the bb_mii_buses vector. >> >> Do you have a better solution? >> >> > > In each case, you put the bb_miiphy_init() right before eth_initialize(). >  One of the fi

Re: [U-Boot] [PATCH 2/3 v3] Add bb_miiphy_init call before any ethernet bring-up code.

Luigi Mantellini wrote: > The lib_[arch]/board.c code calls the bb_miiphy_init that will do just 2 > things: > > 1) Relocate the bb_mii_buses[i].* hooks (.init, .mdio_active, .delay, ...) > 2) Call the board bb_mii_buses[i].init (board specific code). > > The board specifc code will be contained i

Re: [U-Boot] [PATCH 2/3 v3] Add bb_miiphy_init call before any ethernet bring-up code.

The lib_[arch]/board.c code calls the bb_miiphy_init that will do just 2 things: 1) Relocate the bb_mii_buses[i].* hooks (.init, .mdio_active, .delay, ...) 2) Call the board bb_mii_buses[i].init (board specific code). The board specifc code will be contained into the hook .init filed into the bb_

Re: [U-Boot] [PATCH 2/3 v3] Add bb_miiphy_init call before any ethernet bring-up code.

Hi Luigi, Luigi 'Comio' Mantellini wrote: > From: Luigi 'Comio' Mantellini > > Signed-off-by: Luigi 'Comio' Mantellini > --- > lib_arm/board.c |3 +++ > lib_avr32/board.c|3 +++ > lib_blackfin/board.c |3 +++ > lib_i386/board.c |3 +++ > lib_m68k/board.c |3

[U-Boot] [PATCH 2/3 v3] Add bb_miiphy_init call before any ethernet bring-up code.

From: Luigi 'Comio' Mantellini Signed-off-by: Luigi 'Comio' Mantellini --- lib_arm/board.c |3 +++ lib_avr32/board.c|3 +++ lib_blackfin/board.c |3 +++ lib_i386/board.c |3 +++ lib_m68k/board.c |3 +++ lib_mips/board.c |3 +++ lib_ppc/board.c |