From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: Stephen Hurd <stephen.hurd@broadcom.com>,
Rasesh Mody <rasesh.mody@qlogic.com>,
Harish Patil <harish.patil@qlogic.com>,
Sony Chacko <sony.chacko@qlogic.com>,
web@dpdk.org
Subject: Re: [dpdk-web] [PATCH] add bnxt and qede in list of supported NICs
Date: Thu, 28 Jul 2016 14:31:21 -0500 [thread overview]
Message-ID: <CACZ4nht=_OkEE6C97NqNWX2cstOEYmp_hqfPtGgeUAy=vZvmHw@mail.gmail.com> (raw)
In-Reply-To: <4094696.2v6sgOsls5@xps13>
On Thu, Jul 28, 2016 at 1:36 PM, Thomas Monjalon <thomas.monjalon@6wind.com>
wrote:
> 2016-07-28 09:14, Thomas Monjalon:
> > 2016-07-27 15:59, Ajit Khaparde:
> > > On Wed, Jul 27, 2016 at 11:46 AM, Thomas Monjalon <
> thomas.monjalon@6wind.com
> > > > wrote:
> > > > + <li><a href="/doc/guides/nics/bnxt.html">bnxt</a> (NetXtreme
> C-Series)</li>
> > > >
> > > Thanks Thomas.
> > > If you don't mind, can you use this instead?
> > >
> > > + <li><a href="/doc/guides/nics/bnxt.html">bnxt</a>
> (NetXtreme-C/NetXtreme-E)</li>
> >
> > Do you mean NetXtreme-E is supported in 16.07?
> > It does not appear in the release notes.
>
> Applied with suggested change.
>
> I'm still interested to know what is NetXtreme-E and is it supported in
> 16.07?
>
The E there stands for Enterprise. While the "C" is for Cloud.
Coming to support.. Yes. It is supported.
The list of PCI IDs in bnxt_ethdev.c includes the NetXtreme-C as well as
NetXtreme-E product family.
I hope this helps. Let me know if you need more info.
Thanks
-Ajit
next prev parent reply other threads:[~2016-07-28 19:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-27 16:46 Thomas Monjalon
2016-07-27 20:59 ` Ajit Khaparde
2016-07-28 7:14 ` Thomas Monjalon
2016-07-28 18:36 ` Thomas Monjalon
2016-07-28 18:39 ` Ajit Khaparde
2016-07-28 19:31 ` Ajit Khaparde [this message]
2016-07-28 20:09 ` Thomas Monjalon
2016-07-28 7:20 ` Harish Patil
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='CACZ4nht=_OkEE6C97NqNWX2cstOEYmp_hqfPtGgeUAy=vZvmHw@mail.gmail.com' \
--to=ajit.khaparde@broadcom.com \
--cc=harish.patil@qlogic.com \
--cc=rasesh.mody@qlogic.com \
--cc=sony.chacko@qlogic.com \
--cc=stephen.hurd@broadcom.com \
--cc=thomas.monjalon@6wind.com \
--cc=web@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).