Le 18/08/2010 10:47, Ilya Yanok a écrit :
> Hello Albert,
>
> Albert ARIBAUD free.fr> writes:
>
>> At the moment your problem is not being able to reset the PHY at times
>> other than boot, i.e. the 'PHY API' would be limited to reset_phy()
>> which is pretty much board-specific anyway.
>
> The p
Hello Albert,
Albert ARIBAUD free.fr> writes:
> At the moment your problem is not being able to reset the PHY at times
> other than boot, i.e. the 'PHY API' would be limited to reset_phy()
> which is pretty much board-specific anyway.
The problem is the PHY being reseted by the driver and goi
Dear Albert ARIBAUD,
In message <4c6b858f.9060...@free.fr> you wrote:
>
> At the moment your problem is not being able to reset the PHY at times
> other than boot, i.e. the 'PHY API' would be limited to reset_phy()
> which is pretty much board-specific anyway. What prevents simply adding
> calls t
Le 18/08/2010 01:16, Ilya Yanok a écrit :
> Hello Ben, Everybody,
>
> some boards used to have their PHY quirks in board-specific reset_phy()
> function. This used to work because of reset_phy() being called later
> than Ethernet drivers initialization during startup.
> But nowadays some drivers (i
Hello Ben, Everybody,
some boards used to have their PHY quirks in board-specific reset_phy()
function. This used to work because of reset_phy() being called later
than Ethernet drivers initialization during startup.
But nowadays some drivers (in particular I faced this problem using
mpc5xxx_fe
5 matches
Mail list logo
