From: Andrew Lunn <andrew@lunn.ch>
To: "Machnikowski, Maciej" <maciej.machnikowski@intel.com>
Cc: Richard Cochran <richardcochran@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>,
"abyagowi@fb.com" <abyagowi@fb.com>,
"Nguyen, Anthony L" <anthony.l.nguyen@intel.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"kuba@kernel.org" <kuba@kernel.org>,
"linux-kselftest@vger.kernel.org"
<linux-kselftest@vger.kernel.org>
Subject: Re: [RFC v2 net-next 1/2] rtnetlink: Add new RTM_GETSYNCESTATE message to get SyncE status
Date: Sun, 29 Aug 2021 22:16:06 +0200 [thread overview]
Message-ID: <YSvrBvLJ3IRTn9FR@lunn.ch> (raw)
In-Reply-To: <PH0PR11MB495126A63998DABA5B5DE184EACA9@PH0PR11MB4951.namprd11.prod.outlook.com>
> > 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
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Lunn <andrew@lunn.ch>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [RFC v2 net-next 1/2] rtnetlink: Add new RTM_GETSYNCESTATE message to get SyncE status
Date: Sun, 29 Aug 2021 22:16:06 +0200 [thread overview]
Message-ID: <YSvrBvLJ3IRTn9FR@lunn.ch> (raw)
In-Reply-To: <PH0PR11MB495126A63998DABA5B5DE184EACA9@PH0PR11MB4951.namprd11.prod.outlook.com>
> > 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
next prev parent reply other threads:[~2021-08-29 20:16 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-29 8:05 [RFC v2 net-next 0/2] Add RTNL interface for SyncE Maciej Machnikowski
2021-08-29 8:05 ` [Intel-wired-lan] " Maciej Machnikowski
2021-08-29 8:05 ` [RFC v2 net-next 1/2] rtnetlink: Add new RTM_GETSYNCESTATE message to get SyncE status Maciej Machnikowski
2021-08-29 8:05 ` [Intel-wired-lan] " Maciej Machnikowski
2021-08-29 15:10 ` Richard Cochran
2021-08-29 15:10 ` [Intel-wired-lan] " Richard Cochran
2021-08-29 16:42 ` Machnikowski, Maciej
2021-08-29 16:42 ` [Intel-wired-lan] " Machnikowski, Maciej
2021-08-29 20:16 ` Andrew Lunn [this message]
2021-08-29 20:16 ` Andrew Lunn
2021-08-30 20:57 ` Richard Cochran
2021-08-30 20:57 ` [Intel-wired-lan] " Richard Cochran
2021-08-30 23:29 ` Jakub Kicinski
2021-08-30 23:29 ` [Intel-wired-lan] " Jakub Kicinski
2021-08-31 10:20 ` Machnikowski, Maciej
2021-08-31 10:20 ` [Intel-wired-lan] " Machnikowski, Maciej
2021-08-31 13:33 ` Jakub Kicinski
2021-08-31 13:33 ` [Intel-wired-lan] " Jakub Kicinski
2021-08-31 14:07 ` Machnikowski, Maciej
2021-08-31 14:07 ` [Intel-wired-lan] " Machnikowski, Maciej
2021-08-31 14:18 ` Jakub Kicinski
2021-08-31 14:18 ` [Intel-wired-lan] " Jakub Kicinski
2021-08-31 15:19 ` Machnikowski, Maciej
2021-08-31 15:19 ` [Intel-wired-lan] " Machnikowski, Maciej
2021-08-31 15:32 ` Jakub Kicinski
2021-08-31 15:32 ` [Intel-wired-lan] " Jakub Kicinski
2021-08-31 16:00 ` Machnikowski, Maciej
2021-08-31 16:00 ` [Intel-wired-lan] " Machnikowski, Maciej
2021-08-31 16:19 ` Richard Cochran
2021-08-31 16:19 ` [Intel-wired-lan] " Richard Cochran
2021-08-31 22:09 ` Machnikowski, Maciej
2021-08-31 22:09 ` [Intel-wired-lan] " Machnikowski, Maciej
2021-09-01 2:02 ` Jakub Kicinski
2021-09-01 2:02 ` [Intel-wired-lan] " Jakub Kicinski
2021-09-01 2:56 ` Richard Cochran
2021-09-01 2:56 ` [Intel-wired-lan] " Richard Cochran
2021-09-01 1:58 ` Jakub Kicinski
2021-09-01 1:58 ` [Intel-wired-lan] " Jakub Kicinski
2021-09-01 2:55 ` Richard Cochran
2021-09-01 2:55 ` [Intel-wired-lan] " Richard Cochran
2021-08-29 8:05 ` [RFC v2 net-next 2/2] ice: add support for reading SyncE DPLL state Maciej Machnikowski
2021-08-29 8:05 ` [Intel-wired-lan] " Maciej Machnikowski
2021-08-29 11:11 ` kernel test robot
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=YSvrBvLJ3IRTn9FR@lunn.ch \
--to=andrew@lunn.ch \
--cc=abyagowi@fb.com \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=maciej.machnikowski@intel.com \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.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 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.