From: Heiner Kallweit <hkallweit1@gmail.com>
To: Florian Fainelli <f.fainelli@gmail.com>,
Realtek linux nic maintainers <nic_swsd@realtek.com>,
David Miller <davem@davemloft.net>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next] r8169: remove 1000/Half from supported modes
Date: Tue, 28 May 2019 20:02:08 +0200 [thread overview]
Message-ID: <4d22f35c-4f1c-48e8-b32d-dcbed59d3dd2@gmail.com> (raw)
In-Reply-To: <9b73d283-c284-1ccf-7a43-15f66084cba1@gmail.com>
On 28.05.2019 19:40, Florian Fainelli wrote:
> On 5/28/19 9:43 AM, Heiner Kallweit wrote:
>> MAC on the GBit versions supports 1000/Full only, however the PHY
>> partially claims to support 1000/Half. So let's explicitly remove
>> this mode.
>>
>> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
>
> Don't you want a Fixes: tag for that?
>
I'm not aware of any problem caused by that. And according to what
I've read 1000/Half has been specified but never really been used.
So it should be sufficient to treat this as an improvement.
>> ---
>> drivers/net/ethernet/realtek/r8169.c | 5 ++++-
>> 1 file changed, 4 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/net/ethernet/realtek/r8169.c b/drivers/net/ethernet/realtek/r8169.c
>> index 61e7eef5e..0239a3de2 100644
>> --- a/drivers/net/ethernet/realtek/r8169.c
>> +++ b/drivers/net/ethernet/realtek/r8169.c
>> @@ -6397,7 +6397,10 @@ static int r8169_phy_connect(struct rtl8169_private *tp)
>> if (ret)
>> return ret;
>>
>> - if (!tp->supports_gmii)
>> + if (tp->supports_gmii)
>> + phy_remove_link_mode(phydev,
>> + ETHTOOL_LINK_MODE_1000baseT_Half_BIT);
>> + else
>> phy_set_max_speed(phydev, SPEED_100);
>>
>> phy_support_asym_pause(phydev);
>>
>
>
next prev parent reply other threads:[~2019-05-28 18:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 16:43 [PATCH net-next] r8169: remove 1000/Half from supported modes Heiner Kallweit
2019-05-28 17:35 ` Andrew Lunn
2019-05-28 17:40 ` Florian Fainelli
2019-05-28 18:02 ` Heiner Kallweit [this message]
2019-05-30 4:43 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4d22f35c-4f1c-48e8-b32d-dcbed59d3dd2@gmail.com \
--to=hkallweit1@gmail.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).