From: Olivier MATZ <olivier.matz@6wind.com>
To: "Zhang, Helin" <helin.zhang@intel.com>
Cc: "Zhang, Qi Z" <qi.z.zhang@intel.com>,
Ivan Nardi <nardi.ivan@gmail.com>, "dev@dpdk.org" <dev@dpdk.org>,
Olivier MATZ <olivier.matz@6wind.com>,
Christos Ricudis <ricudis.christos@gmail.com>,
"Rowden, Aaron F" <aaron.f.rowden@intel.com>,
"Wu, Jingjing" <jingjing.wu@intel.com>
Subject: Re: i40e_aq_get_phy_capabilities() fails when using SFP+ with no link
Date: Tue, 7 Feb 2017 15:56:26 +0100 [thread overview]
Message-ID: <20170207155626.1ecc1bd0@glumotte.dev.6wind.com> (raw)
In-Reply-To: <F35DEAC7BCE34641BA9FAC6BCA4A12E71A9B598A@SHSMSX103.ccr.corp.intel.com>
Hi Helin,
On Mon, 6 Feb 2017 01:36:45 +0000, "Zhang, Helin"
<helin.zhang@intel.com> wrote:
> Hi guys
>
> There may have firmware dependencies, new DPDK version + old firmware
> version may not work. Please refer to below link to see what type of
> firmware has been validated with 16.11 DPDK.
> http://dpdk.org/doc/guides/rel_notes/release_16_11.html#tested-nics
> Then first, you need to upgrade your firmware. Then let us know if
> the issue is still there. Thanks!
>
I updated the firmware, and I confirm it solves my issue described
at: http://dpdk.org/ml/archives/dev/2017-January/054401.html
Thanks,
Olivier
next prev parent reply other threads:[~2017-02-07 14:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 12:32 i40e_aq_get_phy_capabilities() fails when using SFP+ with no link Christos Ricudis
2017-01-10 15:28 ` Olivier MATZ
2017-01-11 1:08 ` Zhang, Helin
2017-01-11 3:00 ` Christos Ricudis
[not found] ` <FC7A99FCE8F15942AB8D6F91FF66D8F694836A60@ORSMSX112.amr.corp.intel.com>
2017-01-12 13:55 ` Olivier MATZ
2017-01-13 13:24 ` Olivier Matz
2017-01-17 12:50 ` Wu, Jingjing
2017-01-18 10:15 ` Christos Ricudis
2017-02-05 15:30 ` Ivan Nardi
2017-02-05 20:19 ` Ivan Nardi
2017-02-06 1:04 ` Zhang, Qi Z
2017-02-06 1:36 ` Zhang, Helin
2017-02-07 14:56 ` Olivier MATZ [this message]
2017-02-07 14:58 ` Zhang, Helin
2017-02-12 16:13 ` Ivan Nardi
2017-02-06 21:06 ` Ivan Nardi
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=20170207155626.1ecc1bd0@glumotte.dev.6wind.com \
--to=olivier.matz@6wind.com \
--cc=aaron.f.rowden@intel.com \
--cc=dev@dpdk.org \
--cc=helin.zhang@intel.com \
--cc=jingjing.wu@intel.com \
--cc=nardi.ivan@gmail.com \
--cc=qi.z.zhang@intel.com \
--cc=ricudis.christos@gmail.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).