From: Olivier MATZ <olivier.matz@6wind.com>
To: "Rowden, Aaron F" <aaron.f.rowden@intel.com>
Cc: Christos Ricudis <ricudis.christos@gmail.com>,
"Zhang, Helin" <helin.zhang@intel.com>,
Olivier MATZ <olivier.matz@6wind.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Wu, Jingjing" <jingjing.wu@intel.com>
Subject: Re: [dpdk-dev] i40e_aq_get_phy_capabilities() fails when using SFP+ with no link
Date: Thu, 12 Jan 2017 14:55:54 +0100 [thread overview]
Message-ID: <20170112145554.44506d05@glumotte.dev.6wind.com> (raw)
In-Reply-To: <FC7A99FCE8F15942AB8D6F91FF66D8F694836A60@ORSMSX112.amr.corp.intel.com>
Hi,
On Wed, 11 Jan 2017 20:51:58 +0000, "Rowden, Aaron F"
<aaron.f.rowden@intel.com> wrote:
> Hi Helin,
>
> I'm checking on this to see why it could be failing but I don’t think
> this is one part of formal validation. Intel modules are always what
> is recommended.
>
> Aaron
>
> > Hi Helin,
> >
> > > On 11 Jan 2017, at 09:08, Zhang, Helin <helin.zhang@intel.com>
> > > wrote:
> > >
> > > Hi Aaron
> > >
> > > Is the SFP+ (Finisar FTLX8571D3BCL) supported and validated by
> > > Intel? It seems there is some PHY issue in this case.
> >
> > As the original reporter of this issue, I will test with validated
> > SFP+s and will report on my testing.
> >
> > Shouldn’t unsupported SFP+s be blacklisted in the I40E driver?
> >
Just to let you know that in my case the SFP are Intel ones.
Maybe it's a different issue.
I see there are some i40e fixes in the net-next repo, I'll give a try
with this version.
Regards,
Olivier
next prev parent reply other threads:[~2017-01-12 13:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 12:32 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 [this message]
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
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=20170112145554.44506d05@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=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).