From: Ed Czeck <ed.czeck@atomicrules.com>
To: dev@dpdk.org, stephen@networkplumber.org
Cc: Shepard Siegel <shepard.siegel@atomicrules.com>,
John Miller <john.miller@atomicrules.com>
Subject: [PATCH v2 1/4] net/ark: add PCIe IDS for newly supported devices
Date: Wed, 10 Sep 2025 14:57:17 -0400 [thread overview]
Message-ID: <20250910185720.995300-1-ed.czeck@atomicrules.com> (raw)
Update documentation and release notes
update link speed capabilities for 200G and 400G
Signed-off-by: Ed Czeck <ed.czeck@atomicrules.com>
---
v2:
- included 2 more device id
- updated link speeds
---
doc/guides/nics/ark.rst | 7 +++++++
drivers/net/ark/ark_ethdev.c | 10 +++++++++-
2 files changed, 16 insertions(+), 1 deletion(-)
diff --git a/doc/guides/nics/ark.rst b/doc/guides/nics/ark.rst
index 6aabde2ed5..c8ed57289b 100644
--- a/doc/guides/nics/ark.rst
+++ b/doc/guides/nics/ark.rst
@@ -310,6 +310,12 @@ ARK PMD supports the following Arkville RTL PCIe instances including:
* ``1d6c:1024`` - AR-TK242 [2x100GbE Packet Capture Device]
* ``1d6c:1025`` - AR-TK242-FX2 [2x100GbE Gen5 Packet Capture Device]
* ``1d6c:1026`` - AR-TK242-FX2 [1x200GbE Gen5 Packet Capture Device]
+* ``1d6c:102a`` - AR-TK242-FX2 [4x100GbE Gen5 Packet Capture Device]
+* ``1d6c:102b`` - AR-ARKV-FX1 [Arkville 128B DPDK Data Mover for Versal/CPM5]
+* ``1d6c:102c`` - AR-TK242-V80 [Gen5 PCAP Processor]
+* ``1d6c:102d`` - AR-TK242-FX2 [8x10GbE Gen5 Packet Capture-Replay Device]
+* ``1d6c:102e`` - AR-TK242-FX2 [8x25GbE Gen5 Packet Capture-Replay Device]
+* ``1d6c:102f`` - AR-TK242-FX2 [1x400GbE Gen5 Packet Capture-Replay Device]
Arkville RTL Core Configurations
--------------------------------
@@ -322,6 +328,7 @@ stream interfaces for both AMD/Xilinx and Intel FPGAs.
* ARK-FX0 - 256-bit 32B datapath (PCIe Gen3, Gen4)
* ARK-FX1 - 512-bit 64B datapath (PCIe Gen3, Gen4, Gen5)
+* ARKV-FX1 - 1024-bit 128B datapath (AMD PCIe Versal, Gen5 )
* ARK-FX2 - 1024-bit 128B datapath (PCIe Gen5x16 Only)
DPDK and Arkville Firmware Versioning
diff --git a/drivers/net/ark/ark_ethdev.c b/drivers/net/ark/ark_ethdev.c
index c029dc46b3..8d3c0a1b02 100644
--- a/drivers/net/ark/ark_ethdev.c
+++ b/drivers/net/ark/ark_ethdev.c
@@ -102,6 +102,12 @@ static const struct rte_pci_id pci_id_ark_map[] = {
{RTE_PCI_DEVICE(AR_VENDOR_ID, 0x1024)},
{RTE_PCI_DEVICE(AR_VENDOR_ID, 0x1025)},
{RTE_PCI_DEVICE(AR_VENDOR_ID, 0x1026)},
+ {RTE_PCI_DEVICE(AR_VENDOR_ID, 0x102a)},
+ {RTE_PCI_DEVICE(AR_VENDOR_ID, 0x102b)},
+ {RTE_PCI_DEVICE(AR_VENDOR_ID, 0x102c)},
+ {RTE_PCI_DEVICE(AR_VENDOR_ID, 0x102d)},
+ {RTE_PCI_DEVICE(AR_VENDOR_ID, 0x102e)},
+ {RTE_PCI_DEVICE(AR_VENDOR_ID, 0x102f)},
{.vendor_id = 0, /* sentinel */ },
};
@@ -733,7 +739,9 @@ eth_ark_dev_info_get(struct rte_eth_dev *dev,
RTE_ETH_LINK_SPEED_25G |
RTE_ETH_LINK_SPEED_40G |
RTE_ETH_LINK_SPEED_50G |
- RTE_ETH_LINK_SPEED_100G);
+ RTE_ETH_LINK_SPEED_100G |
+ RTE_ETH_LINK_SPEED_200G |
+ RTE_ETH_LINK_SPEED_400G);
dev_info->rx_offload_capa = RTE_ETH_RX_OFFLOAD_TIMESTAMP;
--
2.34.1
next reply other threads:[~2025-09-10 18:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 18:57 Ed Czeck [this message]
2025-09-10 18:57 ` [PATCH v2 2/4] net/ark: remove double mbuf frees Ed Czeck
2025-09-10 18:57 ` [PATCH v2 3/4] net/ark: improve ring handling for segmented packets Ed Czeck
2025-09-10 18:57 ` [PATCH v2 4/4] net/ark: improve Rx queue recovery after mbuf exhaustion Ed Czeck
-- strict thread matches above, loose matches on Subject: below --
2025-09-03 21:28 [PATCH 1/4] net/ark: add PCIe IDS for newly supported devices Ed Czeck
2025-09-10 19:04 ` [PATCH v2 " Ed Czeck
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=20250910185720.995300-1-ed.czeck@atomicrules.com \
--to=ed.czeck@atomicrules.com \
--cc=dev@dpdk.org \
--cc=john.miller@atomicrules.com \
--cc=shepard.siegel@atomicrules.com \
--cc=stephen@networkplumber.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).