On Mon, Mar 19, 2012 at 10:50 PM, Qasim Javed wrote:
> Hi Alexander,
>
> As Adrian mentioned, indeed there is a timestamp field in the transmit
> status descriptor which could be used for your purpose. This timestamp
> is basically the last 16-bits of a snapshot of the TSF counter. Since
> you are
Hi Alexander,
As Adrian mentioned, indeed there is a timestamp field in the transmit
status descriptor which could be used for your purpose. This timestamp
is basically the last 16-bits of a snapshot of the TSF counter. Since
you are using a card based on AR5213 chipset, the TX status descriptor
h
I'd ignore wireshark for now. Look through the TX and TX completion
code. There's a timestamp field somewhere that should be populated for
all TXed frames.
Verify first that the TSF is being written into that timestamp field
upon completion, and then verify that it's pushed all the way back up
thr
Adrian,
I am currently running a 5413, details attached below which does not appear
to attach timestamps to packets that have been transmitted from the same
interface.
When I run wireshark (or tshark) on the wlan0 interface, I can see
timestamps associated with all received packets. However, when
Hi!
On 14 March 2012 13:57, Alexander Watson wrote:
> Hello,
>
> I am working on a project where I need to be able to accurately timestamp
> both transmitted and received packets from an Atheros NIC. I am aware that
> in its normal mode of operation and that Ath5k only timestamps received
> packe
