DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Mody, Rasesh" <Rasesh.Mody@cavium.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
	Alexey Kardashevskiy <aik@ozlabs.ru>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "Patil, Harish" <Harish.Patil@cavium.com>
Subject: Re: [dpdk-dev] [PATCH dpdk v2] bnx2x: Update firmware versions
Date: Sat, 29 Apr 2017 00:31:47 +0000	[thread overview]
Message-ID: <BLUPR0701MB15724FCEFC38D9AFA60AAFA79F120@BLUPR0701MB1572.namprd07.prod.outlook.com> (raw)
In-Reply-To: <98b632fe-3782-740e-f9c4-3cc5d7659869@intel.com>

Hi Alexey,

> From: Ferruh Yigit [mailto:ferruh.yigit@intel.com]
> Sent: Wednesday, April 26, 2017 2:18 AM
> 
> On 4/26/2017 9:08 AM, Alexey Kardashevskiy wrote:
> > Recent kernels/distros have updated firmware images, use them.
> > In order to keep support of older distros (such as Fedora 19 or Ubuntu
> > 14.04), this also tries fallback to an order firmware version.
> >
> > Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
> > ---
> > Changes:
> > v2:
> > * in addition to the very new firmware images, this adds fallback to
> > some older firmware present in 3yo distros

To my knowledge, latest kernel/distro have 7.2.51.0 firmware image currently being used by the BNX2X PMD.
Did you test BNX2X PMD with updated and fallback firmware images? If yes, how was it tested and did you encounter any issue? Did you try SRIOV VF with these firmware versions?

Thanks!
-Rasesh

> 
> Hi Alexey,
> 
> CC'ing maintainers.
> 
> Thank you for the patch, please CC maintainers in your patches.
> 
> Thanks,
> ferruh


  parent reply	other threads:[~2017-04-29  0:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-26  8:08 Alexey Kardashevskiy
2017-04-26  9:18 ` Ferruh Yigit
2017-04-27  4:14   ` Alexey Kardashevskiy
2017-04-27  4:29     ` Ferruh Yigit
2017-04-29  0:31   ` Mody, Rasesh [this message]
2017-04-29  5:12     ` Alexey Kardashevskiy
2017-06-28 16:01       ` Ferruh Yigit
2017-06-28 17:05         ` Mody, Rasesh

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=BLUPR0701MB15724FCEFC38D9AFA60AAFA79F120@BLUPR0701MB1572.namprd07.prod.outlook.com \
    --to=rasesh.mody@cavium.com \
    --cc=Harish.Patil@cavium.com \
    --cc=aik@ozlabs.ru \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.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).