netdev - Re: [PATCH v2 net-next 0/2] Convert ocelot to phylink

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Mon, 16 Aug 2021 15:29:07 +0200
From:   Alexandre Belloni <alexandre.belloni@...tlin.com>
To:     Vladimir Oltean <vladimir.oltean@....com>
Cc:     netdev@...r.kernel.org, Jakub Kicinski <kuba@...nel.org>,
        "David S. Miller" <davem@...emloft.net>,
        Russell King <linux@...linux.org.uk>,
        Horatiu Vultur <horatiu.vultur@...rochip.com>,
        Colin Foster <colin.foster@...advantage.com>,
        Florian Fainelli <f.fainelli@...il.com>,
        Andrew Lunn <andrew@...n.ch>,
        Vivien Didelot <vivien.didelot@...il.com>,
        Claudiu Manoil <claudiu.manoil@....com>,
        UNGLinuxDriver@...rochip.com
Subject: Re: [PATCH v2 net-next 0/2] Convert ocelot to phylink

Hi,

On 15/08/2021 04:47:46+0300, Vladimir Oltean wrote:
> The ocelot switchdev and felix dsa drivers are interesting because they
> target the same class of hardware switches but used in different modes.
> 
> Colin has an interesting use case where he wants to use a hardware
> switch supported by the ocelot switchdev driver with the felix dsa
> driver.
> 
> So far, the existing hardware revisions were similar between the ocelot
> and felix drivers, but not completely identical. With identical hardware,
> it is absurd that the felix driver uses phylink while the ocelot driver
> uses phylib - this should not be one of the differences between the
> switchdev and dsa driver, and we could eliminate it.
> 
> Colin will need the common phylink support in ocelot and felix when
> adding a phylink_pcs driver for the PCS1G block inside VSC7514, which
> will make the felix driver work with either the NXP or the Microchip PCS.
> 
> As usual, Alex, Horatiu, sorry for bugging you, but it would be
> appreciated if you could give this a quick run on actual VSC7514
> hardware (which I don't have) to make sure I'm not introducing any
> breakage.
> 

No worries, if there is any breakage, we'll fix it up.


-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com