From: Andrew Lunn <andrew@lunn.ch>
To: Xander Wilmink <xwilmink@gmail.com>
Cc: netdev@vger.kernel.org, Jonas Jelonek <jelonek.jonas@gmail.com>
Subject: Re: [PATCH net-next] net: sfp: Add quirk for Dell M14MK module
Date: Fri, 7 Aug 2026 23:43:21 +0200 [thread overview]
Message-ID: <5c5ba685-242f-4699-9933-87910a251ff4@lunn.ch> (raw)
In-Reply-To: <20260807213025.1206-1-xwilmink@gmail.com>
On Fri, Aug 07, 2026 at 09:30:25PM +0000, Xander Wilmink wrote:
> Greetings,
>
> This adds an quirk for the Dell M14MK (S28-10G-25G-SR-85C) SFP28 module.
> These are short range fiber modules, and should advertise 10000baseSR/Full.
> Incorrectly these advertise as being a copper module: 10000baseCR/Full.
> The link fails to come up, and the kernel logs "unsupported SFP module:
> no common interface modes."
> With the quirk added, the 10Gbit/s link comes up.
>
> Tested on a Linksys LGS328PC with OpenWRT SNAPSHOT version:
> OpenWrt SNAPSHOT r35298-2a73f02e56 / LuCI Master 26.190.71895~a18dc50.
> Ethtool advertises now "10000baseSR/Full" and the link works on 10Gbit/s.
>
> Thank you for your time.
>
> Kind regards,
>
> Xander Wilmink
The commit message should be formal, since it becomes part of the
Linux kernel. Please remove the Greetings, Thanks, Kind regards etc.
> +static void sfp_quirk_25g_10g_dual(const struct sfp_eeprom_id *id,
> + struct sfp_module_caps *caps)
> +{
> + linkmode_set_bit(ETHTOOL_LINK_MODE_10000baseSR_Full_BIT,
> + caps->link_modes);
> + __set_bit(PHY_INTERFACE_MODE_10GBASER, caps->interfaces);
Do you need to clear 10000baseCR/Full here?
Does it get the 25G part correct? The quirk itself is only touching
10G, so the _25g_ in the name seems irrelevant.
Andrew
---
pw-bot: cr
next prev parent reply other threads:[~2026-08-07 21:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 21:30 [PATCH net-next] net: sfp: Add quirk for Dell M14MK module Xander Wilmink
2026-08-07 21:43 ` Andrew Lunn [this message]
2026-08-20 4:34 ` kernel test robot
2026-08-20 11:58 ` kernel test robot
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=5c5ba685-242f-4699-9933-87910a251ff4@lunn.ch \
--to=andrew@lunn.ch \
--cc=jelonek.jonas@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=xwilmink@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