Am 19.11.2014 um 22:39 schrieb Felix Fietkau:
> On 2014-11-19 22:17, Heiner Kallweit wrote:
>> Am 19.11.2014 um 21:19 schrieb Felix Fietkau:
>>> On 2014-10-31 21:38, Heiner Kallweit wrote:
Kernel 3.14 introduced a switch reset in phy_init_hw in drivers/net/phy
causing BMCR_ANENABLE to get
On 2014-11-19 22:17, Heiner Kallweit wrote:
> Am 19.11.2014 um 21:19 schrieb Felix Fietkau:
>> On 2014-10-31 21:38, Heiner Kallweit wrote:
>>> Kernel 3.14 introduced a switch reset in phy_init_hw in drivers/net/phy
>>> causing BMCR_ANENABLE to get cleared.
>>>
>>> Due to the fact that ar8xxx_phy_co
Am 19.11.2014 um 21:19 schrieb Felix Fietkau:
> On 2014-10-31 21:38, Heiner Kallweit wrote:
>> Kernel 3.14 introduced a switch reset in phy_init_hw in drivers/net/phy
>> causing BMCR_ANENABLE to get cleared.
>>
>> Due to the fact that ar8xxx_phy_config_aneg does nothing for
>> PHY 0 autonegatiation
On 2014-10-31 21:38, Heiner Kallweit wrote:
> Kernel 3.14 introduced a switch reset in phy_init_hw in drivers/net/phy
> causing BMCR_ANENABLE to get cleared.
>
> Due to the fact that ar8xxx_phy_config_aneg does nothing for
> PHY 0 autonegatiation support remains disabled.
> This can cause ports to
Kernel 3.14 introduced a switch reset in phy_init_hw in drivers/net/phy
causing BMCR_ANENABLE to get cleared.
Due to the fact that ar8xxx_phy_config_aneg does nothing for
PHY 0 autonegatiation support remains disabled.
This can cause ports to operate at 10MBit/half-duplex only.
Fix this by callin
