From: Chaoyong He <chaoyong.he@corigine.com>
To: dev@dpdk.org
Cc: oss-drivers@corigine.com, niklas.soderlund@corigine.com,
James Hershaw <james.hershaw@corigine.com>
Subject: [PATCH] net/nfp: support Corigine PCIe ID for the nfp PMD
Date: Fri, 26 Aug 2022 13:50:14 +0800 [thread overview]
Message-ID: <1661493014-24112-1-git-send-email-chaoyong.he@corigine.com> (raw)
From: James Hershaw <james.hershaw@corigine.com>
Previously the nfp driver as supported NFP chips with the Netronome PCIe
ID. This patch extends the PMD to also support NFP chips with the
Corigine PCIe vendor ID (0x1da8), which at this point are assumed to be
otherwise identical from a software perspective.
Signed-off-by: James Hershaw <james.hershaw@corigine.com>
Reviewed-by: Niklas Söderlund <niklas.soderlund@corigine.com>
---
drivers/net/nfp/nfp_common.h | 2 ++
drivers/net/nfp/nfp_ethdev.c | 12 ++++++++++++
drivers/net/nfp/nfp_ethdev_vf.c | 8 ++++++++
3 files changed, 22 insertions(+)
diff --git a/drivers/net/nfp/nfp_common.h b/drivers/net/nfp/nfp_common.h
index 6d917e4..6ceb7e9 100644
--- a/drivers/net/nfp/nfp_common.h
+++ b/drivers/net/nfp/nfp_common.h
@@ -16,6 +16,8 @@
#define NFP_NET_PMD_VERSION "0.1"
#define PCI_VENDOR_ID_NETRONOME 0x19ee
+#define PCI_VENDOR_ID_CORIGINE 0x1da8
+
#define PCI_DEVICE_ID_NFP3800_PF_NIC 0x3800
#define PCI_DEVICE_ID_NFP3800_VF_NIC 0x3803
#define PCI_DEVICE_ID_NFP4000_PF_NIC 0x4000
diff --git a/drivers/net/nfp/nfp_ethdev.c b/drivers/net/nfp/nfp_ethdev.c
index 5cdd34e..3ab82d3 100644
--- a/drivers/net/nfp/nfp_ethdev.c
+++ b/drivers/net/nfp/nfp_ethdev.c
@@ -1071,6 +1071,18 @@
PCI_DEVICE_ID_NFP6000_PF_NIC)
},
{
+ RTE_PCI_DEVICE(PCI_VENDOR_ID_CORIGINE,
+ PCI_DEVICE_ID_NFP3800_PF_NIC)
+ },
+ {
+ RTE_PCI_DEVICE(PCI_VENDOR_ID_CORIGINE,
+ PCI_DEVICE_ID_NFP4000_PF_NIC)
+ },
+ {
+ RTE_PCI_DEVICE(PCI_VENDOR_ID_CORIGINE,
+ PCI_DEVICE_ID_NFP6000_PF_NIC)
+ },
+ {
.vendor_id = 0,
},
};
diff --git a/drivers/net/nfp/nfp_ethdev_vf.c b/drivers/net/nfp/nfp_ethdev_vf.c
index d304d78..affea9d 100644
--- a/drivers/net/nfp/nfp_ethdev_vf.c
+++ b/drivers/net/nfp/nfp_ethdev_vf.c
@@ -505,6 +505,14 @@
PCI_DEVICE_ID_NFP6000_VF_NIC)
},
{
+ RTE_PCI_DEVICE(PCI_VENDOR_ID_CORIGINE,
+ PCI_DEVICE_ID_NFP3800_VF_NIC)
+ },
+ {
+ RTE_PCI_DEVICE(PCI_VENDOR_ID_CORIGINE,
+ PCI_DEVICE_ID_NFP6000_VF_NIC)
+ },
+ {
.vendor_id = 0,
},
};
--
1.8.3.1
next reply other threads:[~2022-08-26 5:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 5:50 Chaoyong He [this message]
2022-08-26 6:08 ` Baowen Zheng
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=1661493014-24112-1-git-send-email-chaoyong.he@corigine.com \
--to=chaoyong.he@corigine.com \
--cc=dev@dpdk.org \
--cc=james.hershaw@corigine.com \
--cc=niklas.soderlund@corigine.com \
--cc=oss-drivers@corigine.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).