er.kernel.org; thomas.petazz...@bootlin.com;
> > maxime.chevall...@bootlin.com; miquel.ray...@bootlin.com; Nadav Haklai
> > <nad...@marvell.com>; Yan Markman <ymark...@marvell.com>;
> > m...@semihalf.com; linux-arm-ker...@lists.infradead.org
> > Sub
miquel.ray...@bootlin.com; Nadav Haklai
> > ; Yan Markman ;
> > m...@semihalf.com; linux-arm-ker...@lists.infradead.org
> > Subject: Re: [EXT] Re: [PATCH net-next 02/10] net: phy: phylink: allow 10GKR
> > interface to use in-band negotiation
> >
> > > > If they don't
> This would definitively work for SFP connectors with a PHY, but would
> that work when using direct attached cable?
Then you need to know what is on the other end of the cable? A switch?
A PHY? and SFP module?
Andrew
> This would definitively work for SFP connectors with a PHY, but would
> that work when using direct attached cable?
Then you need to know what is on the other end of the cable? A switch?
A PHY? and SFP module?
Andrew
> phylink pool SFP loss signal to determine link up/down?
Yes, the SFP driver will act on a GPIO for link up/down, and a GPIO
for module prescience. When it detects an SFP module hotplugged, it
reads the EEPROM to find out what sort of module it is, and what mode
should be used between the MAC
> phylink pool SFP loss signal to determine link up/down?
Yes, the SFP driver will act on a GPIO for link up/down, and a GPIO
for module prescience. When it detects an SFP module hotplugged, it
reads the EEPROM to find out what sort of module it is, and what mode
should be used between the MAC
aklai
> <nad...@marvell.com>; Yan Markman <ymark...@marvell.com>;
> m...@semihalf.com; linux-arm-ker...@lists.infradead.org
> Subject: Re: [EXT] Re: [PATCH net-next 02/10] net: phy: phylink: allow 10GKR
> interface to use in-band negotiation
>
> > > If the
ct: Re: [EXT] Re: [PATCH net-next 02/10] net: phy: phylink: allow 10GKR
> interface to use in-band negotiation
>
> > > If they don't have PHYs, how are the connected to the outside world?
> > >
> > >Andrew
> >
> > By external SFP or direct attached c
On Mon, Mar 19, 2018 at 02:08:23PM +0100, Andrew Lunn wrote:
> > > If they don't have PHYs, how are the connected to the outside world?
> >
> > By external SFP or direct attached cable.
>
> Maybe i'm missing something, but don't you just need to add an SFP
> device in the device tree. The SFP
On Mon, Mar 19, 2018 at 02:08:23PM +0100, Andrew Lunn wrote:
> > > If they don't have PHYs, how are the connected to the outside world?
> >
> > By external SFP or direct attached cable.
>
> Maybe i'm missing something, but don't you just need to add an SFP
> device in the device tree. The SFP
> > If they don't have PHYs, how are the connected to the outside world?
> >
> >Andrew
>
> By external SFP or direct attached cable.
Maybe i'm missing something, but don't you just need to add an SFP
device in the device tree. The SFP code and PHYLINK will work
together, query what the SFP
> > If they don't have PHYs, how are the connected to the outside world?
> >
> >Andrew
>
> By external SFP or direct attached cable.
Maybe i'm missing something, but don't you just need to add an SFP
device in the device tree. The SFP code and PHYLINK will work
together, query what the SFP
.org; linux-kernel@vger.kernel.org;
> thomas.petazz...@bootlin.com; maxime.chevall...@bootlin.com;
> miquel.ray...@bootlin.com; Nadav Haklai <nad...@marvell.com>; Yan Markman
> <ymark...@marvell.com>; m...@semihalf.com;
> linux-arm-ker...@lists.infradead.org
> Subject: R
@bootlin.com; maxime.chevall...@bootlin.com;
> miquel.ray...@bootlin.com; Nadav Haklai ; Yan Markman
> ; m...@semihalf.com;
> linux-arm-ker...@lists.infradead.org
> Subject: RE: [EXT] Re: [PATCH net-next 02/10] net: phy: phylink: allow 10GKR
> interface to use in-band negotiation
>
; Chulski <stef...@marvell.com>; Yan Markman <ymark...@marvell.com>;
> m...@semihalf.com; linux-arm-ker...@lists.infradead.org
> Subject: [EXT] Re: [PATCH net-next 02/10] net: phy: phylink: allow 10GKR
> interface to use in-band negotiation
>
> External Email
>
> --
t: [EXT] Re: [PATCH net-next 02/10] net: phy: phylink: allow 10GKR
> interface to use in-band negotiation
>
> External Email
>
> --
> Hi Antoine
>
> > You guessed right, that's exactly my use ca
ai <nad...@marvell.com>; Yan Markman
<ymark...@marvell.com>; m...@semihalf.com; linux-arm-ker...@lists.infradead.org
Subject: RE: [EXT] Re: [PATCH net-next 02/10] net: phy: phylink: allow 10GKR
interface to use in-band negotiation
> > > There is no inband negotiation li
radead.org
Subject: RE: [EXT] Re: [PATCH net-next 02/10] net: phy: phylink: allow 10GKR
interface to use in-band negotiation
> > > There is no inband negotiation like there is with 802.3z or SGMII,
> > > so this makes no sense.
> >
> > Oh, that's what I feared.
> > > There is no inband negotiation like there is with 802.3z or SGMII,
> > > so this makes no sense.
> >
> > Oh, that's what I feared. I read some docs but probably will need more
> > :)
> >
> > Anyway, the reason to use in-band negotiation was also to avoid using
> > fixed-link. It would work
> > > There is no inband negotiation like there is with 802.3z or SGMII,
> > > so this makes no sense.
> >
> > Oh, that's what I feared. I read some docs but probably will need more
> > :)
> >
> > Anyway, the reason to use in-band negotiation was also to avoid using
> > fixed-link. It would work
20 matches
Mail list logo
