netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 13:35:08 -0700	[thread overview]
Message-ID: <4fbf4bb9-0700-4f59-965b-a064f853f2c0@intel.com> (raw)
In-Reply-To: <3531fc467a80bf02b83b94707fc3039b51ecd4c5@ycharbi.fr>



On 5/23/2024 1:19 PM, kernel.org-fo5k2w@ycharbi.fr wrote:
>> One more thing: Could you confirm if this behavior appears in the 5.19.9
>> driver from the Intel website or source forge? I'm curious if this is a
>> case of a fix that never got published to the netdev community.
>>
>> Thanks,
>> Jake
> 
> I can confirm that the result of the “Supported link modes:” section is identical with the Intel ixgbe-5.19.9 driver:
> uname -r
> 5.10.0-29-amd64
> 
> apt install linux-headers-$(uname -r) gcc make
> wget https://downloadmirror.intel.com/812532/ixgbe-5.19.9.tar.gz
> tar xf ixgbe-5.19.9.tar.gz -C /usr/local/src/
> make -j 8
> 
> modinfo ./ixgbe.ko
> rmmod ixgbe
> modprobe dca
> insmod ./ixgbe.ko
> 
> # eno1 is up
> ethtool eno1
> Settings for eno1:
> 	Supported ports: [ FIBRE ]
> 	Supported link modes:   10000baseT/Full
> 	Supported pause frame use: Symmetric
> 	Supports auto-negotiation: No
> 	Supported FEC modes: Not reported
> 	Advertised link modes:  10000baseT/Full
> 	Advertised pause frame use: Symmetric
> 	Advertised auto-negotiation: No
> 	Advertised FEC modes: Not reported
> 	Speed: 10000Mb/s
> 	Duplex: Full
> 	Auto-negotiation: off
> 	Port: Direct Attach Copper
> 	PHYAD: 0
> 	Transceiver: internal
> 	Supports Wake-on: d
> 	Wake-on: d
>         Current message level: 0x00000007 (7)
>                                drv probe link
> 	Link detected: yes

Thanks. At a glance from reviewing code, it looks like ixgbe simply
collapses all non-backplane links into 10000baseT/Full.

  reply	other threads:[~2024-05-23 20:35 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
2024-05-23 18:49             ` Jacob Keller
2024-05-23 20:19               ` kernel.org-fo5k2w
2024-05-23 20:35                 ` Jacob Keller [this message]
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=4fbf4bb9-0700-4f59-965b-a064f853f2c0@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).