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 16:17:32 -0500 [thread overview]
Message-ID: <20070326211732.GF11742@che.ojctech.com> (raw)
In-Reply-To: <F63792BF-FB34-46CB-A541-E33015EEF69E-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On Tue, Mar 27, 2007 at 09:11:17AM +1200, Scott Raynel wrote:
> Hello again,
>
> On 27/03/2007, at 7:50 AM, David Young wrote:
>
> >
> >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.
>
> I was under the impression that IEEE80211_RADIOTAP_F_RX_BADFCS
> duplicated the function of the _F_BADFCS, not _F_FCS, which indicates
> the presence of FCS bytes in the frame. Or am I missing something?
You're right. It duplicates the _F_BADFCS flag, not _F_FCS.
Dave
--
David Young OJC Technologies
dyoung-eZodSLrBbDpBDgjK7y7TUQ@public.gmane.org Urbana, IL * (217) 278-3933
prev parent reply other threads:[~2007-03-26 21:17 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
[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 [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=20070326211732.GF11742@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