Kumar Gala wrote:
>
> On Apr 21, 2009, at 6:24 PM, Anatolij Gustschin wrote:
>
>> Kumar Gala wrote:
>>>
>>> On Apr 21, 2009, at 4:54 PM, Kumar Gala wrote:
>>>
On Apr 21, 2009, at 12:19 PM, Anatolij Gustschin wrote:
> If the firmware missed to initialize the PHY correctly,
>
On Apr 21, 2009, at 6:24 PM, Anatolij Gustschin wrote:
Kumar Gala wrote:
On Apr 21, 2009, at 4:54 PM, Kumar Gala wrote:
On Apr 21, 2009, at 12:19 PM, Anatolij Gustschin wrote:
If the firmware missed to initialize the PHY correctly,
Linux may hang up on socrates while eth0/eth1 interface
Kumar Gala wrote:
>
> On Apr 21, 2009, at 4:54 PM, Kumar Gala wrote:
>
>>
>> On Apr 21, 2009, at 12:19 PM, Anatolij Gustschin wrote:
>>
>>> If the firmware missed to initialize the PHY correctly,
>>> Linux may hang up on socrates while eth0/eth1 interface
>>> startup (caused by continuous unackno
On Apr 21, 2009, at 4:54 PM, Kumar Gala wrote:
On Apr 21, 2009, at 12:19 PM, Anatolij Gustschin wrote:
If the firmware missed to initialize the PHY correctly,
Linux may hang up on socrates while eth0/eth1 interface
startup (caused by continuous unacknowledged PHY interrupt).
This patch adds
On Apr 21, 2009, at 12:19 PM, Anatolij Gustschin wrote:
If the firmware missed to initialize the PHY correctly,
Linux may hang up on socrates while eth0/eth1 interface
startup (caused by continuous unacknowledged PHY interrupt).
This patch adds PHY fixup to socrates platform code to
ensure the
If the firmware missed to initialize the PHY correctly,
Linux may hang up on socrates while eth0/eth1 interface
startup (caused by continuous unacknowledged PHY interrupt).
This patch adds PHY fixup to socrates platform code to
ensure the PHY is pre-initialized correctly. It is needed
to be compat
