netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: Hau <hau@realtek.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	nic_swsd <nic_swsd@realtek.com>
Subject: Re: [PATCH net] r8169: fix rtl8168h wol fail
Date: Wed, 11 Jan 2023 22:40:02 +0100	[thread overview]
Message-ID: <Y78ssmMck/eZTpYz@lunn.ch> (raw)
In-Reply-To: <e201750b-f3be-b62d-4dc6-2a00f4834256@gmail.com>

> >>> In this application(rtl8168h + rtl8211fs) it also supports 100Mbps fiber
> >> module.
> >>
> >> Does RTL8211FS advertise 100Mbps and 1Gbps on the UTP/MDI side in case
> >> of a 100Mbps fiber module?
> > Yes.
> > 
> I think in this case internal PHY and RTL8211FS would negotiate 1Gbps,
> not matching the speed of the 100Mbps fiber module.
> How does this work?

Fibre line side has no autoneg. Both ends need to be using the same
speed, or the SERDES does not synchronise and does not establish link.

You can ask the SFP module what baud rate it supports, and then use
anything up to that baud rate. I've got systems where the SFP is fast
enough to support a 2.5Gbps link, so the MAC indicates both 2.5G and
1G, defaults to 2.5G, and fails to connect to a 1G link peer. You need
to use ethtool to force it to the lower speed before the link works.

But from what i understand, you cannot use a 1000Base-X SFP, set the
MAC to 100Mbps, and expect it to connect to a 100Base-FX SFP. So for
me, the RTL8211FS should not be advertise 100Mbps and 1Gbps, it needs
to talk to the SFP figure out exactly what it is, and only advertise
the one mode which is supported.

    Andrew

  reply	other threads:[~2023-01-11 21:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-05 18:04 [PATCH net] r8169: fix rtl8168h wol fail Chunhao Lin
2023-01-05 19:37 ` Heiner Kallweit
2023-01-05 21:26   ` Andrew Lunn
2023-01-06  6:53     ` Hau
2023-01-06 14:03       ` Andrew Lunn
2023-01-06 18:40       ` Heiner Kallweit
2023-01-10 17:03         ` Hau
2023-01-10 21:59           ` Heiner Kallweit
2023-01-11 17:23             ` Hau
2023-01-11 19:40               ` Heiner Kallweit
2023-01-11 21:40                 ` Andrew Lunn [this message]
2023-01-13 16:23                   ` Hau
2023-01-13 16:36                     ` Andrew Lunn
2023-01-13 22:28                       ` Heiner Kallweit
2023-01-16 17:04                         ` Hau
2023-01-16 17:59                           ` Heiner Kallweit
2023-01-18 16:57                             ` Hau

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=Y78ssmMck/eZTpYz@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=hau@realtek.com \
    --cc=hkallweit1@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=nic_swsd@realtek.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).