netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Aleksander Jan Bajkowski <olek2@wp.pl>
To: netdev@vger.kernel.org, mkubecek@suse.cz
Cc: Aleksander Jan Bajkowski <olek2@wp.pl>
Subject: [PATCH ethtool-next] sfp: add support for newer SFF-8472 Rate Identifiers
Date: Tue, 29 Sep 2026 23:16:55 +0200	[thread overview]
Message-ID: <20260929211806.1279396-1-olek2@wp.pl> (raw)

This change adds support for newer rate identifiers defined in
SFF-8472.

Standards for SFF-8472
a) SFF_8472 Rev 12.5a dated Jan 16, 2026

Signed-off-by: Aleksander Jan Bajkowski <olek2@wp.pl>
---
 sfpid.c | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/sfpid.c b/sfpid.c
index 065ac4c..994da7e 100644
--- a/sfpid.c
+++ b/sfpid.c
@@ -331,12 +331,28 @@ static void sff8079_show_rate_identifier(const __u8 *id)
 		sprintf(description, "%s", "8/4/2G Rx Rate_Select only");
 		break;
 	case 0x03:
+	case 0x06:
 		sprintf(description, "%s",
 			"8/4/2G Independent Rx & Tx Rate_Select");
 		break;
 	case 0x04:
 		sprintf(description, "%s", "8/4/2G Tx Rate_Select only");
 		break;
+	case 0x08:
+		sprintf(description, "%s", "16/8/4G Rx Rate_Select only");
+		break;
+	case 0x0a:
+		sprintf(description, "%s",
+			"16/8/4G Independent Rx & Tx Rate_Select");
+		break;
+	case 0x0c:
+		sprintf(description, "%s",
+			"32/16/8G Independent Rx & Tx Rate_Select");
+		break;
+	case 0x10:
+		sprintf(description, "%s",
+			"64/32/16G Independent Rx & Tx Rate_Select");
+		break;
 	default:
 		sprintf(description, "%s", "reserved or unknown");
 		break;
-- 
2.53.0


                 reply	other threads:[~2026-09-29 21:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20260929211806.1279396-1-olek2@wp.pl \
    --to=olek2@wp.pl \
    --cc=mkubecek@suse.cz \
    --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;
as well as URLs for NNTP newsgroup(s).