linux-kernel - Re: [PATCH net-next] net: phy: aquantia: Add mdix config and reporting

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: <ec453754-3474-4824-b4e3-e26603e2e1d8@lunn.ch>
Date: Fri, 18 Oct 2024 02:19:07 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Paul Davey <Paul.Davey@...iedtelesis.co.nz>
Cc: "daniel@...rotopia.org" <daniel@...rotopia.org>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH net-next] net: phy: aquantia: Add mdix config and
 reporting

> Due to this I wonder whether the mdix configuration should reject
> ETH_TP_MDI_AUTO if auto-negotiation is disabled?

How does MDIX actually work? Is there anything in 802.3?

For 10BaseT, one pair Rx, one pair Tx, i guess you can find out by
just looking at the signal. But for 4 pairs?

    Andrew

---
pw-bot: cr