From: Andrew Lunn <andrew@lunn.ch>
To: Shaohui Xie <shaohui.xie@nxp.com>
Cc: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
"shh.xie@gmail.com" <shh.xie@gmail.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"davem@davemloft.net" <davem@davemloft.net>,
Shaohui Xie <Shaohui.Xie@freescale.com>
Subject: Re: [PATCH 1/3][v2] net: phy: introduce 1000BASE-KX and 10GBASE-KR
Date: Mon, 18 Jan 2016 16:15:00 +0100 [thread overview]
Message-ID: <20160118151500.GD923@lunn.ch> (raw)
In-Reply-To: <VI1PR04MB1664AB0E483F01F1641059FFE8C00@VI1PR04MB1664.eurprd04.prod.outlook.com>
> [S.H] the fsl backplane, e.g. 10GBASE-KR, needs software to handle link training,
> It's to train link partner, and trained by link partner parallel.
>
> But if media type is not copper, e.g. optical module, we won't need this.
So what we actually need to know is copper vs fibre?
Andrew
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Lunn <andrew-g2DYL2Zd6BY@public.gmane.org>
To: Shaohui Xie <shaohui.xie-3arQi8VN3Tc@public.gmane.org>
Cc: Sebastian Hesselbarth
<sebastian.hesselbarth-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Florian Fainelli
<f.fainelli-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
"shh.xie-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org"
<shh.xie-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linuxppc-dev-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org"
<linuxppc-dev-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>,
"davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org"
<davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>,
Shaohui Xie <Shaohui.Xie-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Subject: Re: [PATCH 1/3][v2] net: phy: introduce 1000BASE-KX and 10GBASE-KR
Date: Mon, 18 Jan 2016 16:15:00 +0100 [thread overview]
Message-ID: <20160118151500.GD923@lunn.ch> (raw)
In-Reply-To: <VI1PR04MB1664AB0E483F01F1641059FFE8C00-mr6QIVyDiCHTAO9RNConP89NdZoXdze2vxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
> [S.H] the fsl backplane, e.g. 10GBASE-KR, needs software to handle link training,
> It's to train link partner, and trained by link partner parallel.
>
> But if media type is not copper, e.g. optical module, we won't need this.
So what we actually need to know is copper vs fibre?
Andrew
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-01-18 15:15 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 8:23 [PATCH 1/3][v2] net: phy: introduce 1000BASE-KX and 10GBASE-KR shh.xie
2016-01-14 8:23 ` shh.xie
2016-01-14 16:44 ` Andrew Lunn
2016-01-15 4:01 ` Shaohui Xie
2016-01-15 4:01 ` Shaohui Xie
2016-01-15 22:57 ` Sebastian Hesselbarth
2016-01-16 2:59 ` Florian Fainelli
2016-01-16 2:59 ` Florian Fainelli
2016-01-18 7:23 ` Shaohui Xie
2016-01-18 7:23 ` Shaohui Xie
2016-01-18 8:05 ` Sebastian Hesselbarth
2016-01-18 8:50 ` Shaohui Xie
2016-01-18 8:50 ` Shaohui Xie
2016-01-18 15:15 ` Andrew Lunn [this message]
2016-01-18 15:15 ` Andrew Lunn
2016-01-19 5:00 ` Shaohui Xie
2016-01-19 5:00 ` Shaohui Xie
2016-01-21 21:12 ` Andrew Lunn
2016-01-21 21:12 ` Andrew Lunn
2016-01-22 8:15 ` Shaohui Xie
2016-01-22 8:15 ` Shaohui Xie
2016-01-22 9:26 ` Sebastian Hesselbarth
2016-01-22 9:26 ` Sebastian Hesselbarth
2016-01-22 10:05 ` Shaohui Xie
2016-01-22 10:05 ` Shaohui Xie
2016-01-22 14:09 ` Shaohui Xie
2016-01-22 14:09 ` Shaohui Xie
2016-01-22 14:38 ` Andrew Lunn
2016-01-22 14:38 ` Andrew Lunn
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=20160118151500.GD923@lunn.ch \
--to=andrew@lunn.ch \
--cc=Shaohui.Xie@freescale.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=shaohui.xie@nxp.com \
--cc=shh.xie@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.