[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YSvrBvLJ3IRTn9FR@lunn.ch>
Date: Sun, 29 Aug 2021 22:16:06 +0200
From: Andrew Lunn <andrew@...n.ch>
To: "Machnikowski, Maciej" <maciej.machnikowski@...el.com>
Cc: Richard Cochran <richardcochran@...il.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"intel-wired-lan@...ts.osuosl.org" <intel-wired-lan@...ts.osuosl.org>,
"abyagowi@...com" <abyagowi@...com>,
"Nguyen, Anthony L" <anthony.l.nguyen@...el.com>,
"davem@...emloft.net" <davem@...emloft.net>,
"kuba@...nel.org" <kuba@...nel.org>,
"linux-kselftest@...r.kernel.org" <linux-kselftest@...r.kernel.org>
Subject: Re: [RFC v2 net-next 1/2] rtnetlink: Add new RTM_GETSYNCESTATE
message to get SyncE status
> > I have nothing against exposing the DPLL if you need to, however I'd like to have
> > an interface that support plain Gigabit as well. This could be done in a generic
> > way by offering Control Register 9 as described in 802.3.
Are we talking about Clause 22, register 9, also known as MII_CTRL1000?
> This part of Gigabit interface is a different part of SyncE device. It controls Master/Slave
> operation of auto-negotiation.
This is controlled using ethtool -s
ethtool -s devname [speed N] [duplex half|full] [port tp|aui|bnc|mii]
....
[sopass xx:yy:zz:aa:bb:cc] [master-slave preferred-
master|preferred-slave|forced-master|forced-slave]
Andrew
Powered by blists - more mailing lists