ath9k-devel.lists.ath9k.org archive mirror
 help / color / mirror / Atom feed
From: <bogus@does.not.exist.com>
To: ath9k-devel@lists.ath9k.org
Subject: No subject
Date: Sun, 15 Sep 2013 09:49:13 -0000	[thread overview]
Message-ID: <mailman.4.1392746587.6052.ath9k-devel@lists.ath9k.org> (raw)

timestamp.

The question is, how accurated this timestamp is? The precision is in
nanoseconds, but what accuracy i can expect?

My main need is the implement a good precision TDOA algorithm.

I don't know jack about driver development, but is something that interests
me. If the accuracy is low, can i improve it in driver or firmware?
If its possible, i can even trade reception packet speed for a better
accuracy in timestamp.

The other question is, what is the difference between the ath9k_htc and
carl9170 drivers? Both support the AR9287 (from the debian wiki).

Thanks for all

Links:

Wireshark community:
http://ask.wireshark.org/questions/28683/recommended-wireless-adapter-usb-with-linux-wireshark-that-reports-mactime-in-radiotap-header

Debian Wiki ath9k_htc: https://wiki.debian.org/ath9k_htc

Debian Wiki carl9170: https://wiki.debian.org/carl9170

--001a11335f40ad0de604f2af55f8
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,<div><br></div><div>I have one question about hardware =
timestamp in Atheros chipsets.</div><div>From a post in Wireshark community=
, the chipset AR9287 can do hardware timestamp.</div><div><br></div><div>Th=
e question is, how accurated this timestamp is? The precision is in nanosec=
onds, but what accuracy i can expect?</div>

<div><br></div><div>My main need is the implement a good precision TDOA alg=
orithm.=A0</div><div><br></div><div>I don&#39;t know jack about driver deve=
lopment, but is something that=A0interests me. If the accuracy is low, can =
i improve it in driver or firmware?=A0</div>

<div>If its possible, i can even trade reception packet speed for a better =
accuracy in timestamp.</div><div><br></div><div>The other question is, what=
 is the difference between the ath9k_htc and carl9170 drivers? Both support=
 the AR9287 (from the debian wiki).</div>

<div><br></div><div>Thanks for all</div><div><br></div><div>Links:</div><di=
v><br></div><div>Wireshark community: <a href=3D"http://ask.wireshark.org/q=
uestions/28683/recommended-wireless-adapter-usb-with-linux-wireshark-that-r=
eports-mactime-in-radiotap-header">http://ask.wireshark.org/questions/28683=
/recommended-wireless-adapter-usb-with-linux-wireshark-that-reports-mactime=
-in-radiotap-header</a></div>

<div><br></div><div>Debian Wiki ath9k_htc:=A0<a href=3D"https://wiki.debian=
.org/ath9k_htc">https://wiki.debian.org/ath9k_htc</a></div><div><br></div><=
div>Debian Wiki carl9170:=A0<a href=3D"https://wiki.debian.org/carl9170">ht=
tps://wiki.debian.org/carl9170</a></div>

</div>

--001a11335f40ad0de604f2af55f8--

             reply	other threads:[~2013-09-15  9:49 UTC|newest]

Thread overview: 96+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-15  9:49 bogus [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-11-19 18:31 No subject bogus
2016-11-19 18:31 bogus
2016-11-19 18:31 bogus
2016-11-19 18:31 bogus
2016-06-13  6:24 bogus
2016-06-13  6:24 bogus
2016-02-09  7:29 bogus
2015-11-16 16:13 bogus
2015-10-12 17:26 bogus
2014-09-13 19:40 bogus
2014-09-13 19:40 bogus
2014-09-13 19:40 bogus
2014-09-13 19:40 bogus
2014-09-13 19:40 bogus
2013-09-15  9:49 bogus
2013-09-15  9:49 bogus
2013-04-03 10:31 bogus
2013-04-03 10:31 bogus
2013-04-03 10:31 bogus
2013-04-03 10:31 bogus
2013-01-16 21:46 bogus
2013-01-16 21:46 bogus
2012-11-08  9:33 bogus
2012-05-25 15:26 bogus
2012-05-25 15:26 bogus
2012-04-05  7:54 bogus
2012-04-05  7:54 bogus
2012-02-27  5:00 bogus
2012-02-27  5:00 bogus
2012-02-27  5:00 bogus
2012-01-15  8:24 bogus
2011-11-12 14:39 bogus
2011-11-12 14:39 bogus
2011-08-05  3:08 bogus
2011-08-05  3:08 bogus
2011-08-05  3:08 bogus
2011-08-05  3:08 bogus
2011-08-05  3:08 bogus
2011-06-04 23:16 bogus
2011-06-04 23:16 bogus
2011-04-07  5:55 bogus
2011-04-07  5:55 bogus
2011-04-07  5:55 bogus
2011-04-07  5:55 bogus
2011-04-07  5:55 bogus
2010-12-19 23:59 bogus
2010-12-19 23:59 bogus
2010-12-19 23:59 bogus
2010-12-19 23:59 bogus
2010-12-19 23:59 bogus
2010-12-19 23:59 bogus
2010-12-19 23:59 bogus
2010-12-19 23:59 bogus
2010-12-19 23:59 bogus
2010-12-19 23:59 bogus
2010-12-19 23:59 bogus
2010-12-19 23:59 bogus
2010-12-19 23:59 bogus
2010-12-19 23:59 bogus
2010-09-24 14:53 bogus
2010-09-24 14:53 bogus
2010-09-24 14:53 bogus
2010-09-24 14:53 bogus
2010-09-24 14:53 bogus
2010-09-24 14:53 bogus
2010-09-24 14:53 bogus
2010-09-24 14:53 bogus
2010-09-24 14:53 bogus
2010-09-24 14:53 bogus
2010-09-24 14:53 bogus
2010-07-23 10:05 bogus
2010-03-25 17:02 bogus
2010-03-25 17:02 bogus
2009-02-27 19:01 bogus
2009-02-27 19:01 bogus
2009-02-27 19:01 bogus
2009-02-27 19:01 bogus
2009-02-27 19:01 bogus
2009-02-27 19:01 bogus
2009-02-27 19:01 bogus
2009-02-15  8:49 bogus
2009-01-04 17:33 bogus
2009-01-04 17:33 bogus
2008-10-14 11:50 bogus
2008-10-14 11:50 bogus
2008-10-14 11:50 bogus
2008-10-14 11:50 bogus
2008-10-14 11:50 bogus
2008-10-14 11:50 bogus
2008-10-14 11:50 bogus
2008-10-14 11:50 bogus
2008-10-14 11:50 bogus
2008-10-14 11:50 bogus
2008-10-14 11:50 bogus
2008-07-28  4:41 bogus

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=mailman.4.1392746587.6052.ath9k-devel@lists.ath9k.org \
    --to=bogus@does.not.exist.com \
    --cc=ath9k-devel@lists.ath9k.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).