From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Raman, Sandeep" <sandeepr@hpe.com>,
"users@dpdk.org" <users@dpdk.org>,
"stable@dpdk.org" <stable@dpdk.org>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: Ajit Khaparde <ajit.khaparde@broadcom.com>
Subject: Re: [dpdk-users] [dpdk-stable] librte_pmd_bnxt library backporting from 17.11 to 16.11
Date: Wed, 29 Nov 2017 09:19:36 -0800 [thread overview]
Message-ID: <bed1d368-a3a3-70d5-de04-f21af266d431@intel.com> (raw)
In-Reply-To: <TU4PR8401MB12807D1483DC5F258DF42990D23B0@TU4PR8401MB1280.NAMPRD84.PROD.OUTLOOK.COM>
On 11/29/2017 7:59 AM, Raman, Sandeep wrote:
> Hi,
>
> With 17.11 DPDK, Broadcom NIC binds successfully. However with 16.11 it fails.
> Is there a way to backport the bnxt library from 17.11 to 16.11?
>
> Any other ways to get this to work with 16.11.
Can Long term stable tree works for you (DPDK 16.11.3) [1], not sure how much of
the bnxt driver back-ported though.
And providing more details abut the failure may be helpful too.
[1]
http://dpdk.org/rel
>
> Thanks,
> Sandeep.
>
next prev parent reply other threads:[~2017-11-29 17:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 15:59 [dpdk-users] " Raman, Sandeep
2017-11-29 17:19 ` Ferruh Yigit [this message]
2017-11-29 21:41 ` [dpdk-users] [dpdk-stable] " Ajit Kumar Khaparde
2017-11-30 3:13 ` Raman, Sandeep
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=bed1d368-a3a3-70d5-de04-f21af266d431@intel.com \
--to=ferruh.yigit@intel.com \
--cc=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
--cc=sandeepr@hpe.com \
--cc=stable@dpdk.org \
--cc=users@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).