From: Andrew Lunn <andrew@lunn.ch>
To: Bhaskar Upadhaya <bhaskar.upadhaya@nxp.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/1] phy: Add 2.5G SGMII interface mode
Date: Thu, 30 Nov 2017 18:41:27 +0100 [thread overview]
Message-ID: <20171130174127.GA28828@lunn.ch> (raw)
In-Reply-To: <AM3PR04MB4494050122E413E2445BD348C380@AM3PR04MB449.eurprd04.prod.outlook.com>
> [bhaskar] 2.5G in general needs to operate with auto negotiation in
> disabled mode. Its 2.5G requirement and not specific to our system.
> My understanding is that one of the main differences between SGMII and 1000BASE-X is the negotiation.
> [Bhaskar] which of SGMII and 1000BASE-X support negotiation ?
SGMII supports passing auto-negotiation results from the PHY to the
MAC. 1000BASE-X does not.
SGMII supports the PHY running at 10, 100, and 1000 Mbps. But to
support this, the MAC needs to replicate the bits 100, or 10 times
when the PHY is running in 10 or 100Mbps mode.
So with your 2.5G SGMII, you need to replicate the bits 250, 25, or
2.5 times if they PHY is running at lower speeds. This last one is
interesting.
Andrew
next prev parent reply other threads:[~2017-11-30 17:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 4:30 [PATCH 1/1] phy: Add 2.5G SGMII interface mode Bhaskar Upadhaya
2017-11-30 15:50 ` Andrew Lunn
2017-11-30 17:16 ` Bhaskar Upadhaya
2017-11-30 17:34 ` David Miller
2017-11-30 17:41 ` Andrew Lunn [this message]
2017-11-30 18:15 ` Russell King - ARM Linux
2017-11-30 18:26 ` Andrew Lunn
2017-11-30 18:53 ` Russell King - ARM Linux
2017-12-01 18:40 ` Bhaskar Upadhaya
2017-12-01 18:44 ` Florian Fainelli
2017-12-01 19:12 ` Andrew Lunn
2017-11-30 17:33 ` Russell King - ARM Linux
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=20171130174127.GA28828@lunn.ch \
--to=andrew@lunn.ch \
--cc=bhaskar.upadhaya@nxp.com \
--cc=davem@davemloft.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=netdev@vger.kernel.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).