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  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]
Date:   Wed, 13 May 2020 20:01:40 +0200
From:   Andrew Lunn <>
To:     Oleksij Rempel <>
Cc:     Mark Rutland <>, Marek Vasut <>,
        Florian Fainelli <>,,,, Rob Herring <>,
        Pengutronix Kernel Team <>,
        David Jander <>,
        "David S. Miller" <>,
        Heiner Kallweit <>
Subject: Re: [PATCH net-next v1] net: phy: tja11xx: add cable-test support

> What would be the best place to do a test before the link is getting up?
> Can it be done in the phy core, or it should be done in the PHY driver?
> So far, no action except of logging these errors is needed. 

You could do it in the config_aneg callback.

A kernel log entry is not very easy to use. You might want to see how
easy it is to send a cable test result to userspace. Anything which is
interested in this information can then listen for it. All the needed
code is there, you will just need to rearrange it a bit.


Powered by blists - more mailing lists