linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bruno Randolf <bruno@thinktube.com>
To: "Tomas Winkler" <tomasw@gmail.com>
Cc: "Luis R. Rodriguez" <lrodriguez@atheros.com>,
	"Michael Buesch" <mb@bu3sch.de>,
	"John W. Linville" <linville@tuxdriver.com>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: pull request: wireless-2.6 2008-08-26
Date: Thu, 28 Aug 2008 13:13:52 +0200	[thread overview]
Message-ID: <200808281313.53163.bruno@thinktube.com> (raw)
In-Reply-To: <1ba2fa240808280352q4a913c1cv33a6bc0998cdbcb9@mail.gmail.com>

On Thursday 28 August 2008 12:52:36 Tomas Winkler wrote:
> Do you know how the  TSF is actually synchronized from the HW perspective?

no, unfortuately i have no idea. also i should admit that we have problems 
with atheros hardware in that we don't know when the RX timestamp is taken 
exactly. this means our IBSS merge can't be 100% exact. but the usual case we 
need to catch is when the beacon TSF is much higher than the local TSF. 

i don't care about IBSS power-save right now.

> > with the same HW but it did not work any more - i didn't have the time to
> > investigate this issue...
>
> There is another IBSS bug that was introduced connected to rates maybe
> this is also your problem.. we have something in the pipe that should
> solve this.

good, i'll retest once you subitted the patch.

> Sure but if TSF is not adopted correctly and that's the case probably
> of most of the drivers under mac80211 then it makes
> worth.  Just need to be aware of this.

true, we need to find a way to support this hardware too...

bruno


  reply	other threads:[~2008-08-28 11:14 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-27  1:30 pull request: wireless-2.6 2008-08-26 John W. Linville
2008-08-27  7:38 ` Tomas Winkler
2008-08-27  8:40   ` David Miller
2008-08-27  9:13     ` Tomas Winkler
2008-08-27 11:10     ` Marcel Holtmann
2008-08-27 10:05       ` Tomas Winkler
2008-08-27 10:10         ` Johannes Berg
2008-08-27 10:33           ` David Miller
2008-08-27 11:34           ` Tomas Winkler
2008-08-27 11:45             ` David Miller
2008-08-27 12:26               ` Tomas Winkler
2008-08-27 13:10             ` Michael Buesch
2008-08-27 14:55               ` Tomas Winkler
2008-08-27 15:22                 ` Michael Buesch
2008-08-27 15:45                   ` Tomas Winkler
2008-08-27 10:32         ` David Miller
2008-08-27 11:42           ` Tomas Winkler
2008-08-27 13:57         ` Arjan van de Ven
2008-08-27 11:39 ` David Miller
2008-08-27 19:26 ` Tomas Winkler
2008-08-27 20:25   ` Michael Buesch
2008-08-27 23:11     ` Tomas Winkler
2008-08-27 23:31       ` Luis R. Rodriguez
2008-08-28  0:19         ` Tomas Winkler
2008-08-28  1:30           ` Luis R. Rodriguez
2008-08-28  7:59             ` Tomas Winkler
2008-08-28 10:35         ` Bruno Randolf
2008-08-28 10:52           ` Tomas Winkler
2008-08-28 11:13             ` Bruno Randolf [this message]
2008-08-28  8:31       ` Michael Buesch
2008-08-28  9:29         ` Tomas Winkler

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=200808281313.53163.bruno@thinktube.com \
    --to=bruno@thinktube.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=lrodriguez@atheros.com \
    --cc=mb@bu3sch.de \
    --cc=netdev@vger.kernel.org \
    --cc=tomasw@gmail.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).