From: Johannes Berg <johannes@sipsolutions.net>
To: Javier Cardona <javier@cozybit.com>
Cc: Marco Porsch <marco.porsch@etit.tu-chemnitz.de>,
"Luis R. Rodriguez" <rodrigue@qca.qualcomm.com>,
linux-wireless@vger.kernel.org, henry@logout.com,
"greenmesh@lists.osll.spb.ru" <greenmesh@lists.osll.spb.ru>
Subject: Re: [Greenmesh] [ath9k] mesh powersave hardware sleep + wakeup
Date: Wed, 18 Apr 2012 08:05:45 -0700 [thread overview]
Message-ID: <4F8ED849.4020002@sipsolutions.net> (raw)
In-Reply-To: <CAPjQAd99vzQDO0PzC-0jq1j8h4ekQAP_dRE=g5f=w=6EwcXrDw@mail.gmail.com> (sfid-20120418_165725_974666_D9DBAE5F)
On 4/18/2012 7:56 AM, Javier Cardona wrote:
> On Tue, Apr 17, 2012 at 7:02 PM, Johannes Berg
> <johannes@sipsolutions.net> wrote:
>> (...)
>> Keep in mind that TSF == start of TSF field, while rx_status->timestamp
>> == start of first symbol, which I didn't even remember when you guys did
>> all the Toffset things, I'm guessing they're all wrong :-)
>
> I think you guessed wrong :)
Nice! FWIW, our hardware (not that the driver supports mesh now) will
give the timestamp at the first symbol of the MPDU, so some more offset
calculations are needed and we don't give valid timestamps today. I
started working on this but haven't figured out HT preamble duration yet.
johannes
next prev parent reply other threads:[~2012-04-18 15:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 9:42 [ath9k] mesh powersave hardware sleep + wakeup Marco Porsch
2012-03-16 20:45 ` Luis R. Rodriguez
2012-03-16 22:09 ` Marco Porsch
2012-04-11 11:00 ` [Greenmesh] " Marco Porsch
2012-04-12 4:05 ` Johannes Berg
2012-04-12 7:41 ` Marco Porsch
2012-04-18 2:02 ` Johannes Berg
2012-04-18 14:56 ` Javier Cardona
2012-04-18 15:05 ` Johannes Berg [this message]
2012-04-18 15:16 ` Javier Cardona
2012-04-19 2:41 ` Yeoh Chun-Yeow
2012-04-19 2:51 ` Javier Cardona
2012-04-27 15:53 ` Marco Porsch
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=4F8ED849.4020002@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=greenmesh@lists.osll.spb.ru \
--cc=henry@logout.com \
--cc=javier@cozybit.com \
--cc=linux-wireless@vger.kernel.org \
--cc=marco.porsch@etit.tu-chemnitz.de \
--cc=rodrigue@qca.qualcomm.com \
/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).