Re: [PATCH net-next v5 0/5] ethtool: introduce PHY MSE diagnostics UAPI and drivers

[PATCH net-next v5 0/5] ethtool: introduce PHY MSE diagnostics UAPI and drivers · Oleksij Rempel <o.rempel@pengutronix.de> · 2025-09-08
[PATCH net-next v5 5/5] net: phy: dp83td510: add MSE interface support for 10BASE-T1L · Oleksij Rempel <o.rempel@pengutronix.de> · 2025-09-08
[PATCH net-next v5 4/5] net: phy: micrel: add MSE interface support for KSZ9477 family · Oleksij Rempel <o.rempel@pengutronix.de> · 2025-09-08
[PATCH net-next v5 3/5] ethtool: netlink: add lightweight MSE reporting to LINKSTATE_GET · Oleksij Rempel <o.rempel@pengutronix.de> · 2025-09-08
[PATCH net-next v5 1/5] ethtool: introduce core UAPI and driver API for PHY MSE diagnostics · Oleksij Rempel <o.rempel@pengutronix.de> · 2025-09-08
Re: [PATCH net-next v5 1/5] ethtool: introduce core UAPI and driver API for PHY MSE diagnostics · Jakub Kicinski <kuba@kernel.org> · 2025-09-12
Re: [PATCH net-next v5 1/5] ethtool: introduce core UAPI and driver API for PHY MSE diagnostics · Oleksij Rempel <o.rempel@pengutronix.de> · 2025-09-12
Re: [PATCH net-next v5 1/5] ethtool: introduce core UAPI and driver API for PHY MSE diagnostics · Jakub Kicinski <kuba@kernel.org> · 2025-09-12
[PATCH net-next v5 2/5] ethtool: netlink: add ETHTOOL_MSG_MSE_GET and wire up PHY MSE access · Oleksij Rempel <o.rempel@pengutronix.de> · 2025-09-08
Re: [PATCH net-next v5 2/5] ethtool: netlink: add ETHTOOL_MSG_MSE_GET and wire up PHY MSE access · Jakub Kicinski <kuba@kernel.org> · 2025-09-12
Re: [PATCH net-next v5 2/5] ethtool: netlink: add ETHTOOL_MSG_MSE_GET and wire up PHY MSE access · Oleksij Rempel <o.rempel@pengutronix.de> · 2025-09-12
Re: [PATCH net-next v5 2/5] ethtool: netlink: add ETHTOOL_MSG_MSE_GET and wire up PHY MSE access · Jakub Kicinski <kuba@kernel.org> · 2025-09-13
Re: [PATCH net-next v5 2/5] ethtool: netlink: add ETHTOOL_MSG_MSE_GET and wire up PHY MSE access · Oleksij Rempel <o.rempel@pengutronix.de> · 2025-09-15
Re: [PATCH net-next v5 2/5] ethtool: netlink: add ETHTOOL_MSG_MSE_GET and wire up PHY MSE access · Jakub Kicinski <kuba@kernel.org> · 2025-09-15
Re: [PATCH net-next v5 2/5] ethtool: netlink: add ETHTOOL_MSG_MSE_GET and wire up PHY MSE access · Oleksij Rempel <o.rempel@pengutronix.de> · 2025-09-16
Re: [PATCH net-next v5 0/5] ethtool: introduce PHY MSE diagnostics UAPI and drivers · Jakub Kicinski <kuba@kernel.org> · 2025-09-12
Re: [PATCH net-next v5 0/5] ethtool: introduce PHY MSE diagnostics UAPI and drivers · Oleksij Rempel <o.rempel@pengutronix.de> · 2025-09-12

From: Jakub Kicinski <kuba@kernel.org>
Date: 2025-09-12 02:18:48
Also in: linux-doc, lkml

On Mon,  8 Sep 2025 14:46:05 +0200 Oleksij Rempel wrote:

 In practice, such scenarios can only be investigated in
fixed-link mode; here, MSE can provide an empirically estimated value
indicating conditions under which autonegotiation would not succeed.

Does fixed-link make sense here? I thought fixed-link meant MAC-to-MAC
in most contexts

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help