netdev - Re: [RFC PATCH v2 net-next 0/8] Add support for VSC7511-7514 chips over SPI

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: <20210710194755.xmt5jnaanh45dmlm@skbuf>
Date:   Sat, 10 Jul 2021 22:47:55 +0300
From:   Vladimir Oltean <olteanv@...il.com>
To:     Colin Foster <colin.foster@...advantage.com>
Cc:     andrew@...n.ch, vivien.didelot@...il.com, f.fainelli@...il.com,
        davem@...emloft.net, kuba@...nel.org, robh+dt@...nel.org,
        claudiu.manoil@....com, alexandre.belloni@...tlin.com,
        UNGLinuxDriver@...rochip.com, linux@...linux.org.uk,
        netdev@...r.kernel.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH v2 net-next 0/8] Add support for VSC7511-7514 chips
 over SPI

On Sat, Jul 10, 2021 at 12:25:54PM -0700, Colin Foster wrote:
> 1. The first probe of the internal MDIO bus fails. I suspect this is related to
> power supplies / grounding issues that would not appear on standard hardware.

Where and with what error code does it fail exactly? I don't understand
the concept of "the first probe"? You mean that there is an
-EPROBE_DEFER and it tries again immediately afterwards? Or you need to
unbind and rebind the driver to the device, or what?

> 2. Communication to the CPU bus doesn't seem to function properly. I suspect
> this is due to the fact that ocelot / felix assumes it is using the built-in CPU
> / NPI port for forwarding, though I am not positive.

What is the CPU bus and what doesn't function properly about it?

> Nonetheless, these two issues likely won't require a large architecture change,
> and perhaps those who know much more about the ocelot chips than I could chime
> in.

I guess you don't know if that's the case or not until you know what the
problem is...