From: Andrew Lunn <andrew@lunn.ch>
To: David Mestre <dev@davidmestre.net>
Cc: netdev@vger.kernel.org, linux@armlinux.org.uk
Subject: Re: [RFC net-next] net: sfp: add quirk for OEM SFP-2.5G-T-C
Date: Sat, 24 Oct 2026 16:21:14 +0200 [thread overview]
Message-ID: <1f015d68-c1b0-486d-8edf-bfc453f97f7c@lunn.ch> (raw)
In-Reply-To: <e0137c6e-7ecb-4b45-8108-70058f9906e1@davidmestre.net>
On Fri, Oct 23, 2026 at 07:49:29PM +0200, David Mestre wrote:
> The OEM SFP-2.5G-T-C module needs the same fixed 2500BASE-X host link
> as the existing OEM SFP-2.5G-T entry. On a ZBT Z8803BE (MT7988),
> the module has no carrier with in-band autonegotiation enabled.
> Forcing 2500 Mbit/s, full duplex and autonegotiation off restores
> the link.
>
> The existing OEM SFP-2.5G-T entry requires an exact part-name match,
> so it does not match the -C variant. Reuse its quirk for the exact
> additional part name.
>
> Signed-off-by: David Mestre <dev@davidmestre.net>
This is something which could go via net, rather than net-next.
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Andrew
prev parent reply other threads:[~2026-10-24 14:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 17:49 [RFC net-next] net: sfp: add quirk for OEM SFP-2.5G-T-C David Mestre
2026-10-24 14:21 ` Andrew Lunn [this message]
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=1f015d68-c1b0-486d-8edf-bfc453f97f7c@lunn.ch \
--to=andrew@lunn.ch \
--cc=dev@davidmestre.net \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
/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