linux-kernel - Re: [PATCH net-next 0/3] net: phy: dp83867: add cable diag support

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: <a0690702-9781-47c9-b7a7-06ab52707c40@lunn.ch>
Date: Thu, 13 Jun 2024 19:26:53 +0200
From: Andrew Lunn <andrew@...n.ch>
To: João Rodrigues <jrodrigues@...met.com>
Cc: Heiner Kallweit <hkallweit1@...il.com>,
	Russell King <linux@...linux.org.uk>,
	"David S. Miller" <davem@...emloft.net>,
	Eric Dumazet <edumazet@...gle.com>,
	Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
	"open list:ETHERNET PHY LIBRARY" <netdev@...r.kernel.org>,
	open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH net-next 0/3] net: phy: dp83867: add cable diag support

> The TDR reporting in PD83867 is divided into segments (from which a
> cable length can be extracted). Because the reported lengths do not come
> in regular intervals, when doing cable-test-tdr from ethtool, the value
> of the reflection is reported, but not the length at which occurred
> (even though the PHY reports it).

So what does the output look like?

   Andrew