From: Ivan Malov <ivan.malov@arknetworks.am>
To: dev@dpdk.org
Cc: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Andy Moreton <andy.moreton@amd.com>,
Pieter Jansen Van Vuuren <pieter.jansen-van-vuuren@amd.com>,
Viacheslav Galaktionov <viacheslav.galaktionov@arknetworks.am>
Subject: [PATCH 0/9] net/sfc: SFN7xxx deprecation and Medford fixes
Date: Tue, 30 Dec 2025 01:35:18 +0400 [thread overview]
Message-ID: <20251229213527.37907-1-ivan.malov@arknetworks.am> (raw)
The series provides various fixes, primarily for Medford4 support.
It also fixes a legacy flow control bug; due to hardware constraints
in the fix, SFN7xxx NICs are now marked as deprecated.
Andy Moreton (1):
common/sfc_efx/base: count Rx TRUNC ERR as CRC errors on X4
Ivan Malov (8):
doc: remove support for AMD Solarflare SFN7xxx family boards
common/sfc_efx/base: fix flow control setting on legacy MCDI
common/sfc_efx/base: fix indication of requestable FEC flags
common/sfc_efx/base: define mask for pause mode capabilities
net/sfc: avoid speed reset when setting FEC in started state
net/sfc: rework the capability check that is done on FEC set
net/sfc: drop AUTO from FEC capabilities and fix the comment
net/sfc: fix reporting status of autonegotiation to the user
doc/guides/nics/sfc_efx.rst | 14 ---
doc/guides/rel_notes/release_26_03.rst | 4 +
drivers/common/sfc_efx/base/ef10_ev.c | 41 +++++--
drivers/common/sfc_efx/base/ef10_mac.c | 35 ++++--
drivers/common/sfc_efx/base/ef10_nic.c | 57 +++++-----
drivers/common/sfc_efx/base/efx.h | 1 +
drivers/common/sfc_efx/base/efx_np.c | 2 +-
drivers/net/sfc/sfc.h | 2 +-
drivers/net/sfc/sfc_ethdev.c | 141 +++++++++++++++----------
drivers/net/sfc/sfc_ev.c | 7 +-
drivers/net/sfc/sfc_port.c | 8 +-
drivers/net/sfc/sfc_repr.c | 2 +-
12 files changed, 193 insertions(+), 121 deletions(-)
--
2.47.3
next reply other threads:[~2025-12-29 21:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-29 21:35 Ivan Malov [this message]
2025-12-29 21:35 ` [PATCH 1/9] doc: remove support for AMD Solarflare SFN7xxx family boards Ivan Malov
2025-12-29 21:35 ` [PATCH 2/9] common/sfc_efx/base: fix flow control setting on legacy MCDI Ivan Malov
2025-12-29 21:35 ` [PATCH 3/9] common/sfc_efx/base: fix indication of requestable FEC flags Ivan Malov
2025-12-29 21:35 ` [PATCH 4/9] common/sfc_efx/base: define mask for pause mode capabilities Ivan Malov
2025-12-29 21:35 ` [PATCH 5/9] common/sfc_efx/base: count Rx TRUNC ERR as CRC errors on X4 Ivan Malov
2025-12-29 21:35 ` [PATCH 6/9] net/sfc: avoid speed reset when setting FEC in started state Ivan Malov
2025-12-29 21:35 ` [PATCH 7/9] net/sfc: rework the capability check that is done on FEC set Ivan Malov
2025-12-29 21:35 ` [PATCH 8/9] net/sfc: drop AUTO from FEC capabilities and fix the comment Ivan Malov
2025-12-29 21:35 ` [PATCH 9/9] net/sfc: fix reporting status of autonegotiation to the user Ivan Malov
2025-12-31 19:13 ` [PATCH 0/9] net/sfc: SFN7xxx deprecation and Medford fixes Stephen Hemminger
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=20251229213527.37907-1-ivan.malov@arknetworks.am \
--to=ivan.malov@arknetworks.am \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=andy.moreton@amd.com \
--cc=dev@dpdk.org \
--cc=pieter.jansen-van-vuuren@amd.com \
--cc=viacheslav.galaktionov@arknetworks.am \
/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).