Search Linux Wireless

Re: [PATCH v2 1/2] ath9k: RX timestamp is reported at end of frame

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 2012-11-13 at 10:48 -0800, Thomas Pedersen wrote:
> Accurate RX timestamp reporting is important for proper IBSS merging,
> mesh synchronization, and MCCA scheduling. Namely, knowing where the TSF
> is recorded is needed to sync with the beacon timestamp field.

> -       rx_status->flag |= RX_FLAG_MACTIME_MPDU;
> +	rx_status->flag |= RX_FLAG_MACTIME_END;

This and the other similar patches obviously won't apply any more.

Before you repost though I think it would make sense to fix the
calculation issue that Simon pointed out on the radiotap list? I hope he
comes up with some code though as I'm not good enough at bitrate
calculations :-)

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


[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Wireless Personal Area Network]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite Hiking]     [MIPS Linux]     [ARM Linux]     [Linux RAID]

  Powered by Linux