linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: Andy Green <andy@warmcat.com>
Cc: Michael Wu <flamingice@sourmilk.net>, linux-wireless@vger.kernel.org
Subject: Re: [RFC][PATCH] Add radiotap-based packet injection capability to  monitor mode
Date: Thu, 15 Mar 2007 02:41:41 -0400	[thread overview]
Message-ID: <1173940901.24577.6.camel@dv> (raw)
In-Reply-To: <45F8E873.4050705@warmcat.com>

On Thu, 2007-03-15 at 06:32 +0000, Andy Green wrote:
>   It seemed from the struct ieee80211_radiotap_header header version in 
> Linville's latest FC7 #4 RPM anyway that they were native endian, ie, 
> using u16 in there.  I took from that the args were likewise u16, which 
> was possible since the radiotap part doesn't normally leave the machine. 
>   But having fixed endianness makes more sense.

I posted a patch that annotates radiotap as little-endian, but I haven't
seen any reaction so far.

I'm not aware of any driver that implements radiotap as native endian
(at least intentionally).  All implementation I know are little endian,
even if it means sparse warnings (that's how I became aware of the
problem with the non-annotated include file for radiotap).

-- 
Regards,
Pavel Roskin


      reply	other threads:[~2007-03-15  6:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-15  1:13 [RFC][PATCH] Add radiotap-based packet injection capability to monitor mode Andy Green
2007-03-15  5:56 ` Michael Wu
2007-03-15  6:32   ` Andy Green
2007-03-15  6:41     ` Pavel Roskin [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=1173940901.24577.6.camel@dv \
    --to=proski@gnu.org \
    --cc=andy@warmcat.com \
    --cc=flamingice@sourmilk.net \
    --cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).