From: "Alina Friedrichsen" <x-alina@gmx.net>
To: Sujith <Sujith.Manoharan@atheros.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: IBSS issues
Date: Fri, 27 Feb 2009 11:56:34 +0100 [thread overview]
Message-ID: <20090227105634.291200@gmx.net> (raw)
In-Reply-To: <18855.48369.413479.945570@gargle.gargle.HOWL>
Hello!
> Yes, the TBTT is calculated only once after joining the BSS network.
What about the following, which is called after scanning?
ieee80211_if_config(sdata, IEEE80211_IFCC_BEACON_ENABLED);
This calls indirectly the function which looks in the template for the =
TSF.
> Am not sure I understand the proposal. What would the tsf value in
> set_tsf() be ?
> 11.1.4 (IEEE802.11-2007) says that the TSF has to be reset to zero on
> joining
> an IBSS network. We do that correctly.
In the praxis setting the TSF should not a problem as log the value is =
not higher then the original TSF from the other node. As long the clock=
s are working correct and the other node is not moved with nearly light=
-speed this shouldn't happen. ;)
> To calculate the next TBTT, we
> can't use the
> HW TSF, since it has just been reset. And the Beacon's timestamp + in=
tval
> + FUDGE
> is what we do in ath9k to get the TBTT for this peer, which I think i=
s
> correct.
> A sniffer shows the beacon generation being evenly distributed.
I think the TSF timer keep this value more up-to-date than a static var=
iable in RAM, so that e.g. the speed of the CPU has a lower effect on t=
he de-sync of this value.
Regards
Alina
--=20
Computer Bild Tarifsieger! GMX FreeDSL - Telefonanschluss + DSL
f=FCr nur 17,95 =BF/mtl.!* http://dsl.gmx.de/?ac=3DOM.AD.PD003K11308T45=
69a
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-02-27 10:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-27 4:04 IBSS issues Sujith
2009-02-27 8:25 ` Alina Friedrichsen
2009-02-27 8:44 ` Sujith
2009-02-27 9:53 ` Alina Friedrichsen
2009-02-27 10:14 ` Sujith
2009-02-27 10:56 ` Alina Friedrichsen [this message]
2009-02-27 9:01 ` Alina Friedrichsen
2009-02-27 9:24 ` Sujith
2009-02-27 10:19 ` Alina Friedrichsen
2009-02-27 10:32 ` Sujith
2009-02-27 11:02 ` Alina Friedrichsen
2009-02-27 21:53 ` Johannes Berg
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=20090227105634.291200@gmx.net \
--to=x-alina@gmx.net \
--cc=Sujith.Manoharan@atheros.com \
--cc=linux-wireless@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.