From: Jacob Keller <jacob.e.keller@intel.com>
To: <kernel.org-fo5k2w@ycharbi.fr>, Jeff Daly <jeffd@silicom-usa.com>,
"Simon Horman" <horms@kernel.org>
Cc: <netdev@vger.kernel.org>
Subject: Re: [PATCH net] Revert "ixgbe: Manual AN-37 for troublesome link partners for X550 SFI"
Date: Thu, 23 May 2024 11:47:51 -0700 [thread overview]
Message-ID: <c9ba7475-ffc6-4e82-b2f1-74fd295060ee@intel.com> (raw)
In-Reply-To: <69ac60c954ce47462b177c145622793aa3fbeaeb@ycharbi.fr>
On 5/23/2024 9:49 AM, kernel.org-fo5k2w@ycharbi.fr wrote:
>> The link is an SFP-10GBase-CX1?
>
> As I understand it, CX1 is the name given to Twinax copper cables such as the one I used in the experiments in this thread. It's therefore a priori the right value to display for this kind of connection (instead of “10000baseT/Full”).
>
I'm filing an internal tracking bug regarding this as well.
> Thanks again for your hard work in finding a solution. You can always contact me later so that I can carry out tests if you need. The machine is at least available for 1 year for testing purposes.
>
> Best regards,
> Yohan.
Appreciate it. Hopefully we can find something that works for both cases.
next prev parent reply other threads:[~2024-05-23 18:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-21 0:21 [PATCH net] Revert "ixgbe: Manual AN-37 for troublesome link partners for X550 SFI" Jacob Keller
2024-05-21 16:41 ` Simon Horman
2024-05-21 16:49 ` Jeff Daly
2024-05-21 17:12 ` kernel.org-fo5k2w
2024-05-21 21:05 ` Jacob Keller
2024-05-23 16:15 ` Jacob Keller
2024-05-23 16:18 ` Jeff Daly
2024-05-23 16:49 ` kernel.org-fo5k2w
2024-05-23 18:47 ` Jacob Keller [this message]
2024-05-23 18:49 ` Jacob Keller
2024-05-23 20:19 ` kernel.org-fo5k2w
2024-05-23 20:35 ` Jacob Keller
2024-06-26 14:30 ` Jeff Daly
2024-05-23 9:00 ` patchwork-bot+netdevbpf
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=c9ba7475-ffc6-4e82-b2f1-74fd295060ee@intel.com \
--to=jacob.e.keller@intel.com \
--cc=horms@kernel.org \
--cc=jeffd@silicom-usa.com \
--cc=kernel.org-fo5k2w@ycharbi.fr \
--cc=netdev@vger.kernel.org \
/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).