On Wed, 2010-05-12 at 18:42 +0200, Roberto Riggio wrote:
> On 05/09/2010 10:24 PM, Gábor Stefanik wrote:
> >> u_int16_t it_len;
> >> u_int32_t it_present;
> >>
> > AFAIK these 2 fields need to be little-endian even on big-endian
> > machines. If your system is big-endian, this can cause problems.
> >
>
> Thanks, that was indeed the issue. I totally missed this info
> in the radiotap website. Everything is working fine now.
I'd make it more prominent, but ... this is what it says now:
Important Radiotap Characteristics
* Fields are strictly ordered; The developer can specify any
combination of fields, but the data must appear following the
radiotap header in the order they are specified in the
it_present bitmask (or more accurately, in the order the bit
numbers for the it_present bitmask are defined).
* Data is specified in little endian byte-order, all data fields
including the it_version, it_len and it_present fields in the
radiotap header are to be specified in little endian byte-order.
This wiki has adopted the Linux convention of using __le64,
__le32 and __le16 for 64-, 32- and 16-bit little endian
quantities.
johannes
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
