netdev - Re: [PATCH v2 net-next 00/13] New DSA driver for VSC9953 Seville switch

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <20200530.180351.1434687967128631713.davem@davemloft.net>
Date:   Sat, 30 May 2020 18:03:51 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     olteanv@...il.com
Cc:     netdev@...r.kernel.org, andrew@...n.ch, vivien.didelot@...il.com,
        f.fainelli@...il.com, antoine.tenart@...tlin.com,
        alexandre.belloni@...tlin.com, UNGLinuxDriver@...rochip.com,
        alexandru.marginean@....com, claudiu.manoil@....com,
        madalin.bucur@....nxp.com, radu-andrei.bulie@....com,
        fido_max@...ox.ru, broonie@...nel.org
Subject: Re: [PATCH v2 net-next 00/13] New DSA driver for VSC9953 Seville
 switch

From: Vladimir Oltean <olteanv@...il.com>
Date: Sat, 30 May 2020 14:51:29 +0300

> From: Vladimir Oltean <vladimir.oltean@....com>
> 
> Looking at the Felix and Ocelot drivers, Maxim asked if it would be
> possible to use them as a base for a new driver for the Seville switch
> inside NXP T1040. Turns out, it is! The result is that the mscc_felix
> driver was extended to probe on Seville.
> 
> The biggest challenge seems to be getting register read/write API
> generic enough to cover such wild bitfield variations between hardware
> generations.
> 
> There is a trivial dependency patch on the regmap core which is in Mark
> Brown's for-next tree:
> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git/commit/?h=for-next&id=8baebfc2aca26e3fa67ab28343671b82be42b22c
> I didn't know what to do with it, so I just added it here as well, as
> 01/13, so that net-next builds wouldn't break.

Looks good, series applied, thanks.