From: Andrew Lunn <andrew@lunn.ch>
To: Ethan Nelson-Moore <enelsonmoore@gmail.com>
Cc: netdev@vger.kernel.org, linux-api@vger.kernel.org,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>
Subject: Re: [PATCH net-next] uapi: net: mii: correct 100BASE4 bit descriptions
Date: Thu, 29 Jan 2026 14:49:20 +0100 [thread overview]
Message-ID: <268c80bc-e2be-453f-8d03-bf5a5cc1cf9c@lunn.ch> (raw)
In-Reply-To: <20260129051736.18986-1-enelsonmoore@gmail.com>
On Wed, Jan 28, 2026 at 09:17:35PM -0800, Ethan Nelson-Moore wrote:
> The 100BASE4 bits in MII registers indicate 100BASE-T4, as can be seen
> in Ethernet PHY documentation (such as the datasheet linked below), not
> 4K packets. Correct the comments describing these bits.
>
> Link: https://www.ti.com/lit/ds/symlink/dp83849c.pdf
It is much better to reference IEEE 802.3, clause 22, section X.Y.Z.
The standard is free to download.
I do wounder where the 4K comment comes from. Did 100BASE-T4 introduce
the concept of jumbo packets?
Andrew
---
pw-bot: cr
prev parent reply other threads:[~2026-01-29 13:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-29 5:17 [PATCH net-next] uapi: net: mii: correct 100BASE4 bit descriptions Ethan Nelson-Moore
2026-01-29 13:49 ` 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=268c80bc-e2be-453f-8d03-bf5a5cc1cf9c@lunn.ch \
--to=andrew@lunn.ch \
--cc=enelsonmoore@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=linux-api@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
/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