From: Jakub Kicinski <kuba@kernel.org>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: "Andrew Lunn" <andrew@lunn.ch>,
"Heiner Kallweit" <hkallweit1@gmail.com>,
"Russell King" <linux@armlinux.org.uk>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Paolo Abeni" <pabeni@redhat.com>,
kernel@pengutronix.de, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org,
"Maxime Chevallier" <maxime.chevallier@bootlin.com>,
"Vladimir Oltean" <vladimir.oltean@nxp.com>,
"Marc Kleine-Budde" <mkl@pengutronix.de>,
"Florian Fainelli" <f.fainelli@gmail.com>,
"Köry Maincent" <kory.maincent@bootlin.com>,
thomas.petazzoni@bootlin.com, jlu@pengutronix.de
Subject: Re: Initial Thoughts on OSI Level 1 Diagnostic for 10BaseT1L Interface
Date: Tue, 27 Aug 2024 16:23:29 -0700 [thread overview]
Message-ID: <20240827162329.636fe3af@kernel.org> (raw)
In-Reply-To: <Zs1gk3gfU7EAPmPc@pengutronix.de>
On Tue, 27 Aug 2024 07:13:55 +0200 Oleksij Rempel wrote:
> I'd like to share my initial thoughts on how to approach network OSI
> Layer 1 diagnostics for projects using the 10BaseT1L interface. I
> believe this concept could be made more generic and eventually included
> in the kernel documentation. The aim is to help developers like myself
> prioritize tasks more effectively.
>
> The primary focus of this concept is on embedded systems where human
> interaction isn't feasible, meaning all interfaces should be
> machine-readable. For instance, a flight-recorder application could
> gather as much diagnostic data as possible for later analysis.
Having an open source form of that would be great. Most large operators
probably end up building their own triaging and failure classification
tools.
> At this point, the concept is targeting existing diagnostic interfaces,
> but it may also highlight the need for new ones.
Can't comment on T1L specifics myself but +1 for adding such guides
under Documentation/.
prev parent reply other threads:[~2024-08-27 23:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 5:13 Initial Thoughts on OSI Level 1 Diagnostic for 10BaseT1L Interface Oleksij Rempel
2024-08-27 23:23 ` Jakub Kicinski [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=20240827162329.636fe3af@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=jlu@pengutronix.de \
--cc=kernel@pengutronix.de \
--cc=kory.maincent@bootlin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=maxime.chevallier@bootlin.com \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=vladimir.oltean@nxp.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;
as well as URLs for NNTP newsgroup(s).