linux-kernel - Re: signal quality and cable diagnostic

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: <20200511143337.GC413878@lunn.ch>
Date:   Mon, 11 May 2020 16:33:37 +0200
From:   Andrew Lunn <andrew@...n.ch>
To:     Oleksij Rempel <o.rempel@...gutronix.de>
Cc:     "David S. Miller" <davem@...emloft.net>,
        Florian Fainelli <f.fainelli@...il.com>,
        Heiner Kallweit <hkallweit1@...il.com>,
        Jakub Kicinski <kuba@...nel.org>,
        Jonathan Corbet <corbet@....net>,
        Michal Kubecek <mkubecek@...e.cz>,
        David Jander <david@...tonic.nl>, kernel@...gutronix.de,
        linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
        Russell King <linux@...linux.org.uk>, mkl@...gutronix.de,
        Marek Vasut <marex@...x.de>,
        Christian Herber <christian.herber@....com>
Subject: Re: signal quality and cable diagnostic

On Mon, May 11, 2020 at 04:13:10PM +0200, Oleksij Rempel wrote:
> Hi Andrew,
> 
> First of all, great work! As your cable diagnostic patches are in
> net-next now and can be used as base for the follow-up discussion.
> 
> Do you already have ethtool patches somewhere? :=) Can you please give a
> link for testing?

Hi Oleksij

It was mentioned in the cover note

https://github.com/lunn/ethtool/tree/feature/cable-test-v4

> 
> I continue to work on TJA11xx PHY and need to export some additional
> cable diagnostic/link stability information: Signal Quality Index (SQI).

Is this something you want to continually make available, or just as
part of cable diagnostics. Additional nested attributes can be added
to the cable test results structure, and the user space code just
dumps whatever it finds. So it should be easy to have something like:

Pair A: OK
Pair A: Signal Quality Index class D

Are the classes part of the Open Alliance specification? Ideally we
want to report something standardized, not something proprietary to
NXP.

	Andrew