From: Shepard Siegel <shepard.siegel@atomicrules.com>
To: ed.czeck@atomicrules.com
Cc: dev@dpdk.org, Shepard Siegel <shepard.siegel@atomicrules.com>
Subject: [PATCH v3 1/2] net/ark: introduce Arkville FX2 PCIe device
Date: Fri, 10 Feb 2023 20:26:58 -0500 [thread overview]
Message-ID: <20230211012659.2611391-1-shepard.siegel@atomicrules.com> (raw)
In-Reply-To: <20230210193837.2604100-1-shepard.siegel@atomicrules.com>
This commit introduces the Arkville FX2 PCIe device.
Arkville FX2 provides support for PCIe Gen5x16 endpoints.
FX2 is backwards-compatible with the net/ark PMD so that no
changes other than the whitelist addition in this patch are
needed for the basic operation of this device.
Additional details are in a doc: patch with this submission.
Signed-off-by: Shepard Siegel <shepard.siegel@atomicrules.com>
---
drivers/net/ark/ark_ethdev.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/net/ark/ark_ethdev.c b/drivers/net/ark/ark_ethdev.c
index c654a229f7..b2995427c8 100644
--- a/drivers/net/ark/ark_ethdev.c
+++ b/drivers/net/ark/ark_ethdev.c
@@ -99,6 +99,7 @@ static const struct rte_pci_id pci_id_ark_map[] = {
{RTE_PCI_DEVICE(AR_VENDOR_ID, 0x101c)},
{RTE_PCI_DEVICE(AR_VENDOR_ID, 0x101e)},
{RTE_PCI_DEVICE(AR_VENDOR_ID, 0x101f)},
+ {RTE_PCI_DEVICE(AR_VENDOR_ID, 0x1022)},
{.vendor_id = 0, /* sentinel */ },
};
--
2.25.1
next prev parent reply other threads:[~2023-02-11 1:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 19:38 [PATCH] doc: update ark guide Shepard Siegel
2023-02-10 20:34 ` Ferruh Yigit
2023-02-10 21:03 ` Shepard Siegel
2023-02-10 21:10 ` Ferruh Yigit
2023-02-10 21:43 ` Shepard Siegel
2023-02-10 21:46 ` Shepard Siegel
2023-02-10 22:35 ` [PATCH v2] " Shepard Siegel
2023-02-10 22:56 ` Ferruh Yigit
2023-02-10 23:47 ` Shepard Siegel
2023-02-11 1:26 ` Shepard Siegel [this message]
2023-02-11 1:26 ` [PATCH v3 2/2] doc: add Arkville FX2 PCIe device description Shepard Siegel
2023-02-11 2:13 ` Ferruh Yigit
2023-02-11 3:07 ` Shepard Siegel
2023-02-13 12:07 ` 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=20230211012659.2611391-1-shepard.siegel@atomicrules.com \
--to=shepard.siegel@atomicrules.com \
--cc=dev@dpdk.org \
--cc=ed.czeck@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).