From: Heiner Kallweit <hkallweit1@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>, Fabio Baltieri <fabio.baltieri@gmail.com>
Cc: 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
Subject: Re: [PATCH] r8169: add support for RTL8127ATF
Date: Tue, 18 Nov 2025 21:02:22 +0100 [thread overview]
Message-ID: <ff55848b-5543-4a8d-b8c2-88837db16c29@gmail.com> (raw)
In-Reply-To: <89298d49-d85f-4dfd-954c-f8ca9b47f386@lunn.ch>
On 11/18/2025 8:31 PM, Andrew Lunn wrote:
>> I see, unfortunately all I have for this NIC is the out of tree Realtek
>> driver and it does not seem to implement the API for reading the module
>> EEPROM data, and there's no datasheet available, so I'm afraid that
>> either the Realtek folks pick this up or it's not going to happen.
>
> Heiner is of the opinion it is not going to happen.
>
Realtek seems to do all SFP handling in firmware, w/o providing info about
to which extent this firmware can be controlled via chip registers.
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.
> Andrew
Heiner
next prev parent reply other threads:[~2025-11-18 20:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 19:16 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 [this message]
2025-11-18 20:20 ` Fabio Baltieri
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=ff55848b-5543-4a8d-b8c2-88837db16c29@gmail.com \
--to=hkallweit1@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fabio.baltieri@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 \
/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
all inboxes | Powered by JetHome®