netdev - Re: GPY215 PHY interrupt issue

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: <Y4jOMocoLneO8xoD@lunn.ch>
Date:   Thu, 1 Dec 2022 16:54:26 +0100
From:   Andrew Lunn <andrew@...n.ch>
To:     Michael Walle <michael@...le.cc>
Cc:     Heiner Kallweit <hkallweit1@...il.com>,
        Russell King <linux@...linux.org.uk>,
        Horatiu Vultur <horatiu.vultur@...rochip.com>,
        netdev@...r.kernel.org, Xu Liang <lxu@...linear.com>
Subject: Re: GPY215 PHY interrupt issue

> So, switching the line to GPIO input doesn't help here, which also
> means the interrupt line will be stuck the whole time.

Sounds like they totally messed up the design somehow.

Since we are into horrible hack territory.....

I assume you are using the Link state change interrupt? LSTC?

Maybe instead use Link speed change and Duplex mode change? And
disallow 10/Half. Some PHYs change to 10/Half when they loose
link. They might be enough to tell you the link has changed. You can
then read the BMSR to find out what actually happened.

This is assuming that interrupts in general are not FUBAR.

     Andrew