netdev - Re: net: macb: fail when there's no PHY

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: <20201203040025.GB2333853@lunn.ch>
Date:   Thu, 3 Dec 2020 05:00:25 +0100
From:   Andrew Lunn <andrew@...n.ch>
To:     Grant Edwards <grant.b.edwards@...il.com>
Cc:     netdev@...r.kernel.org
Subject: Re: net: macb: fail when there's no PHY

On Thu, Dec 03, 2020 at 03:03:30AM -0000, Grant Edwards wrote:
> On 2020-12-02, Andrew Lunn <andrew@...n.ch> wrote:
> 
> >>> So it will access the MDIO bus of the PHY that is attached to the
> >>> MAC.
> >>
> >> If that's the case, wouldn't the ioctl() calls "just work" even when
> >> only the fixed-phy mdio bus and fake PHY are declared in the device
> >> tree?
> >
> > The fixed-link PHY is connected to the MAC. So the IOCTL calls will be
> > made to the fixed-link fake MDIO bus.
> 
> Ah! When you said "the PHY that is attached to the MAC" above, I
> thought you meant electrically attached to the MAC via the mdio bus.

Ah, sorry. phylib and phylink have API calls to connect a MAC and a
PHY. phylink_connect_phy(), phy_connect(). I was thinking in those
terms. But if you don't know you way around this subsystem, the
misunderstanding is understanding.

	 Andrew