From: Stephen Hemminger <stephen@networkplumber.org>
To: Eldho Paul Mathew <eldho789@gmail.com>
Cc: dev@dpdk.org
Subject: Re: Driver: bnxt_en
Date: Fri, 10 Jan 2025 10:04:25 -0800 [thread overview]
Message-ID: <20250110100425.598c939c@hermes.local> (raw)
In-Reply-To: <CAOFFPToi31bmGM76Uuiy0VAOsH=5YM6z0x1UH9EyyPGM-CF4tw@mail.gmail.com>
On Fri, 10 Jan 2025 10:02:48 +0530
Eldho Paul Mathew <eldho789@gmail.com> wrote:
> We are using DPDK 18.05.1
>
> We received a new network card.
>
> Broadcom Inc. and subsidiaries BCM57414 NetXtreme-E 10Gb/25Gb RDMA Ethernet
> Controller
>
> DPDK 18.05.1 has support for this card and driver bnxt_en?
>
> If not, which stable version onwards has this driver support added?
Release 18.05 is not a stable LTS version.
Let me teach you how to look this question up.
To look up device you need the actual PCI-ID, using pcilookup.com
14e4:16d7
Look at source of drivers/net/bnxt/bnxt_ethdev.c for the pci table bnxt_id_pci_map.
The entry for 16d7 is
#define BROADCOM_DEV_ID_57414 0x16d7
Using git blame find the commit that added that:
$ git blame drivers/net/bnxt/bnxt_ethdev.c | grep BROADCOM_DEV_ID_57414
3fab7694403 (Ajit Khaparde 2017-04-26 14:20:02 -0500 51) { RTE_PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, BROADCOM_DEV_ID_57414_VF) },
1f4a84672ec (Ajit Khaparde 2017-01-06 13:55:17 -0600 60) { RTE_PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, BROADCOM_DEV_ID_57414) },
1f4a84672ec (Ajit Khaparde 2017-01-06 13:55:17 -0600 68) { RTE_PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, BROADCOM_DEV_ID_57414_MF) },
3f6d59b0c88 (Kalesh AP 2019-12-02 09:48:07 +0530 4999) case BROADCOM_DEV_ID_57414_VF:
So we want 1f4a84672ec
If you look at that commit with a tool like gitk it shows it happened way back in 17.02
And the card is listed in driver for 18.11
prev parent reply other threads:[~2025-01-10 18:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 4:32 Eldho Paul Mathew
2025-01-10 18:04 ` Stephen Hemminger [this message]
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=20250110100425.598c939c@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=eldho789@gmail.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).