From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Andrew Lunn <andrew@lunn.ch>, Birger Koblitz <mail@birger-koblitz.de>
Cc: Tony Nguyen <anthony.l.nguyen@intel.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.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>,
intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [Intel-wired-lan] [PATCH net-next v2] ixgbe: Add 10G-BX support
Date: Tue, 14 Oct 2025 15:07:52 +0200 [thread overview]
Message-ID: <77cfe8ef-57d4-4dee-b89d-3f5504653413@molgen.mpg.de> (raw)
In-Reply-To: <0c753725-fd6f-4f85-9371-f7342f86acff@lunn.ch>
Dear Birger, dear Andrew,
Am 14.10.25 um 14:27 schrieb Andrew Lunn:
> On Tue, Oct 14, 2025 at 06:18:27AM +0200, Birger Koblitz wrote:
> 61;8003;1c> Adds support for 10G-BX modules, i.e. 10GBit Ethernet over a single strand
>> Single-Mode fiber
>> The initialization of a 10G-BX SFP+ is the same as for a 10G SX/LX module,
>> and is identified according to SFF-8472 table 5-3, footnote 3 by the
>> 10G Ethernet Compliance Codes field being empty, the Nominal Bit
>> Rate being compatible with 12.5GBit, and the module being a fiber module
>> with a Single Mode fiber link length.
>>
>> This was tested using a Lightron WSPXG-HS3LC-IEA 1270/1330nm 10km
>> transceiver:
>> $ sudo ethtool -m enp1s0f1
>> Identifier : 0x03 (SFP)
>> Extended identifier : 0x04 (GBIC/SFP defined by 2-wire interface ID)
>> Connector : 0x07 (LC)
>> Transceiver codes : 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
>> Encoding : 0x01 (8B/10B)
>> BR Nominal : 10300MBd
>> Rate identifier : 0x00 (unspecified)
>> Length (SMF) : 10km
>> Length (OM2) : 0m
>> Length (OM1) : 0m
>> Length (Copper or Active cable) : 0m
>> Length (OM3) : 0m
>> Laser wavelength : 1330nm
>> Vendor name : Lightron Inc.
>> Vendor OUI : 00:13:c5
>> Vendor PN : WSPXG-HS3LC-IEA
>> Vendor rev : 0000
>> Option values : 0x00 0x1a
>> Option : TX_DISABLE implemented
>> BR margin max : 0%
>> BR margin min : 0%
>> Vendor SN : S142228617
>> Date code : 140611
>> Optical diagnostics support : Yes
>>
>> Signed-off-by: Birger Koblitz <mail@birger-koblitz.de>
>
> Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Unfortunately I do not see the original patch on the mailing list
*intel-wired-lan*, and lore.kernel.org also does not have it [1].
Kind regards,
Paul
[1]:
https://lore.kernel.org/intel-wired-lan/0c753725-fd6f-4f85-9371-f7342f86acff@lunn.ch/T/#u
next prev parent reply other threads:[~2025-10-14 13:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 4:18 Birger Koblitz
2025-10-14 12:27 ` Andrew Lunn
2025-10-14 13:07 ` Paul Menzel [this message]
2025-10-14 13:22 ` [Intel-wired-lan] " Birger Koblitz
2025-10-14 23:36 ` Jacob Keller
2025-10-15 7:59 ` Paul Menzel
2025-10-15 9:16 ` Birger Koblitz
2025-10-15 9:38 ` Paul Menzel
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=77cfe8ef-57d4-4dee-b89d-3f5504653413@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@birger-koblitz.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.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®