patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Mody, Rasesh" <Rasesh.Mody@cavium.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
	Dept-Eng DPDK Dev <Dept-EngDPDKDev@cavium.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH] doc: update qede management firmware guide
Date: Fri, 8 Jun 2018 18:49:57 +0000	[thread overview]
Message-ID: <SN1PR07MB403272BEE383DE15EBE37F6F9F7B0@SN1PR07MB4032.namprd07.prod.outlook.com> (raw)
In-Reply-To: <95b73a68-0ed1-b7f0-9175-d2514acbb8eb@intel.com>

> From: Ferruh Yigit [mailto:ferruh.yigit@intel.com]
> Sent: Friday, June 08, 2018 11:10 AM
> 
> On 6/1/2018 11:57 PM, Rasesh Mody wrote:
> > Fixes: c49a438fce90 ("doc: update qede guide and features")
> > Fixes: db86fbe54d90 ("doc: update qede PMD NIC guide")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Rasesh Mody <rasesh.mody@cavium.com>
> > ---
> >  doc/guides/nics/qede.rst |   12 ++++++------
> >  1 file changed, 6 insertions(+), 6 deletions(-)
> >
> > diff --git a/doc/guides/nics/qede.rst b/doc/guides/nics/qede.rst index
> > a4adf75..5ebd119 100644
> > --- a/doc/guides/nics/qede.rst
> > +++ b/doc/guides/nics/qede.rst
> > @@ -66,12 +66,12 @@ Prerequisites
> >    or `QLogic Driver Download Center
> <http://driverdownloads.qlogic.com/QLogicDriverDownloads_UI/DefaultNe
> wSearch.aspx>`_.
> >    To download firmware file from QLogic website, select adapter category,
> model and DPDK Poll Mode Driver.
> >
> > -- Requires management firmware (MFW) version **8.34.x.x** or higher
> > to be
> > -  flashed on to the adapter. If the required management firmware is
> > not
> > -  available then download from
> > -  `QLogic Driver Download Center
> <http://driverdownloads.qlogic.com/QLogicDriverDownloads_UI/DefaultNe
> wSearch.aspx>`_.
> > -  For downloading firmware upgrade utility, select adapter category, model
> and Linux distro.
> > -  To flash the management firmware refer to the instructions in the QLogic
> Firmware Upgrade Utility Readme document.
> > +- It is highly recommended that the NIC be updated with the latest
> available management firmware (MFW) version supported for that NIC.
> 
> Does it make sense to document minimum supported FW by the DPDK
> driver?

The DPDK driver is backward compatible with older versions of Management FW (MFW). However, some of the newer features may not be available in older MFW. So, we recommend users to upgrade to latest available version.

I will check internally and get back on whether and if we need to put a minimum supported version in here.

Thanks!
-Rasesh
> 
> > +  Management Firmware and Firmware Upgrade Utility for Cavium
> > + FastLinQ(r) branded adapters can be downloaded from  `Driver Download
> Center
> <http://driverdownloads.qlogic.com/QLogicDriverDownloads_UI/DefaultNe
> wSearch.aspx>`_.
> > +  For downloading Firmware Upgrade Utility, select NIC category, model
> and Linux distro.
> > +  To update the management firmware, refer to the instructions in the
> Firmware Upgrade Utility Readme document.
> > +  For OEM branded adapters please follow the instruction provided by the
> OEM to update the Management Firmware on the NIC.
> >
> >  - SR-IOV requires Linux PF driver version **8.20.x.x** or higher.
> >    If the required PF driver is not available then download it from
> >


  reply	other threads:[~2018-06-08 18:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-01 22:57 Rasesh Mody
2018-06-08 18:09 ` Ferruh Yigit
2018-06-08 18:49   ` Mody, Rasesh [this message]
2018-06-28  0:33     ` Mody, Rasesh
2018-06-28  0:32 ` [dpdk-stable] [PATCH v2] " Rasesh Mody
2018-06-28 16:53   ` Ferruh Yigit

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=SN1PR07MB403272BEE383DE15EBE37F6F9F7B0@SN1PR07MB4032.namprd07.prod.outlook.com \
    --to=rasesh.mody@cavium.com \
    --cc=Dept-EngDPDKDev@cavium.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).