From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
To: radiotap-eZodSLrBbDpBDgjK7y7TUQ@public.gmane.org
Subject: new RX flag request: bad PLCP
Date: Fri, 03 Aug 2007 23:28:31 +0200 [thread overview]
Message-ID: <1186176511.13315.2.camel@johannes.berg> (raw)
[-- Attachment #1: Type: text/plain, Size: 400 bytes --]
Some people actually want to see frames their microwave sends; thus we
need a flag to indicate that the PLCP checksum failed. I thus propose:
/* frame failed PLCP check; for the benefit of older software (and
* because it is most likely true) you should also set the BADFCS flag) */
#define IEEE80211_RADIOTAP_F_RX_BADPLCPCHECK 0x0002 /* frame failed PLCP check */
Comments?
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
reply other threads:[~2007-08-03 21:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1186176511.13315.2.camel@johannes.berg \
--to=johannes-cdvu00un1vgdhxzaddlk8q@public.gmane.org \
--cc=radiotap-eZodSLrBbDpBDgjK7y7TUQ@public.gmane.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 NNTP newsgroup(s).