[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BN8PR12MB32666F34D45D7881BDD4CAB3D3350@BN8PR12MB3266.namprd12.prod.outlook.com>
Date: Mon, 13 Jan 2020 13:54:28 +0000
From: Jose Abreu <Jose.Abreu@...opsys.com>
To: Andrew Lunn <andrew@...n.ch>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Joao Pinto <Joao.Pinto@...opsys.com>,
Florian Fainelli <f.fainelli@...il.com>,
"Heiner Kallweit" <hkallweit1@...il.com>,
"David S. Miller" <davem@...emloft.net>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Russell King <rmk+kernel@....linux.org.uk>
Subject: RE: [RFC net-next] net: phy: Add basic support for Synopsys XPCS
using a PHY driver
From: Andrew Lunn <andrew@...n.ch>
Date: Jan/13/2020, 13:38:45 (UTC+00:00)
> On Mon, Jan 13, 2020 at 02:11:08PM +0100, Jose Abreu wrote:
> > Adds the basic support for XPCS including support for USXGMII.
>
> Hi Jose
>
> Please could you describe the 'big picture'. What comes after the
> XPCS? An SFP? A copper PHY? How in Linux do you combine this PHY and
> whatever comes next using PHYLINK?
>
> Or do only support backplane with this, and the next thing in the line
> is the peers XPCS?
My current setup is this:
Host PC x86 -> PCI -> XGMAC -> XPCS -> SERDES 10G-BASE-R -> QSFP+
The only piece that needs configuration besides XGMAC is the XPCS hereby
I "called" it a PHY ... Anyway, this is an RFC because I'm not entirely
sure about the approach. Hmm ?
---
Thanks,
Jose Miguel Abreu
Powered by blists - more mailing lists