DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Raman, Sandeep" <sandeepr@hpe.com>
To: Ajit Kumar Khaparde <ajit.khaparde@broadcom.com>,
	Ferruh Yigit <ferruh.yigit@intel.com>,
	"Ram, Vinayak (NFV BU)" <vinayak.ram@hpe.com>
Cc: "users@dpdk.org" <users@dpdk.org>,
	"stable@dpdk.org" <stable@dpdk.org>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"K S, Gopinath (NFV)" <gopinathks@hpe.com>
Subject: Re: [dpdk-dev] [dpdk-stable] librte_pmd_bnxt library backporting from 17.11 to 16.11
Date: Thu, 30 Nov 2017 03:13:27 +0000	[thread overview]
Message-ID: <TU4PR8401MB1280837326DD6C13CC51A3F9D2380@TU4PR8401MB1280.NAMPRD84.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <-3909302079043608748@unknownmsgid>

Ajith, Ferruh,

The device is BRCM 631 NIC. Let me get details about the failure.
16.11.3 is what I have compiled and the NIC bind did not work.

Thanks,
Sandeep.
From: Ajit Kumar Khaparde [mailto:ajit.khaparde@broadcom.com]
Sent: Thursday, November 30, 2017 3:11 AM
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: Raman, Sandeep <sandeepr@hpe.com>; users@dpdk.org; stable@dpdk.org; dev@dpdk.org
Subject: Re: [dpdk-stable] librte_pmd_bnxt library backporting from 17.11 to 16.11

Thanks Ferruh.
Raman,
What device are you trying this on?
Can you send the device id?

Thanks
Ajit

On Nov 29, 2017, at 11:19, Ferruh Yigit <ferruh.yigit@intel.com<mailto:ferruh.yigit@intel.com>> wrote:
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.



      reply	other threads:[~2017-11-30  3:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-29 15:59 [dpdk-dev] " Raman, Sandeep
2017-11-29 17:19 ` [dpdk-dev] [dpdk-stable] " Ferruh Yigit
2017-11-29 21:41   ` Ajit Kumar Khaparde
2017-11-30  3:13     ` Raman, Sandeep [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=TU4PR8401MB1280837326DD6C13CC51A3F9D2380@TU4PR8401MB1280.NAMPRD84.PROD.OUTLOOK.COM \
    --to=sandeepr@hpe.com \
    --cc=ajit.khaparde@broadcom.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=gopinathks@hpe.com \
    --cc=stable@dpdk.org \
    --cc=users@dpdk.org \
    --cc=vinayak.ram@hpe.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).