netdev - Re: [PATCH 1/8] net: ethernet: ixp4xx: Standard module init

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: <CACRpkdaqm3qhHmymOTn_KqrspQzMT85y8c14cda724edUqxAWw@mail.gmail.com>
Date:   Wed, 29 May 2019 09:10:17 +0200
From:   Linus Walleij <linus.walleij@...aro.org>
To:     Andrew Lunn <andrew@...n.ch>
Cc:     netdev <netdev@...r.kernel.org>,
        "David S . Miller" <davem@...emloft.net>,
        Krzysztof Halasa <khalasa@...p.pl>
Subject: Re: [PATCH 1/8] net: ethernet: ixp4xx: Standard module init

On Fri, May 24, 2019 at 9:46 PM Andrew Lunn <andrew@...n.ch> wrote:

> What is the address space like? Could the mdio driver be pull out into
> a standalone driver?

The IXP4xx actually has a peculiar structure.

Both the MDIO and ethernet goes out through the NPE (network
processing engine) and MDIO in particular is just talking to some
mailbox on the NPE. The ethernet has dedicated registers but appear
as dependent on the NPE.

Only NPE B (second) has MDIO.

I guess I should try to make the MDIO a child of the NPE.
I try to improve the legacy code little by little.

Yours,
Linus Walleij