From: Ed Czeck <ed.czeck@atomicrules.com>
To: dev@dpdk.org
Cc: ferruh.yigit@xilinx.com, ktraynor@redhat.com, bluca@debian.org,
Shepard Siegel <shepard.siegel@atomicrules.com>,
John Miller <john.miller@atomicrules.com>
Subject: [PATCH v3 6/7] net/ark: add new devices to support list
Date: Tue, 7 Jun 2022 11:49:16 -0400 [thread overview]
Message-ID: <20220607154917.1871118-6-ed.czeck@atomicrules.com> (raw)
In-Reply-To: <20220607154917.1871118-1-ed.czeck@atomicrules.com>
update device list is doc
Signed-off-by: Ed Czeck <ed.czeck@atomicrules.com>
---
v3: clarification in doc for LTS support
---
doc/guides/nics/ark.rst | 7 +++++--
drivers/net/ark/ark_ethdev.c | 6 ++++++
2 files changed, 11 insertions(+), 2 deletions(-)
diff --git a/doc/guides/nics/ark.rst b/doc/guides/nics/ark.rst
index 29c0a07d60..44488f0ce8 100644
--- a/doc/guides/nics/ark.rst
+++ b/doc/guides/nics/ark.rst
@@ -297,6 +297,9 @@ ARK PMD supports the following Arkville RTL PCIe instances including:
* ``1d6c:1017`` - AR-ARK-FX1 [Arkville 64B Multi-Homed Primary Endpoint]
* ``1d6c:1018`` - AR-ARK-FX1 [Arkville 64B Multi-Homed Secondary Endpoint]
* ``1d6c:1019`` - AR-ARK-FX1 [Arkville 64B Multi-Homed Tertiary Endpoint]
+* ``1d6c:101a`` - AR-ARK-SRIOV-FX0 [Arkville 32B Primary Physical Function]
+* ``1d6c:101b`` - AR-ARK-SRIOV-FX1 [Arkville 64B Primary Physical Function]
+* ``1d6c:101c`` - AR-ARK-SRIOV-VF [Arkville Virtual Function]
* ``1d6c:101e`` - AR-ARKA-FX1 [Arkville 64B DPDK Data Mover for Agilex R-Tile]
* ``1d6c:101f`` - AR-TK242 [2x100GbE Packet Capture Device]
@@ -307,7 +310,8 @@ Arkville's firmware and its PMD have version dependencies which must
be stepped together at certain releases. PMD code ensures the versions are
compatible. The following lists shows where version compatible steps have
occurred. If other combinations are required, please contact Atomic Rules
-support.
+support. LTS versions of DPDK remain compatible with the corresponding
+Arkville version.
* DPDK 22.07 requires Arkville 22.07.
* DPDK 22.03 requires Arkville 22.03.
@@ -337,7 +341,6 @@ Unsupported Features
Features that may be part of, or become part of, the Arkville RTL IP that are
not currently supported or exposed by the ARK PMD include:
-* PCIe SR-IOV Virtual Functions (VFs)
* Arkville's Packet Generator Control and Status
* Arkville's Packet Director Control and Status
* Arkville's Packet Checker Control and Status
diff --git a/drivers/net/ark/ark_ethdev.c b/drivers/net/ark/ark_ethdev.c
index 2abc35283d..377631e66e 100644
--- a/drivers/net/ark/ark_ethdev.c
+++ b/drivers/net/ark/ark_ethdev.c
@@ -94,6 +94,9 @@ static const struct rte_pci_id pci_id_ark_map[] = {
{RTE_PCI_DEVICE(AR_VENDOR_ID, 0x1017)},
{RTE_PCI_DEVICE(AR_VENDOR_ID, 0x1018)},
{RTE_PCI_DEVICE(AR_VENDOR_ID, 0x1019)},
+ {RTE_PCI_DEVICE(AR_VENDOR_ID, 0x101a)},
+ {RTE_PCI_DEVICE(AR_VENDOR_ID, 0x101b)},
+ {RTE_PCI_DEVICE(AR_VENDOR_ID, 0x101c)},
{RTE_PCI_DEVICE(AR_VENDOR_ID, 0x101e)},
{RTE_PCI_DEVICE(AR_VENDOR_ID, 0x101f)},
{.vendor_id = 0, /* sentinel */ },
@@ -127,6 +130,9 @@ ark_device_caps[] = {
SET_DEV_CAPS(0x1017, true),
SET_DEV_CAPS(0x1018, true),
SET_DEV_CAPS(0x1019, true),
+ SET_DEV_CAPS(0x101a, true),
+ SET_DEV_CAPS(0x101b, true),
+ SET_DEV_CAPS(0x101c, false),
SET_DEV_CAPS(0x101e, false),
SET_DEV_CAPS(0x101f, false),
{.device_id = 0,}
--
2.25.1
next prev parent reply other threads:[~2022-06-07 15:50 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 21:22 [PATCH 1/4] net/ark: update mpu code to match current hardware version Ed Czeck
2022-05-02 21:22 ` [PATCH 2/4] net/ark: update ddm " Ed Czeck
2022-05-02 21:22 ` [PATCH 3/4] net/ark: update udm " Ed Czeck
2022-05-02 21:22 ` [PATCH 4/4] net/ark: add new devices to support list Ed Czeck
2022-05-05 15:37 ` [PATCH v1 1/5] net/ark: update mpu code to match current hardware version Ed Czeck
2022-05-05 15:37 ` [PATCH v1 2/5] net/ark: update ddm " Ed Czeck
2022-05-05 15:37 ` [PATCH v1 3/5] net/ark: update udm " Ed Czeck
2022-05-05 15:37 ` [PATCH v1 4/5] net/ark: add new devices to support list Ed Czeck
2022-05-05 15:37 ` [PATCH v1 5/5] net/ark: add PMD support for devices as virtual functions Ed Czeck
2022-05-06 21:27 ` [PATCH v1 1/5] net/ark: update mpu code to match current hardware version Ed Czeck
2022-05-06 21:27 ` [PATCH v1 2/5] net/ark: update ddm " Ed Czeck
2022-05-06 21:27 ` [PATCH v1 3/5] net/ark: update udm " Ed Czeck
2022-05-06 21:27 ` [PATCH v1 4/5] net/ark: add new devices to support list Ed Czeck
2022-05-06 21:27 ` [PATCH v1 5/5] net/ark: add PMD support for devices as virtual functions Ed Czeck
2022-05-18 12:56 ` Ferruh Yigit
2022-05-18 12:54 ` [PATCH v1 1/5] net/ark: update mpu code to match current hardware version Ferruh Yigit
2022-05-19 10:13 ` Kevin Traynor
2022-05-19 21:36 ` [PATCH v2 1/7] devtools: add Atomic Rules acronyms for commit checks Ed Czeck
2022-05-19 21:36 ` [PATCH v2 2/7] net/ark: update MPU functions for firmware update Ed Czeck
2022-05-19 21:36 ` [PATCH v2 3/7] net/ark: update DDM " Ed Czeck
2022-05-19 21:36 ` [PATCH v2 4/7] net/ark: update UDM " Ed Czeck
2022-05-19 21:36 ` [PATCH v2 5/7] net/ark: report additional errors from firmware Ed Czeck
2022-05-19 21:36 ` [PATCH v2 6/7] net/ark: add new devices to support list Ed Czeck
2022-05-20 8:14 ` Andrew Rybchenko
2022-05-19 21:36 ` [PATCH v2 7/7] net/ark: add PMD support for devices as virtual functions Ed Czeck
2022-05-20 14:15 ` [PATCH v2 1/7] devtools: add Atomic Rules acronyms for commit checks Ed Czeck
2022-05-20 14:15 ` [PATCH v2 2/7] net/ark: update MPU functions for firmware update Ed Czeck
2022-05-23 14:39 ` Ferruh Yigit
2022-05-20 14:15 ` [PATCH v2 3/7] net/ark: update DDM " Ed Czeck
2022-05-20 14:15 ` [PATCH v2 4/7] net/ark: update UDM " Ed Czeck
2022-05-20 14:15 ` [PATCH v2 5/7] net/ark: report additional errors from firmware Ed Czeck
2022-05-20 14:15 ` [PATCH v2 6/7] net/ark: add new devices to support list Ed Czeck
2022-05-20 14:15 ` [PATCH v2 7/7] net/ark: add PMD support for devices as virtual functions Ed Czeck
2022-05-23 14:38 ` Ferruh Yigit
2022-06-07 15:49 ` [PATCH v3 1/7] devtools: add Atomic Rules acronyms for commit checks Ed Czeck
2022-06-07 15:49 ` [PATCH v3 2/7] net/ark: update MPU functions for firmware update Ed Czeck
2022-06-07 15:49 ` [PATCH v3 3/7] net/ark: update DDM " Ed Czeck
2022-06-07 15:49 ` [PATCH v3 4/7] net/ark: update UDM " Ed Czeck
2022-06-07 15:49 ` [PATCH v3 5/7] net/ark: report additional errors from firmware Ed Czeck
2022-06-07 15:49 ` Ed Czeck [this message]
2022-06-07 15:49 ` [PATCH v3 7/7] net/ark: add PMD support for devices as virtual functions Ed Czeck
2022-06-07 21:31 ` [PATCH v4 1/7] devtools: add Atomic Rules acronyms for commit checks Ed Czeck
2022-06-07 21:31 ` [PATCH v4 2/7] net/ark: update MPU functions for firmware update Ed Czeck
2022-06-07 21:31 ` [PATCH v4 3/7] net/ark: update DDM " Ed Czeck
2022-06-07 21:31 ` [PATCH v4 4/7] net/ark: update UDM " Ed Czeck
2022-06-07 21:31 ` [PATCH v4 5/7] net/ark: report additional errors from firmware Ed Czeck
2022-06-07 21:31 ` [PATCH v4 6/7] net/ark: add new devices to support list Ed Czeck
2022-06-07 21:31 ` [PATCH v4 7/7] net/ark: add PMD support for devices as virtual functions Ed Czeck
2022-06-08 8:41 ` [PATCH v4 1/7] devtools: add Atomic Rules acronyms for commit checks Ferruh Yigit
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=20220607154917.1871118-6-ed.czeck@atomicrules.com \
--to=ed.czeck@atomicrules.com \
--cc=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@xilinx.com \
--cc=john.miller@atomicrules.com \
--cc=ktraynor@redhat.com \
--cc=shepard.siegel@atomicrules.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;
as well as URLs for NNTP newsgroup(s).