DPDK usage discussions
 help / color / mirror / Atom feed
From: "Raman, Sandeep" <sandeepr@hpe.com>
To: "users@dpdk.org" <users@dpdk.org>,
	"stable@dpdk.org" <stable@dpdk.org>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-users] librte_pmd_bnxt library backporting from 17.11 to 16.11
Date: Wed, 29 Nov 2017 15:59:33 +0000	[thread overview]
Message-ID: <TU4PR8401MB12807D1483DC5F258DF42990D23B0@TU4PR8401MB1280.NAMPRD84.PROD.OUTLOOK.COM> (raw)

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.

Thanks,
Sandeep.

             reply	other threads:[~2017-11-29 15:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-29 15:59 Raman, Sandeep [this message]
2017-11-29 17:19 ` [dpdk-users] [dpdk-stable] " Ferruh Yigit
2017-11-29 21:41   ` 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=TU4PR8401MB12807D1483DC5F258DF42990D23B0@TU4PR8401MB1280.NAMPRD84.PROD.OUTLOOK.COM \
    --to=sandeepr@hpe.com \
    --cc=dev@dpdk.org \
    --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).