DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Yang, Qiming" <qiming.yang@intel.com>
To: "Yigit, Ferruh" <ferruh.yigit@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Wu, Jingjing" <jingjing.wu@intel.com>,
	"Xing, Beilei" <beilei.xing@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: add i40e firmware upgrade guide
Date: Wed, 16 Aug 2017 09:12:45 +0000	[thread overview]
Message-ID: <F5DF4F0E3AFEF648ADC1C3C33AD4DBF16F7D3695@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <53b04b4b-06ea-90e2-6174-534e2d17a18d@intel.com>

> -----Original Message-----
> From: Yigit, Ferruh
> Sent: Tuesday, August 15, 2017 4:52 PM
> To: Yang, Qiming <qiming.yang@intel.com>; dev@dpdk.org
> Cc: Wu, Jingjing <jingjing.wu@intel.com>; Xing, Beilei <beilei.xing@intel.com>
> Subject: Re: [dpdk-dev] [PATCH] doc: add i40e firmware upgrade guide
> 
> On 8/15/2017 4:26 AM, Qiming Yang wrote:
> > This patch adds one link to DPDK i40e doc, which is for users on how
> > to upgrade firmware.
> 
> Does it make sense to add a link to download the FW too?
> 
This one is good enough, it has detail about updating process, and in chapter 3.0 includes the link to get the latest NVM.
So it's no need to add another link to download the FW.
> >
> > Signed-off-by: Qiming Yang <qiming.yang@intel.com>
> > ---
> >  doc/guides/nics/i40e.rst | 2 ++
> >  1 file changed, 2 insertions(+)
> >
> > diff --git a/doc/guides/nics/i40e.rst b/doc/guides/nics/i40e.rst index
> > bc200d3..606375d 100644
> > --- a/doc/guides/nics/i40e.rst
> > +++ b/doc/guides/nics/i40e.rst
> > @@ -78,6 +78,8 @@ Prerequisites
> >  - To get better performance on Intel platforms, please follow the "How to get
> best performance with NICs on Intel platforms"
> >    section of the :ref:`Getting Started Guide for Linux <linux_gsg>`.
> >
> > +- Upgrade the NVM/FW version follow the `Intel® Ethernet NVM Update
> > +Tool Quick Usage Guide for Linux
> > +  <https://www-
> ssl.intel.com/content/www/us/en/embedded/products/networking/nvm-
> update-tool-quick-linux-usage-guide.html>`_ if need.
> >
> >  Pre-Installation Configuration
> >  ------------------------------
> >


  reply	other threads:[~2017-08-16  9:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-15  3:26 Qiming Yang
2017-08-15  8:52 ` Ferruh Yigit
2017-08-16  9:12   ` Yang, Qiming [this message]
2017-09-04 16:35 ` Mcnamara, John
2017-09-05  9:41   ` 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=F5DF4F0E3AFEF648ADC1C3C33AD4DBF16F7D3695@SHSMSX101.ccr.corp.intel.com \
    --to=qiming.yang@intel.com \
    --cc=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=jingjing.wu@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).