From: Fabio Baltieri <fabio.baltieri@gmail.com>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
nic_swsd@realtek.com, Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Michael Zimmermann <sigmaepsilon92@gmail.com>
Subject: Re: [PATCH] r8169: add support for RTL8127ATF
Date: Tue, 18 Nov 2025 20:20:18 +0000 [thread overview]
Message-ID: <aRzVApYF_8loj8Uo@google.com> (raw)
In-Reply-To: <ff55848b-5543-4a8d-b8c2-88837db16c29@gmail.com>
On Tue, Nov 18, 2025 at 09:02:22PM +0100, Heiner Kallweit wrote:
> A contact in Realtek confirmed that only 1G and 10G speeds are supported.
> He wasn't sure whether copper SFP modules are supported, and will check
> internally.
>
> I'll try to strip down the patch as far as possible, likely supporting 10G
> only in the beginning (as 1G requires some more vendor magic to configure).
> I assume the typical user won't spend money on a 10G card to use it with a
> 1G fiber module.
> Reducing complexity of the patch should make the decision easier to accept it.
>
> I don't have hw with RTL8127ATF, so I would give the patch to Fabio for testing.
Hey thanks for following up on this, cc'ing Michael as well, as it turns
out he was also working on upstream support for this at the same time as
me, maybe he can help testing in more scenarios.
I did test 1G support between two RTL8127ATF cards and it works fine,
have not tried between that a 1G fiber only card (don't own any), happy
to drop it if you think it may not work but hopefully it can be tested
and kept, it was in the out of tree driver after all, I'd hope the
vendor did some interoperability test with that code.
Cheers,
Fabio
next prev parent reply other threads:[~2025-11-18 20:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 19:16 [PATCH] r8169: add support for RTL8127ATF Fabio Baltieri
2025-11-17 19:37 ` Andrew Lunn
2025-11-18 11:08 ` Fabio Baltieri
2025-11-18 19:31 ` Andrew Lunn
2025-11-18 20:02 ` Heiner Kallweit
2025-11-18 20:20 ` Fabio Baltieri [this message]
2025-11-18 21:31 ` Michael Zimmermann
2025-11-18 22:01 ` Fabio Baltieri
2025-11-19 7:00 ` Michael Zimmermann
2025-11-19 10:26 ` Fabio Baltieri
2025-11-20 23:17 ` Heiner Kallweit
2025-11-21 12:09 ` Fabio Baltieri
2025-11-21 13:09 ` Heiner Kallweit
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=aRzVApYF_8loj8Uo@google.com \
--to=fabio.baltieri@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
--cc=pabeni@redhat.com \
--cc=sigmaepsilon92@gmail.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).