From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: "Madalin Bucur (OSS)" <madalin.bucur@oss.nxp.com>
Cc: Heiner Kallweit <hkallweit1@gmail.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"andrew@lunn.ch" <andrew@lunn.ch>,
"f.fainelli@gmail.com" <f.fainelli@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"ykaukab@suse.de" <ykaukab@suse.de>
Subject: Re: [PATCH net-next 2/2] dpaa_eth: support all modes with rate adapting PHYs
Date: Wed, 29 Jan 2020 13:34:57 +0000 [thread overview]
Message-ID: <20200129133457.GG25745@shell.armlinux.org.uk> (raw)
In-Reply-To: <DB8PR04MB698538EB0ED388D39771E159EC0F0@DB8PR04MB6985.eurprd04.prod.outlook.com>
On Thu, Jan 23, 2020 at 07:20:58AM +0000, Madalin Bucur (OSS) wrote:
> There has been a long email thread [1] related to this particular issue.
> Please note USXGMII is one of the supported modes of the AQR PHYs but
> unfortunately not a mode our SoC is capable to use. The DPAA 1 platforms
> do not support USXGMII, they use a serial interface to the PHY, called
> anywhere in the DPAA SoC and PHY datasheets XFI. We're left with "xgmii"
> compatible in the device tree because that's what was available at the
> time in the kernel for 10G and because in the SoC XGMII is the actual
> MII that connects the MAC to the SoC internal blocks that are part of
> the physical layer. Because we have an internal PCS, the DPAA SoC to
> external PHY connection is a PHY-layer internal connection, that has
> no official denomination derived from a standard. In the industry, this
> is called XFI.
People in industry call 1000BASE-X "SGMII" as well, despite SGMII being
a Cisco modification of 1000BASE-X. They are compatible up to a point
but they do not inter-operate. What terms industry uses does not make
those terms correct, and does not mean we should continue their cockups.
The same is true for the XFI. Get over it.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
According to speedtest.net: 11.9Mbps down 500kbps up
prev parent reply other threads:[~2020-01-29 13:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 13:59 [PATCH net-next 0/2] net: phy: aquantia: indicate rate adaptation Madalin Bucur
2020-01-22 13:59 ` [PATCH net-next 1/2] net: phy: aquantia: add rate_adaptation indication Madalin Bucur
2020-01-22 17:58 ` Florian Fainelli
2020-01-23 7:38 ` Madalin Bucur (OSS)
2020-01-27 17:42 ` Florian Fainelli
2020-01-28 7:02 ` Madalin Bucur (OSS)
2020-01-28 15:55 ` Vladimir Oltean
2020-01-29 9:38 ` Madalin Bucur (OSS)
2020-01-29 10:15 ` Vladimir Oltean
2020-01-29 10:53 ` Madalin Bucur (OSS)
2020-01-29 10:57 ` Russell King - ARM Linux admin
2020-01-29 10:59 ` Madalin Bucur (OSS)
2020-01-29 11:57 ` Vladimir Oltean
2020-01-29 12:47 ` Madalin Bucur
2020-01-29 13:44 ` Andrew Lunn
2020-01-29 14:36 ` Madalin Bucur (OSS)
2020-01-29 15:33 ` Andrew Lunn
2020-01-30 9:40 ` Madalin Bucur (OSS)
2020-01-22 13:59 ` [PATCH net-next 2/2] dpaa_eth: support all modes with rate adapting PHYs Madalin Bucur
2020-01-22 20:05 ` Heiner Kallweit
2020-01-23 7:20 ` Madalin Bucur (OSS)
2020-01-29 13:34 ` Russell King - ARM Linux admin [this message]
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=20200129133457.GG25745@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=madalin.bucur@oss.nxp.com \
--cc=netdev@vger.kernel.org \
--cc=ykaukab@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.