netdev - Re: [PATCH 7/8] net: ethernet: ixp4xx: Add DT bindings

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:   Wed, 29 May 2019 09:13:58 +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 7/8] net: ethernet: ixp4xx: Add DT bindings

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

> > +description: |
> > +  The Intel IXP4xx ethernet makes use of the IXP4xx NPE (Network
> > +  Processing Engine) and the IXP4xx Queue Mangager to process
> > +  the ethernet frames. It can optionally contain an MDIO bus to
> > +  talk to PHYs.
>
> Hi Linus
>
> You mention MDIO and PHYs, but the code is not there yet. When you do
> add the needed code, it is a good idea to place the PHY nodes inside a
> container node:

Actually I think the MDIO needs to go into the NPE (network processing
engine) node, that is where it actually is implemented.

It coincides with having to rewrite the code in Linux to split that off into
its own device as you pointed out on patch 1, hm a bit of work ahead
here...

Yours,
Linus Walleij