From: Georgiewskiy Yuriy <bottleman@icf.org.ru>
To: linux-wireless@vger.kernel.org, ath9k-devel@lists.ath9k.org,
devel@lists.open80211s.org
Subject: improve operational ANI in Mesh mode
Date: Sat, 16 Feb 2013 06:43:16 +0400 (MSK) [thread overview]
Message-ID: <alpine.DEB.2.02.1302160630580.4293@icf.org.ru> (raw)
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1895 bytes --]
Hi, in our setups we experience pure ANI operational in mesh mode
VS AP mode, after debuffing and digging in ANI code i find what ANI
in AP mode work in limited mode, i try this mode with mesh and seems
getting same good operation as in AP mode, i am not familiar with ANI
may be there is another better way to fix this issue?
changes what i made:
diff -ruN compat-drivers-3.7.6-1/drivers/net/wireless/ath/ath9k/ani.c compat-drivers-3.7.6-1-new/drivers/net/wireless/ath/ath9k/ani.c
--- compat-drivers-3.7.6-1/drivers/net/wireless/ath/ath9k/ani.c 2013-02-11 04:23:53.000000000 +0400
+++ compat-drivers-3.7.6-1-new/drivers/net/wireless/ath/ath9k/ani.c 2013-02-16 05:03:46.640746411 +0400
@@ -303,7 +303,8 @@
ah->stats.ast_ani_reset++;
/* only allow a subset of functions in AP mode */
- if (ah->opmode == NL80211_IFTYPE_AP) {
+ if (ah->opmode == NL80211_IFTYPE_AP || ah->opmode == NL80211_IFTYPE_MESH_POINT) {
+ ath_dbg(common, ANI, "only allow a subset of functions in AP or MESH mode");
if (IS_CHAN_2GHZ(chan)) {
ah->ani_function = (ATH9K_ANI_SPUR_IMMUNITY_LEVEL |
ATH9K_ANI_FIRSTEP_LEVEL);
@@ -323,7 +324,8 @@
if (is_scanning ||
(ah->opmode != NL80211_IFTYPE_STATION &&
- ah->opmode != NL80211_IFTYPE_ADHOC)) {
+ ah->opmode != NL80211_IFTYPE_ADHOC &&
+ ah->opmode != NL80211_IFTYPE_MESH_POINT)) {
/*
* If we're scanning or in AP mode, the defaults (ini)
* should be in place. For an AP we assume the historical
C уважением With Best Regards
Георгиевский Юрий. Georgiewskiy Yuriy
+7 4872 711666 +7 4872 711666
факс +7 4872 711143 fax +7 4872 711143
Компания ООО "Ай Ти Сервис" IT Service Ltd
http://nkoort.ru http://nkoort.ru
JID: GHhost@icf.org.ru JID: GHhost@icf.org.ru
YG129-RIPE YG129-RIPE
next reply other threads:[~2013-02-16 3:16 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-16 2:43 Georgiewskiy Yuriy [this message]
2013-02-16 4:08 ` improve operational ANI in Mesh mode Adrian Chadd
2013-02-16 4:18 ` Georgiewskiy Yuriy
2013-02-19 13:40 ` Simon Wunderlich
2013-02-19 14:04 ` Georgiewskiy Yuriy
2013-02-19 16:31 ` [ath9k-devel] " Adrian Chadd
2013-02-19 16:49 ` Georgiewskiy Yuriy
2013-02-19 17:20 ` Adrian Chadd
2013-02-19 18:29 ` Sujith Manoharan
2013-02-19 18:33 ` Adrian Chadd
2013-02-19 18:38 ` Georgiewskiy Yuriy
2013-02-19 18:44 ` Sujith Manoharan
2013-02-19 19:11 ` Georgiewskiy Yuriy
2013-02-19 19:37 ` Adrian Chadd
2013-02-19 20:31 ` Georgiewskiy Yuriy
2013-02-20 3:30 ` Yeoh Chun-Yeow
2013-02-20 19:31 ` Georgiewskiy Yuriy
2013-02-21 0:37 ` Georgiewskiy Yuriy
2013-02-21 1:08 ` Yeoh Chun-Yeow
2013-02-21 1:23 ` Georgiewskiy Yuriy
2013-02-20 14:24 ` Bob Copeland
2013-02-20 19:55 ` Georgiewskiy Yuriy
2013-02-20 20:25 ` Bob Copeland
2013-02-20 20:27 ` Bob Copeland
2013-02-20 3:12 ` Sujith Manoharan
2013-02-20 10:31 ` Simon Wunderlich
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=alpine.DEB.2.02.1302160630580.4293@icf.org.ru \
--to=bottleman@icf.org.ru \
--cc=ath9k-devel@lists.ath9k.org \
--cc=devel@lists.open80211s.org \
--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 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).