From: Tobias Waldekranz <tobias@waldekranz.com>
To: Russell King - ARM Linux admin <linux@armlinux.org.uk>
Cc: Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
netdev@vger.kernel.org, Antoine Tenart <atenart@kernel.org>,
Vivien Didelot <vivien.didelot@gmail.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Maxime Chevallier <maxime.chevallier@bootlin.com>,
"David S. Miller" <davem@davemloft.net>,
linux-arm-kernel@lists.infradead.org,
Heiner Kallweit <hkallweit1@gmail.com>
Subject: Re: net: phy: Dealing with 88e1543 dual-port mode
Date: Fri, 20 Nov 2020 10:12:43 +0100 [thread overview]
Message-ID: <875z609yt0.fsf@waldekranz.com> (raw)
In-Reply-To: <20201120004048.GO1551@shell.armlinux.org.uk>
On Fri, Nov 20, 2020 at 00:40, Russell King - ARM Linux admin <linux@armlinux.org.uk> wrote:
> I think you're advocating calling the fiber interface "SGMII", which
> would be totally wrong.
>
> SGMII is a Cisco modification of 802.3 1000base-X to allow 10M and 100M
> speeds to be used over a single serdes lane in each direction.
>
> 1000base-X is what you run over a fiber link. This is not SGMII. Using
> "SGMII" for 1000base-X is incorrect, but a common abuse of the term in
> industry. Abusing a term does not make it correct, especially when it
> comes to defining further standards.
>
> (This is one of my pet peaves, sorry.)
Nomenclature is very important, no excuse necessary.
You are right that SGMII is not the term I am looking for, but I am not
sure 1000base-X is either. I am looking for a word that describes the
serial interface that can run in either 1000base-X or 100base-FX mode
(and possibly other ancient/proprietary modes). Maybe just "serdes"?
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Tobias Waldekranz <tobias@waldekranz.com>
To: Russell King - ARM Linux admin <linux@armlinux.org.uk>
Cc: Maxime Chevallier <maxime.chevallier@bootlin.com>,
Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Antoine Tenart <atenart@kernel.org>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: net: phy: Dealing with 88e1543 dual-port mode
Date: Fri, 20 Nov 2020 10:12:43 +0100 [thread overview]
Message-ID: <875z609yt0.fsf@waldekranz.com> (raw)
In-Reply-To: <20201120004048.GO1551@shell.armlinux.org.uk>
On Fri, Nov 20, 2020 at 00:40, Russell King - ARM Linux admin <linux@armlinux.org.uk> wrote:
> I think you're advocating calling the fiber interface "SGMII", which
> would be totally wrong.
>
> SGMII is a Cisco modification of 802.3 1000base-X to allow 10M and 100M
> speeds to be used over a single serdes lane in each direction.
>
> 1000base-X is what you run over a fiber link. This is not SGMII. Using
> "SGMII" for 1000base-X is incorrect, but a common abuse of the term in
> industry. Abusing a term does not make it correct, especially when it
> comes to defining further standards.
>
> (This is one of my pet peaves, sorry.)
Nomenclature is very important, no excuse necessary.
You are right that SGMII is not the term I am looking for, but I am not
sure 1000base-X is either. I am looking for a word that describes the
serial interface that can run in either 1000base-X or 100base-FX mode
(and possibly other ancient/proprietary modes). Maybe just "serdes"?
next prev parent reply other threads:[~2020-11-20 9:13 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 14:22 net: phy: Dealing with 88e1543 dual-port mode Maxime Chevallier
2020-11-19 14:22 ` Maxime Chevallier
2020-11-19 14:55 ` Russell King - ARM Linux admin
2020-11-19 14:55 ` Russell King - ARM Linux admin
2020-11-19 15:19 ` Russell King - ARM Linux admin
2020-11-19 15:19 ` Russell King - ARM Linux admin
2020-11-19 15:24 ` Maxime Chevallier
2020-11-19 15:24 ` Maxime Chevallier
2020-11-19 22:43 ` Tobias Waldekranz
2020-11-19 22:43 ` Tobias Waldekranz
2020-11-19 23:16 ` Russell King - ARM Linux admin
2020-11-19 23:16 ` Russell King - ARM Linux admin
2020-11-20 0:11 ` Tobias Waldekranz
2020-11-20 0:11 ` Tobias Waldekranz
2020-11-20 0:40 ` Russell King - ARM Linux admin
2020-11-20 0:40 ` Russell King - ARM Linux admin
2020-11-20 9:12 ` Tobias Waldekranz [this message]
2020-11-20 9:12 ` Tobias Waldekranz
2020-11-20 9:36 ` Maxime Chevallier
2020-11-20 9:36 ` Maxime Chevallier
2020-11-20 10:25 ` Russell King - ARM Linux admin
2020-11-20 10:25 ` Russell King - ARM Linux admin
2020-11-20 10:59 ` Tobias Waldekranz
2020-11-20 10:59 ` Tobias Waldekranz
2020-11-20 13:55 ` Andrew Lunn
2020-11-20 13:55 ` Andrew Lunn
2020-11-20 14:18 ` Maxime Chevallier
2020-11-20 14:18 ` Maxime Chevallier
2020-11-20 0:00 ` Andrew Lunn
2020-11-20 0:00 ` Andrew Lunn
2020-11-20 9:05 ` Tobias Waldekranz
2020-11-20 9:05 ` Tobias Waldekranz
2020-11-19 15:16 ` Andrew Lunn
2020-11-19 15:16 ` Andrew Lunn
2020-11-19 15:45 ` Maxime Chevallier
2020-11-19 15:45 ` Maxime Chevallier
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=875z609yt0.fsf@waldekranz.com \
--to=tobias@waldekranz.com \
--cc=andrew@lunn.ch \
--cc=atenart@kernel.org \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=vivien.didelot@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.