netdev - Re: [PATCH 4/4] RFC: net: dsa: realtek-smi: Add Realtek SMI driver

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: <CACRpkda5encW6gcpcKh_0Je17Z=fkGwixLur1iGJ+Dc1+kHRsw@mail.gmail.com>
Date:   Mon, 6 Nov 2017 09:25:30 +0100
From:   Linus Walleij <linus.walleij@...aro.org>
To:     Andrew Lunn <andrew@...n.ch>
Cc:     Vivien Didelot <vivien.didelot@...oirfairelinux.com>,
        Florian Fainelli <f.fainelli@...il.com>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        Antti Seppälä <a.seppala@...il.com>,
        Roman Yeryomin <roman@...em.lv>,
        Colin Leitner <colin.leitner@...glemail.com>,
        Gabor Juhos <juhosg@...nwrt.org>
Subject: Re: [PATCH 4/4] RFC: net: dsa: realtek-smi: Add Realtek SMI driver

On Mon, Nov 6, 2017 at 12:59 AM, Andrew Lunn <andrew@...n.ch> wrote:

> I'm wondering if this should be modelled as a normal MDIO bus? Put the
> driver as drivers/net/mdio-realtek.c?

I looked into it but couldn't find a good fit.

The MDIO bus makes much more sense since more than one vendor
is using it so it's not a one-off. This Realtek is a RTK-specific thing plus
I don't think they are doing it anymore.

It's very confusing since they are using the MDIO electrical specification
and signal names but a totally different custom SMI wire protocol on top.

Yours,
Linus Walleij