From: Andrew Lunn <andrew@lunn.ch>
To: Daniel Golle <daniel@makrotopia.org>
Cc: Vladimir Oltean <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Russell King <linux@armlinux.org.uk>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 5/5] net: dsa: mxl862xx: add SerDes ethtool statistics
Date: Wed, 20 May 2026 03:12:56 +0200 [thread overview]
Message-ID: <8fe2cc9d-2a22-4a19-b313-8e570cdc975e@lunn.ch> (raw)
In-Reply-To: <agzqLhlZsSQnWjP-@makrotopia.org>
> The firmware also exposes self-test via PRBS and BERT, which also
> doesn't fit the ethtool self-test model very well (which currently
> supports only MAC-level and PHY-level loopback tests, with no way to
> represent the PCS/SerDes-level)...
Where was a presentation about this at last years netdev conference
and a long discussion with Alex at Meta about how to expose PRBS the
fbnic has. It is probably the same PCS or similar PCS, since they
licensed it as well.
Andrew
prev parent reply other threads:[~2026-05-20 1:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 17:38 [PATCH net-next 0/5] net: dsa: mxl862xx: SerDes ports and stats Daniel Golle
2026-05-19 17:38 ` [PATCH net-next 1/5] net: dsa: mxl862xx: store firmware version for feature gating Daniel Golle
2026-05-19 17:38 ` [PATCH net-next 2/5] net: dsa: mxl862xx: move phylink stubs to mxl862xx-phylink.c Daniel Golle
2026-05-19 17:38 ` [PATCH net-next 3/5] net: dsa: mxl862xx: move API macros to mxl862xx-host.h Daniel Golle
2026-05-19 17:39 ` [PATCH net-next 4/5] net: dsa: mxl862xx: add support for SerDes ports Daniel Golle
2026-05-19 17:39 ` [PATCH net-next 5/5] net: dsa: mxl862xx: add SerDes ethtool statistics Daniel Golle
2026-05-19 18:40 ` Vladimir Oltean
2026-05-19 22:54 ` Daniel Golle
2026-05-20 1:12 ` Andrew Lunn [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8fe2cc9d-2a22-4a19-b313-8e570cdc975e@lunn.ch \
--to=andrew@lunn.ch \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®