From: "Russell King (Oracle)" <linux@armlinux•org.uk>
To: Maxime Chevallier <maxime.chevallier@bootlin•com>
Cc: davem@davemloft•net, netdev@vger•kernel.org,
linux-kernel@vger•kernel.org, linux-arm-msm@vger•kernel.org,
thomas.petazzoni@bootlin•com, "Andrew Lunn" <andrew@lunn•ch>,
"Jakub Kicinski" <kuba@kernel•org>,
"Eric Dumazet" <edumazet@google•com>,
"Paolo Abeni" <pabeni@redhat•com>,
linux-arm-kernel@lists•infradead.org,
"Christophe Leroy" <christophe.leroy@csgroup•eu>,
"Herve Codina" <herve.codina@bootlin•com>,
"Florian Fainelli" <f.fainelli@gmail•com>,
"Heiner Kallweit" <hkallweit1@gmail•com>,
"Vladimir Oltean" <vladimir.oltean@nxp•com>,
"Köry Maincent" <kory.maincent@bootlin•com>,
"Marek Behún" <kabel@kernel•org>,
"Oleksij Rempel" <o.rempel@pengutronix•de>,
"Nicolò Veronese" <nicveronese@gmail•com>,
"Simon Horman" <horms@kernel•org>,
mwojtas@chromium•org, "Antoine Tenart" <atenart@kernel•org>,
devicetree@vger•kernel.org, "Conor Dooley" <conor+dt@kernel•org>,
"Krzysztof Kozlowski" <krzk+dt@kernel•org>,
"Rob Herring" <robh@kernel•org>,
"Romain Gantois" <romain.gantois@bootlin•com>,
"Daniel Golle" <daniel@makrotopia•org>,
"Dimitri Fedrau" <dimitri.fedrau@liebherr•com>,
"Tariq Toukan" <tariqt@nvidia•com>
Subject: Re: [PATCH net-next v20 02/14] net: ethtool: Introduce ETHTOOL_LINK_MEDIUM_* values
Date: Thu, 27 Nov 2025 18:02:28 +0000 [thread overview]
Message-ID: <aSiSNA1PaM5Md8ju@shell.armlinux.org.uk> (raw)
In-Reply-To: <20251127171800.171330-3-maxime.chevallier@bootlin.com>
On Thu, Nov 27, 2025 at 06:17:45PM +0100, Maxime Chevallier wrote:
> In an effort to have a better representation of Ethernet ports,
> introduce enumeration values representing the various ethernet Mediums.
>
> This is part of the 802.3 naming convention, for example :
>
> 1000 Base T 4
> | | | |
> | | | \_ pairs (4)
> | | \___ Medium (T == Twisted Copper Pairs)
> | \_______ Baseband transmission
> \____________ Speed
>
> Other example :
>
> 10000 Base K X 4
> | | \_ lanes (4)
> | \___ encoding (BaseX is 8b/10b while BaseR is 66b/64b)
> \_____ Medium (K is backplane ethernet)
>
> In the case of representing a physical port, only the medium and number
> of pairs should be relevant. One exception would be 1000BaseX, which is
> currently also used as a medium in what appears to be any of
> 1000BaseSX, 1000BaseCX and 1000BaseLX. This was reflected in the mediums
> associated with the 1000BaseX linkmode.
There's more than just those three for 1000BASE-X:
SX
LX
CX
EX
BX10 - single fibre strand, single mode, 1310nm and 1490nm over
10km.
to name a few more. SFP modules don't have a way to indicate EX, but do
have a way to indicate 1000BASE-BX10 (BaseBX10 bit set with the rate
indicating 1000M.)
Also note that 100BASE-T encompasses 100BASE-TX (what we generally see
as fast ethernet), 100BASE-T4, etc. Should we be getting these
descriptions correct as we're introducing this level of detail?
--
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:[~2025-11-27 18:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-27 17:17 [PATCH net-next v20 00/14] net: phy: Introduce PHY ports representation Maxime Chevallier
2025-11-27 17:17 ` [PATCH net-next v20 01/14] dt-bindings: net: Introduce the ethernet-connector description Maxime Chevallier
2025-11-27 18:16 ` Rob Herring (Arm)
2025-11-28 8:34 ` Maxime Chevallier
2025-11-27 17:17 ` [PATCH net-next v20 02/14] net: ethtool: Introduce ETHTOOL_LINK_MEDIUM_* values Maxime Chevallier
2025-11-27 18:02 ` Russell King (Oracle) [this message]
2025-11-27 17:17 ` [PATCH net-next v20 03/14] net: phy: Introduce PHY ports representation Maxime Chevallier
2025-11-27 18:04 ` Russell King (Oracle)
2025-11-28 8:45 ` Maxime Chevallier
2025-11-27 17:17 ` [PATCH net-next v20 04/14] net: phy: dp83822: Add support for phy_port representation Maxime Chevallier
2025-11-27 17:17 ` [PATCH net-next v20 05/14] dt-bindings: net: dp83822: Deprecate ti,fiber-mode Maxime Chevallier
2025-11-27 18:16 ` Rob Herring (Arm)
2025-11-28 8:35 ` Maxime Chevallier
2025-11-27 17:17 ` [PATCH net-next v20 06/14] net: phy: Create a phy_port for PHY-driven SFPs Maxime Chevallier
2025-11-27 17:17 ` [PATCH net-next v20 07/14] net: phy: Introduce generic SFP handling for PHY drivers Maxime Chevallier
2025-11-27 17:17 ` [PATCH net-next v20 08/14] net: phy: marvell-88x2222: Support SFP through phy_port interface Maxime Chevallier
2025-11-27 17:17 ` [PATCH net-next v20 09/14] net: phy: marvell: " Maxime Chevallier
2025-11-27 17:17 ` [PATCH net-next v20 10/14] net: phy: marvell10g: Support SFP through phy_port Maxime Chevallier
2025-11-27 17:17 ` [PATCH net-next v20 11/14] net: phy: at803x: Support SFP through phy_port interface Maxime Chevallier
2025-11-27 17:17 ` [PATCH net-next v20 12/14] net: phy: qca807x: " Maxime Chevallier
2025-11-27 17:17 ` [PATCH net-next v20 13/14] net: phy: Only rely on phy_port for PHY-driven SFP Maxime Chevallier
2025-11-27 17:17 ` [PATCH net-next v20 14/14] Documentation: networking: Document the phy_port infrastructure Maxime Chevallier
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=aSiSNA1PaM5Md8ju@shell.armlinux.org.uk \
--to=linux@armlinux$(echo .)org.uk \
--cc=andrew@lunn$(echo .)ch \
--cc=atenart@kernel$(echo .)org \
--cc=christophe.leroy@csgroup$(echo .)eu \
--cc=conor+dt@kernel$(echo .)org \
--cc=daniel@makrotopia$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=devicetree@vger$(echo .)kernel.org \
--cc=dimitri.fedrau@liebherr$(echo .)com \
--cc=edumazet@google$(echo .)com \
--cc=f.fainelli@gmail$(echo .)com \
--cc=herve.codina@bootlin$(echo .)com \
--cc=hkallweit1@gmail$(echo .)com \
--cc=horms@kernel$(echo .)org \
--cc=kabel@kernel$(echo .)org \
--cc=kory.maincent@bootlin$(echo .)com \
--cc=krzk+dt@kernel$(echo .)org \
--cc=kuba@kernel$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-arm-msm@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=maxime.chevallier@bootlin$(echo .)com \
--cc=mwojtas@chromium$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=nicveronese@gmail$(echo .)com \
--cc=o.rempel@pengutronix$(echo .)de \
--cc=pabeni@redhat$(echo .)com \
--cc=robh@kernel$(echo .)org \
--cc=romain.gantois@bootlin$(echo .)com \
--cc=tariqt@nvidia$(echo .)com \
--cc=thomas.petazzoni@bootlin$(echo .)com \
--cc=vladimir.oltean@nxp$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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