From: Ben Greear <greearb@candelatech.com>
To: Stefan Bruens <stefan.bruens@rwth-aachen.de>,
linux-wireless@vger.kernel.org
Subject: Re: Support of TX timestamps in kernel / by hardware
Date: Sun, 17 May 2015 09:29:42 -0700 [thread overview]
Message-ID: <5558C1F6.2010006@candelatech.com> (raw)
In-Reply-To: <5898815.03gqQSlLcY@pebbles.site>
On 05/17/2015 09:08 AM, Stefan Bruens wrote:
> Hi,
>
> I have looked through the individual hardware drivers, but there seems to be
> no way of getting an accurate time when an individual packet preamble hits the
> antenna.
>
> For RX, most drivers support a RX timestamp based on the TSF and put this into
> struct ieee80211_rx_status -> mactime. For TX, I found nothing related.
I guess a timestamp made in the driver when tx-status is given by the
firmware/hardware might be at least a good estimate.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2015-05-17 16:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-17 16:08 Support of TX timestamps in kernel / by hardware Stefan Bruens
2015-05-17 16:29 ` Ben Greear [this message]
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=5558C1F6.2010006@candelatech.com \
--to=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
--cc=stefan.bruens@rwth-aachen.de \
/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).