From: "Alina Friedrichsen" <x-alina@gmx.net>
To: linux-wireless@vger.kernel.org, linville@tuxdriver.com,
johannes@sipsolutions.net
Subject: [PATCH] ath9k: Don't reset TSF after scanning automatically
Date: Thu, 19 Feb 2009 23:46:31 +0100 [thread overview]
Message-ID: <20090219224631.322560@gmx.net> (raw)
Reset automatically the TSF on re-enabling beaconing after scanning in =
IBSS mode causes several problems. For example a new created IBSS netwo=
rk can't age before an other node has joined, because scans are done au=
tomatically in that case. And several other strange bugs more...
The TSF reset is done manually in the higher level mac80211 code in the=
cases were it's needed, so we don't need to do it here.
Signed-off-by: Alina Friedrichsen <x-alina@gmx.net>
---
diff --git a/drivers/net/wireless/ath9k/beacon.c b/drivers/net/wireless=
/ath9k/beacon.c
index 390d510..18bda36 100644
--- a/drivers/net/wireless/ath9k/beacon.c
+++ b/drivers/net/wireless/ath9k/beacon.c
@@ -790,8 +790,6 @@ void ath_beacon_config(struct ath_softc *sc, int if=
_id)
u64 tsf;
u32 tsftu;
ath9k_hw_set_interrupts(ah, 0);
- if (nexttbtt =3D=3D intval)
- intval |=3D ATH9K_BEACON_RESET_TSF;
if (sc->sc_ah->opmode =3D=3D NL80211_IFTYPE_ADHOC) {
/*
* Pull nexttbtt forward to reflect the current
@@ -825,6 +823,9 @@ void ath_beacon_config(struct ath_softc *sc, int if=
_id)
sc->imask |=3D ATH9K_INT_SWBA;
ath_beaconq_config(sc);
} else if (sc->sc_ah->opmode =3D=3D NL80211_IFTYPE_AP) {
+ if (nexttbtt =3D=3D intval)
+ intval |=3D ATH9K_BEACON_RESET_TSF;
+
/*
* In AP mode we enable the beacon timers and
* SWBA interrupts to prepare beacon frames.
--=20
Psssst! Schon vom neuen GMX MultiMessenger geh=F6rt? Der kann`s mit all=
en: http://www.gmx.net/de/go/multimessenger01
--
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
reply other threads:[~2009-02-19 22:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20090219224631.322560@gmx.net \
--to=x-alina@gmx.net \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).