[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180507.231841.206393937472731641.davem@davemloft.net>
Date: Mon, 07 May 2018 23:18:41 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: antoine.tenart@...tlin.com
Cc: kishon@...com, linux@...linux.org.uk, gregory.clement@...tlin.com,
andrew@...n.ch, jason@...edaemon.net,
sebastian.hesselbarth@...il.com, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, thomas.petazzoni@...tlin.com,
maxime.chevallier@...tlin.com, miquel.raynal@...tlin.com,
nadavh@...vell.com, stefanc@...vell.com, ymarkman@...vell.com,
mw@...ihalf.com, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH net-next v2 00/13] net: mvpp2: phylink conversion
From: Antoine Tenart <antoine.tenart@...tlin.com>
Date: Fri, 4 May 2018 15:56:30 +0200
> Also as the SFP cages on both DB boards can be considered as non-wired,
> the SFP code was reworked to really support when some pins of the SFP
> cage aren't described in the device tree. Also a warning was added when
> no Tx disable pin is available. (Patches 1-3).
I guess there is still discussion about whether fixed-link should be
used for this instead of SFP.
Powered by blists - more mailing lists