From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ajit Khaparde <ajit.khaparde@broadcom.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] bnxt: Add new device ids
Date: Wed, 26 Apr 2017 09:52:26 +0100 [thread overview]
Message-ID: <ea173cf3-9ef3-6b73-b56d-86ccf1c31b96@intel.com> (raw)
In-Reply-To: <20170425215315.6167-1-ajit.khaparde@broadcom.com>
On 4/25/2017 10:53 PM, Ajit Khaparde wrote:
> Add support for new device ids.
Hi Ajit,
Is NIC documentation (doc/guides/nics/bnxt.rst) needs to get updated for
these new devices?
Also if http://dpdk.org/doc/nics needs update please send another web patch.
Thanks,
ferruh
>
> Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
> ---
> drivers/net/bnxt/bnxt_ethdev.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/net/bnxt/bnxt_ethdev.c b/drivers/net/bnxt/bnxt_ethdev.c
> index 5dc3ff0..7805221 100644
> --- a/drivers/net/bnxt/bnxt_ethdev.c
> +++ b/drivers/net/bnxt/bnxt_ethdev.c
> @@ -60,6 +60,8 @@ static const char bnxt_version[] =
>
> #define PCI_VENDOR_ID_BROADCOM 0x14E4
>
> +#define BROADCOM_DEV_ID_STRATUS_NIC 0x1614
> +#define BROADCOM_DEV_ID_57414_VF 0x16c1
> #define BROADCOM_DEV_ID_57301 0x16c8
> #define BROADCOM_DEV_ID_57302 0x16c9
> #define BROADCOM_DEV_ID_57304_PF 0x16ca
> @@ -94,6 +96,8 @@ static const char bnxt_version[] =
> #define BROADCOM_DEV_ID_57416_MF 0x16ee
>
> static const struct rte_pci_id bnxt_pci_id_map[] = {
> + { RTE_PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, BROADCOM_DEV_ID_STRATUS_NIC) },
> + { RTE_PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, BROADCOM_DEV_ID_57414_VF) },
> { RTE_PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, BROADCOM_DEV_ID_57301) },
> { RTE_PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, BROADCOM_DEV_ID_57302) },
> { RTE_PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, BROADCOM_DEV_ID_57304_PF) },
>
next prev parent reply other threads:[~2017-04-26 8:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-25 21:53 Ajit Khaparde
2017-04-26 8:52 ` Ferruh Yigit [this message]
2017-04-26 18:41 ` Ajit Khaparde
2017-04-26 19:01 ` Ferruh Yigit
2017-04-26 19:02 ` 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=ea173cf3-9ef3-6b73-b56d-86ccf1c31b96@intel.com \
--to=ferruh.yigit@intel.com \
--cc=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.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).