From: Hau <hau@realtek.com>
To: Heiner Kallweit <hkallweit1@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: nic_swsd <nic_swsd@realtek.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH net-next] r8169: add support for rtl8168h(revid 0x2a) + rtl8211fs fiber application
Date: Fri, 22 Jul 2022 15:21:42 +0000 [thread overview]
Message-ID: <ab3f4c46d0a7489597150dc47a5211cb@realtek.com> (raw)
In-Reply-To: <356f4285-1e83-ab14-c890-4131acd8e61d@gmail.com>
> On 21.07.2022 16:45, Chunhao Lin wrote:
> > rtl8168h(revid 0x2a) + rtl8211fs is for fiber related application.
> > rtl8168h will control rtl8211fs via its eeprom or gpo pins.
>
> RTL8168h has an integrated PHY, how is it with rev 0x2a? Can this version be
> used with an external PHY only?
> And how about the case that somebody combines this chip version with
> another PHY that supports fiber? It seems the code makes the assumption
> that rev2a is always coupled with an external RTL8211FS.
>
> Are there any realworld devices that use RTL8168H with fiber?
>
RTL8168h with revid 0x2a is always coupled with an external RTL8211FS. Right now there is no plan for it to connect to another external PHY.
RTL8168H with revid 0x15 and it with revid 0x2a are the same chip. But revid 0x2a is used for identify this application.
Following is the diagram for this application.
+-------------+ Ethernet Cable +-------------+
| +-------------------- + |
| | MDIO(EEDN) | |fiber
| rtl8168h +----------------- ---+ rtl8211fs +------+
| | MDC(EECS) | |
| +--------------------+ |
+-------------+ +--------------+
------Please consider the environment before printing this e-mail.
next prev parent reply other threads:[~2022-07-22 15:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 14:45 [PATCH net-next] r8169: add support for rtl8168h(revid 0x2a) + rtl8211fs fiber application Chunhao Lin
2022-07-21 20:35 ` Heiner Kallweit
2022-07-22 3:27 ` Andrew Lunn
2022-07-22 15:26 ` Hau
2022-07-22 15:21 ` Hau [this message]
2022-07-22 1:42 ` Jakub Kicinski
2022-07-22 15:22 ` 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=ab3f4c46d0a7489597150dc47a5211cb@realtek.com \
--to=hau@realtek.com \
--cc=hkallweit1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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).