[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f2a38c01-8726-a7fe-f645-2c83fe30b932@ti.com>
Date: Tue, 15 Sep 2020 18:29:22 -0500
From: Dan Murphy <dmurphy@...com>
To: Andrew Lunn <andrew@...n.ch>
CC: <davem@...emloft.net>, <f.fainelli@...il.com>,
<hkallweit1@...il.com>, <mkubecek@...e.cz>,
<netdev@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH net-next 1/3] ethtool: Add 100base-FX link mode entries
Andrew
On 9/15/20 3:21 PM, Andrew Lunn wrote:
> On Tue, Sep 15, 2020 at 01:17:06PM -0500, Dan Murphy wrote:
>> Add entries for the 100base-FX full and half duplex supported modes.
>>
>> $ ethtool eth0
>> Supported ports: [ TP MII FIBRE ]
>> Supported link modes: 10baseT/Half 10baseT/Full
>> 100baseT/Half 100baseT/Full
>> 100baseFX/Half 100baseFX/Full
>> Supported pause frame use: Symmetric Receive-only
>> Supports auto-negotiation: No
>> Supported FEC modes: Not reported
>> Advertised link modes: 10baseT/Half 10baseT/Full
>> 100baseT/Half 100baseT/Full
>> 100baseFX/Half 100baseFX/Full
> I thought this PHY could not switch between TP and Fibre. It has a
> strap which decides? So i would expect the supported modes to be
> either BaseT or BaseFX. Not both. Same for Advertised?
>
> Andrew
I found that the phy-device was setting all these bits in phy_init in
features_init.
My first pass was to clear all these bits as well because the PHY was
still advertising these modes.
But you are right this PHY cannot switch without strapping.
I can clear these bits.
Dan
Powered by blists - more mailing lists