#1025: TX timestamp (TSF) jumping in monitor mode
----------------------------------+-----------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: scottr
Type: defect | Status: assigned
Priority: minor | Milestone: version 0.9.x - progressive
release candidate phase
Component: madwifi: driver | Version: trunk
Resolution: | Keywords: TSF monitor
Patch_attached: 1 |
----------------------------------+-----------------------------------------
Comment (by scottr):
Hi,
After some experimentation, I've come up with the following conclusions:
1) Yes, the TX timestamp is 16 bits, as opposed to the 15 bit RX
timestamp.
2) The TX timestamp seems to have a resolution of 1ms, as opposed to the
1us resolution of the RX timestamp. This was measured by timing how long
it took for the field to wrap during a ping flood. This came out at
approximately 16,000 jiffies. So, the counter was incrementing at a rate
of 16,000 / 65536 = 0.25 jiffies per tick. With 1 jiffy == 250us (HZ),
that's 1ms per tick.
I'm currently working out how to incorporate the 1ms resolution timestamp
into the TSF returned by the HAL.
Cheers,
--
Ticket URL: <http://madwifi.org/ticket/1025>
MadWifi <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Madwifi-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/madwifi-tickets
