From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Josua Mayer <josua@solid-run.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
Mikhail Anikin <mikhail.anikin@solid-run.com>,
Rabeeh Khoury <rabeeh@solid-run.com>,
Yazan Shhady <yazan.shhady@solid-run.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] net: sfp: support 25G long-range modules (extended compliance code 0x3)
Date: Mon, 19 Jan 2026 10:48:41 +0000 [thread overview]
Message-ID: <aW4MCTm_u6q8uaet@shell.armlinux.org.uk> (raw)
In-Reply-To: <a8ea329c-42b9-4adc-80ad-2f602a5fbf0c@solid-run.com>
On Mon, Jan 19, 2026 at 07:30:20AM +0000, Josua Mayer wrote:
> On 18/01/2026 18:01, Andrew Lunn wrote:
> > On Sun, Jan 18, 2026 at 04:07:38PM +0200, Josua Mayer wrote:
> >> The extended compliance code value SFF8024_ECC_100GBASE_ER4_25GBASE_ER
> >> (0x3) means either 4-lane 100G or single lane 25G.
> > Is there a way to tell them apart?
> The physical connectors are different, so we can know from the
> device-tree compatible string.
>
> For now sfp driver does not support qsfp.
And likely will never do.
I did look at QSFP support due to the LX2160A SR board, and I did
scratch some code together, but I didn't get far with it:
(a) LX2160A is just not flexible enough to consider the possibilities
properly to implement support (no run-time reconfiguration of the
interface mode.)
(b) QSFPs can be used as a single interface, or as multiple interfaces.
There is no way that the SFP and phylink layers can cope with that
as they are currently structured.
(c) QSFP EEPROMs have a completely different structure to SFP EEPROMs.
(d) I couldn't see any way that the QSFP EEPROM distinguished between
e.g. a cable that had QSFP at one end and 4x SFP at the other vs
a cable that had QSFP at each end, thus making it impossible to
know whether 100G as 4 25G lanes would be possible.
(e) I'm aware that there's devlink which I believe can deal with some
of this "single network interface of 4 lanes" vs "four network
interfaces of 1 lane" configuration, but I've never used it, and
when I looked at it, it wasn't clear how. I have no hardware that
makes use of devlink to play with to find out.
Basically, QSFP support is something I have little knowledge of, there
is precious little on the 'net about its use, I have no hardware
experience with, and I don't see how it fits into Linux networking.
So I decided it would be a fools errand to attempt to implement
anything.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2026-01-19 10:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-18 14:07 [PATCH 0/2] net: sfp: support 25G long-range modules (extended compliance code 0x3) Josua Mayer
2026-01-18 14:07 ` [PATCH 1/2] net: ethtool: Add link mode for 25Gbps long-range fiber Josua Mayer
2026-01-18 14:07 ` [PATCH 2/2] net: sfp: support 25G long-range modules (extended compliance code 0x3) Josua Mayer
2026-01-18 16:01 ` Andrew Lunn
2026-01-19 7:30 ` Josua Mayer
2026-01-19 10:48 ` Russell King (Oracle) [this message]
2026-01-19 19:30 ` Jakub Kicinski
2026-01-21 9:44 ` Josua Mayer
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=aW4MCTm_u6q8uaet@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--cc=josua@solid-run.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikhail.anikin@solid-run.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rabeeh@solid-run.com \
--cc=yazan.shhady@solid-run.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.