[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <edad81cb-fb30-fede-1629-b32295979e95@gmail.com>
Date: Wed, 20 Jun 2018 10:58:26 -0700
From: Florian Fainelli <f.fainelli@...il.com>
To: Ilias Apalodimas <ilias.apalodimas@...aro.org>,
Ivan Vecera <ivecera@...hat.com>
Cc: Andrew Lunn <andrew@...n.ch>, netdev@...r.kernel.org,
grygorii.strashko@...com, ivan.khoronzhuk@...aro.org,
nsekhar@...com, jiri@...nulli.us, francois.ozog@...aro.org,
yogeshs@...com, spatton@...com, Jose.Abreu@...opsys.com
Subject: Re: [RFC v2, net-next, PATCH 4/4] net/cpsw_switchdev: add switchdev
mode of operation on cpsw driver
On 06/20/2018 10:51 AM, Ilias Apalodimas wrote:
> Hello Ivan,
> On Wed, Jun 20, 2018 at 02:56:48PM +0200, Ivan Vecera wrote:
>> On 18.6.2018 22:19, Ilias Apalodimas wrote:
>>> Jiri proposed using devlink, which makes sense, but i am not sure it's
>>> applicable on this patchset. This will change the driver completely and will
>>> totally break backwards compatibility.
>>
>> Another good reason for a new driver.
>>
>> I.
> This is actually conflicting at least to my understanding. Jiri proposed using
> devlink was used as an alternative method to enable a new mode instead of
> adding it on a .config option. A new driver wouldn't have a need for that right?
Correct, with a new driver would likely behave correctly upon being
probed such that you could have your switch ports act as normal network
devices from which you could run IP-config and do NFS boot.
--
Florian
Powered by blists - more mailing lists