From: David Young <dyoung-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
To: radiotap-rN9S6JXhQ+WXmMXjJBpWqg@public.gmane.org
Subject: Re: Query about recent Radiotap changes
Date: Mon, 26 Mar 2007 14:50:45 -0500 [thread overview]
Message-ID: <20070326195045.GA11742@che.ojctech.com> (raw)
In-Reply-To: <16B0F9F6-C3B2-4A00-A789-C1DD3E279D08-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On Mon, Mar 26, 2007 at 09:35:24PM +1200, Scott Raynel wrote:
> Hi!
>
> Just noticed the changes that went into OpenBSD tonight, but I have a
> query as to one of the comments in the file:
>
> /* For IEEE80211_RADIOTAP_RX_FLAGS */
> #define IEEE80211_RADIOTAP_F_RX_BADFCS 0x0001 /* Frame failed CRC
> check.
> *
> * Deprecated: use the flag
> * IEEE80211_RADIOTAP_F_FCS in
> * the
> IEEE80211_RADIOTAP_FLAGS
> * field, instead.
> */
>
> /* For IEEE80211_RADIOTAP_TX_FLAGS */
>
> What does the Deprecated warning apply to? I presume it's got to do
> with the old field, IEEE80211_RADIOTAP_FCS, but the comment is in an
> extremely weird place. It implies that the new _F_RX_BADFCS flag is
> deprecated.
The _F_RX_BADFCS flag in the field IEEE80211_RADIOTAP_RX_FLAGS is
redundant. The flag duplicates the function of the _F_FCS field in
the IEEE80211_RADIOTAP_FLAGS field. TIMTOWTDI is a recipe for design
complexity.
The reasons I add the four new fields are three-fold:
* keep my word that those fields would become part of the standard
* standardize an existing practice that apparently came to
be due to an innocent misunderstanding between myself and
another developer
* create a basis for adding new fields: the next available
type number is 18.
You could say these fields became part of the standard through the first
and last radiotap fields amnesty. I am not
Dave
--
David Young OJC Technologies
dyoung-eZodSLrBbDpBDgjK7y7TUQ@public.gmane.org Urbana, IL * (217) 278-3933
next prev parent reply other threads:[~2007-03-26 19:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-26 9:35 Query about recent Radiotap changes Scott Raynel
[not found] ` <16B0F9F6-C3B2-4A00-A789-C1DD3E279D08-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2007-03-26 19:50 ` David Young [this message]
[not found] ` <20070326195045.GA11742-eZ+MEZF6i8Dc+919tysfdA@public.gmane.org>
2007-03-26 19:53 ` David Young
2007-03-26 21:11 ` Scott Raynel
[not found] ` <F63792BF-FB34-46CB-A541-E33015EEF69E-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2007-03-26 21:17 ` David Young
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=20070326195045.GA11742@che.ojctech.com \
--to=dyoung-e+axbwqsrlaavxtiumwx3w@public.gmane.org \
--cc=radiotap-rN9S6JXhQ+WXmMXjJBpWqg@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