DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Daly, Jeff" <jeffd@silicom-usa.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Wang, Haiyue" <haiyue.wang@intel.com>
Subject: RE: [PATCH v2] ixgbe/base: Manual AN-37 for troublesome link partners for X550 SFI
Date: Wed, 18 May 2022 00:03:40 +0000	[thread overview]
Message-ID: <DM4PR11MB599498DB9F8AD1122DB9CC47D7D19@DM4PR11MB5994.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220316185917.4448-1-jeffd@silicom-usa.com>

Jeff:

> -----Original Message-----
> From: Jeff Daly <jeffd@silicom-usa.com>
> Sent: Thursday, March 17, 2022 2:59 AM
> To: dev@dpdk.org
> Cc: Wang, Haiyue <haiyue.wang@intel.com>
> Subject: [PATCH v2] ixgbe/base: Manual AN-37 for troublesome link partners
> for X550 SFI
> 
> Some SFP link partners exhibit a disinclination to autonegotiate with X550
> configured in SFI mode.  This patch enables a manual AN-37 restart to work
> around the problem.

This fix for some specific hardware in base code, unfortunately  Intel DPDK team don't have the device and the knowledge to approve this, the base code is delivered by our kernel software team, I will suggest you can send this to the kernel community to get the right expert to review.

Thanks
Qi


  reply	other threads:[~2022-05-18  0:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-16 18:15 [PATCH] " Jeff Daly
2022-03-16 18:59 ` [PATCH v2] " Jeff Daly
2022-05-18  0:03   ` Zhang, Qi Z [this message]
2022-05-24 10:42     ` Thomas Monjalon
2022-05-24 13:42       ` Zhang, Qi Z
2022-05-24 15:54         ` Thomas Monjalon
2022-05-25  0:11           ` Zhang, Qi Z
2022-05-25  7:55             ` Thomas Monjalon
2022-05-25  8:29               ` Zhang, Qi Z

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=DM4PR11MB599498DB9F8AD1122DB9CC47D7D19@DM4PR11MB5994.namprd11.prod.outlook.com \
    --to=qi.z.zhang@intel.com \
    --cc=dev@dpdk.org \
    --cc=haiyue.wang@intel.com \
    --cc=jeffd@silicom-usa.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).