From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: dev@dpdk.org
Cc: ferruh.yigit@intel.com, Scott Branden <scott.branden@broadcom.com>
Subject: [dpdk-dev] [PATCH v5 2/3] net/bnxt: add support for Stingray PF devices ids
Date: Fri, 13 Apr 2018 14:07:55 -0700 [thread overview]
Message-ID: <20180413210756.10549-2-ajit.khaparde@broadcom.com> (raw)
In-Reply-To: <20180413210756.10549-1-ajit.khaparde@broadcom.com>
From: Scott Branden <scott.branden@broadcom.com>
Add support for Stingray PF devices ids:
BCM58802 = 0xd802
BCM58804 = 0xd804
BCM58808 = 0x16f0
Signed-off-by: Scott Branden <scott.branden@broadcom.com>
Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
---
drivers/net/bnxt/bnxt_ethdev.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/drivers/net/bnxt/bnxt_ethdev.c b/drivers/net/bnxt/bnxt_ethdev.c
index a856c7e0e..1d4ff54b7 100644
--- a/drivers/net/bnxt/bnxt_ethdev.c
+++ b/drivers/net/bnxt/bnxt_ethdev.c
@@ -69,6 +69,9 @@ int bnxt_logtype_driver;
#define BROADCOM_DEV_ID_57407_MF 0x16ea
#define BROADCOM_DEV_ID_57414_MF 0x16ec
#define BROADCOM_DEV_ID_57416_MF 0x16ee
+#define BROADCOM_DEV_ID_58802 0xd802
+#define BROADCOM_DEV_ID_58804 0xd804
+#define BROADCOM_DEV_ID_58808 0x16f0
static const struct rte_pci_id bnxt_pci_id_map[] = {
{ RTE_PCI_DEVICE(PCI_VENDOR_ID_BROADCOM,
@@ -107,6 +110,9 @@ static const struct rte_pci_id bnxt_pci_id_map[] = {
{ RTE_PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, BROADCOM_DEV_ID_57317_SFP) },
{ RTE_PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, BROADCOM_DEV_ID_57414_MF) },
{ RTE_PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, BROADCOM_DEV_ID_57416_MF) },
+ { RTE_PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, BROADCOM_DEV_ID_58802) },
+ { RTE_PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, BROADCOM_DEV_ID_58804) },
+ { RTE_PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, BROADCOM_DEV_ID_58808) },
{ .vendor_id = 0, /* sentinel */ },
};
--
2.15.1 (Apple Git-101)
next prev parent reply other threads:[~2018-04-13 21:08 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-21 18:06 [dpdk-dev] [PATCH 0/4] bnxt patchset Ajit Khaparde
2018-03-21 18:06 ` [dpdk-dev] [PATCH 1/4] introduce Broadcom Stingray Ajit Khaparde
2018-03-30 10:34 ` Ferruh Yigit
2018-03-30 18:54 ` Scott Branden
2018-03-21 18:06 ` [dpdk-dev] [PATCH 2/4] net/bnxt: add support for Stingray PF devices ids Ajit Khaparde
2018-03-30 10:35 ` Ferruh Yigit
2018-03-30 18:24 ` Scott Branden
2018-04-10 0:20 ` [dpdk-dev] [PATCH v4 0/3] bnxt patchset to support Stingray product family Ajit Khaparde
2018-04-10 0:20 ` [dpdk-dev] [PATCH v4 1/3] introduce Broadcom Stingray Ajit Khaparde
2018-04-10 0:20 ` [dpdk-dev] [PATCH v4 2/3] net/bnxt: add support for Stingray PF devices ids Ajit Khaparde
2018-04-10 0:20 ` [dpdk-dev] [PATCH v4 3/3] doc: add Broadcom Stingray SoC support to release notes Ajit Khaparde
2018-04-11 19:07 ` Ferruh Yigit
2018-04-13 21:07 ` [dpdk-dev] [PATCH v5 1/3] introduce Broadcom Stingray Ajit Khaparde
2018-04-13 21:07 ` Ajit Khaparde [this message]
2018-04-13 21:07 ` [dpdk-dev] [PATCH v5 3/3] doc: add Broadcom Stingray SoC support to release notes Ajit Khaparde
2018-04-13 23:07 ` [dpdk-dev] [PATCH v5 1/3] introduce Broadcom Stingray Ferruh Yigit
2018-03-21 18:06 ` [dpdk-dev] [PATCH 3/4] mk: allow kernel artifacts to be located in output directory Ajit Khaparde
2018-03-30 10:35 ` Ferruh Yigit
2018-03-30 18:23 ` Scott Branden
2018-04-03 14:18 ` Ferruh Yigit
[not found] ` <CACZ4nhuwOp99YiaD75TzQ1igPgnjsayqHLnXyaNmmpySVZefPA@mail.gmail.com>
2018-04-06 18:10 ` Scott Branden
2018-04-06 21:31 ` Ferruh Yigit
2018-04-06 22:32 ` Scott Branden
2018-04-10 14:59 ` Ferruh Yigit
2018-04-10 20:30 ` Scott Branden
2018-03-21 18:06 ` [dpdk-dev] [PATCH 4/4] igb_uio: bind error if pcie bridge Ajit Khaparde
2018-03-26 17:24 ` Ferruh Yigit
2018-03-26 18:05 ` Scott Branden
2018-03-26 18:20 ` Ferruh Yigit
2018-03-26 19:13 ` Scott Branden
2018-03-26 20:43 ` [dpdk-dev] [PATCH v2] " Ajit Khaparde
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=20180413210756.10549-2-ajit.khaparde@broadcom.com \
--to=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=scott.branden@broadcom.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).