From: Andrew Lunn <andrew@lunn.ch>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: David Miller <davem@davemloft.net>,
o.rempel@pengutronix.de, f.fainelli@gmail.com,
hkallweit1@gmail.com, kuba@kernel.org, corbet@lwn.net,
mkubecek@suse.cz, linville@tuxdriver.com, david@protonic.nl,
kernel@pengutronix.de, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, linux@armlinux.org.uk,
mkl@pengutronix.de, marex@denx.de, christian.herber@nxp.com,
amitc@mellanox.com, petrm@mellanox.com
Subject: Re: [PATCH ethtool v1] netlink: add master/slave configuration support
Date: Tue, 9 Jun 2020 20:30:34 +0200 [thread overview]
Message-ID: <20200609183034.GC1056844@lunn.ch> (raw)
In-Reply-To: <20200609101935.5716b3bd@hermes.lan>
Hi Stephen
> A common example is that master/slave is unclear and would be clearer
> as primary/secondary or active/backup or controller/worker.
802.3, cause 32.1.2, 2015 version:
A 100BASE-T2 PHY can be configured either as a master PHY or as a
slave PHY. The master-slave relationship between two stations
sharing a link segment is established during Auto-Negotiation (see
Clause 28, 32.5, Annex 28C, and 32.5.2). The master PHY uses an
external clock to determine the timing of transmitter and receiver
operations. The slave PHY recovers the clock from the received
signal and uses it to determine the timing of transmitter
operations, i.e., it performs loop timing, as illustrated in Figure
32–2.
In this case, i would say master/slave is very clearly defined.
Given these definitions, would you like to propose alternatives?
Do you have any insights has to how the IEEE 802.3 standard will be
changed?
Andrew
next prev parent reply other threads:[~2020-06-09 18:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-26 9:10 [PATCH ethtool v1] netlink: add master/slave configuration support Oleksij Rempel
2020-05-26 12:41 ` Michal Kubecek
2020-05-27 10:26 ` Oleksij Rempel
2020-06-07 22:30 ` Stephen Hemminger
2020-06-07 23:45 ` David Miller
2020-06-09 17:19 ` Stephen Hemminger
2020-06-09 18:30 ` Andrew Lunn [this message]
2020-06-09 18:36 ` David Miller
2020-06-09 19:29 ` Kees Cook
2020-06-09 19:34 ` David Miller
2020-06-09 19:49 ` Kees Cook
2020-06-09 20:05 ` David Miller
2020-06-09 20:29 ` Kees Cook
2020-06-09 20:53 ` Michal Kubecek
2020-06-09 21:34 ` Kees Cook
2020-06-09 19:30 ` Williams, Dan J
2020-06-09 19:38 ` David Miller
2020-06-09 21:48 ` Dan Williams
2020-06-10 6:07 ` Oleksij Rempel
2020-06-09 18:46 ` Edward Cree
2020-06-09 20:31 ` Michal Kubecek
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=20200609183034.GC1056844@lunn.ch \
--to=andrew@lunn.ch \
--cc=amitc@mellanox.com \
--cc=christian.herber@nxp.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=david@protonic.nl \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=linville@tuxdriver.com \
--cc=marex@denx.de \
--cc=mkl@pengutronix.de \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=petrm@mellanox.com \
--cc=stephen@networkplumber.org \
/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).