From: Johannes Berg <johannes@sipsolutions.net>
To: radiotap@netbsd.org
Subject: [RFC PATCH 0/2] UHR fields
Date: Thu, 9 Oct 2025 11:03:16 +0200 [thread overview]
Message-ID: <20251009091110.10697-1-johannes@sipsolutions.net> (raw)
Hi,
Over the last couple of days I've been working to define fields
for UHR, since we'll need them. I have neither a sniffer nor a
wireshark implementation yet, but that'll come in time. I'm not
sure if I'll work on wireshark myself though.
I've published these to my own forked github for easier review:
https://jmberg.github.io/radiotap.github.io/fields/UHR-ELR.html
https://jmberg.github.io/radiotap.github.io/fields/UHR.html
(and may continue to update those if I find issues)
I decided that ELR was sufficiently different that it was better
to have a separate field for it, since the MCS space is totally
different (just 0 and 1) etc.
The UHR field is copied from EHT with adjustments, so there may
be issues due to that, I'll have to review it again carefully
wrt. that, but it does inherit a lot from EHT. The concepts are
similar.
Any thoughts/comments welcome.
johannes
next reply other threads:[~2025-10-09 9:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 9:03 Johannes Berg [this message]
2025-10-09 9:03 ` [RFC PATCH 1/2] UHR-ELR: add a new field Johannes Berg
2025-10-09 9:03 ` [RFC PATCH 2/2] UHR: add " Johannes Berg
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=20251009091110.10697-1-johannes@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=radiotap@netbsd.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).