[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2a1590b2-fa9a-f2bf-0ef7-97659244fa9b@seco.com>
Date: Fri, 11 Nov 2022 15:58:22 -0500
From: Sean Anderson <sean.anderson@...o.com>
To: Tim Harvey <tharvey@...eworks.com>,
netdev <netdev@...r.kernel.org>,
Russell King <linux@...linux.org.uk>,
"David S. Miller" <davem@...emloft.net>
Subject: Re: status of rate adaptation
On 11/11/22 15:57, Sean Anderson wrote:
> Hi Tim,
>
> On 11/11/22 15:44, Tim Harvey wrote:
>> Greetings,
>>
>> I've noticed some recent commits that appear to add rate adaptation support:
>> 3c42563b3041 net: phy: aquantia: Add support for rate matching
>> 7de26bf144f6 net: phy: aquantia: Add some additional phy interfaces
>> b7e9294885b6 net: phylink: Adjust advertisement based on rate matching
>> ae0e4bb2a0e0 net: phylink: Adjust link settings based on rate matching
>> 0c3e10cb4423 net: phy: Add support for rate matching
>>
>> I have a board with an AQR113C PHY over XFI that functions properly at
>> 10Gbe links but still not at 1Gbe,2.5Gbe,5.0Gbe,100M with v6.1-rc4
>>
>> Should I expect this to work now at those lower rates
>
> Yes.
>
>> and if so what kind of debug information or testing can I provide?
>
> Please send
>
> - Your test procedure (how do you select 1G?)
> - Device tree node for the interface
> - Output of ethtool (on both ends if possible).
> - Kernel logs with debug enabled for drivers/phylink.c
Sorry, this should be drivers/net/phy/phylink.c
>
> That should be enough to get us started.
>
> --Sean
Powered by blists - more mailing lists