1 Jul 2009 17:05
1 Jul 2009 18:58
Re: monitor mode parametars
Luis R. Rodriguez <mcgrof <at> gmail.com>
2009-07-01 16:58:53 GMT
2009-07-01 16:58:53 GMT
On Wed, Jul 1, 2009 at 8:05 AM, Vania Toperich<vaniat <at> 3folded.nl> wrote: > Hi, > > I am wondering how to configure monitor mode parameters for ath9k, > specifically if N is using channel bonding and which one, lower or > higher. > > Thanks for help. I haven't tried this myself with monitor but it should work using iw: iw dev <devname> set freq <freq> [HT20|HT40+|HT40-] iw phy <phyname> set freq <freq> [HT20|HT40+|HT40-] When done please help expand the documentation on the iw wiki: http://wireless.kernel.org/en/users/Documentation/iw Note that not all channels will be usable with HT40- or HT40+. If the channel is disabled then you won't be able to use HT40. Then on certain band edges you won't be able to use an extension channel towards the end. This is obvious but in case you become confused for any mac80211 driver you can specifically check the ht40 allow map through debugfs. For example, I get: mcgrof <at> pogo ~ $ sudo mount -t debugfs debugfs /sys/kernel/debug/ mcgrof <at> pogo ~ $ cat /sys/kernel/debug/ieee80211/phy0/ht40allow_map 2412 HT40 +(Continue reading)
1 Jul 2009 20:24
Re: [Stable-review] [patch 000/108] 2.6.30-stable review
On Tue, Jun 30, 2009 at 5:28 PM, Greg KH<gregkh@...> wrote: > This is the start of the stable review cycle for the 2.6.30.1 release. > There are 108 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let us know. If anyone is a maintainer of the proper subsystem, and > wants to add a Signed-off-by: line to the patch, please respond with it. > drivers/net/wireless/ath5k/base.c | 7 ++ > drivers/net/wireless/ath9k/calib.c | 67 ++++++---------- > drivers/net/wireless/ath9k/main.c | 28 +++++--- > drivers/net/wireless/ath9k/pci.c | 18 +++++ > drivers/net/wireless/ath9k/regd.c | 2 +- > drivers/net/wireless/ath9k/xmit.c | 5 +- > net/mac80211/rc80211_minstrel.c | 2 +- > net/wireless/nl80211.c | 26 +++++-- > net/wireless/reg.c | 10 ++- Cc'ing linux-wireless. 14 of the 108 patches for 2.6.30.1 are for wireless. Here they are [1]: [patch 062/108] mac80211: fix minstrel single-rate memory corruption [patch 063/108] cfg80211: fix for duplicate userspace replies [patch 064/108] cfg80211: cleanup return calls on nl80211_set_reg() [patch 065/108] cfg80211: return immediately if num reg rules > NL80211_MAX_SUPP_REG_RULES [patch 066/108] cfg80211: fix in nl80211_set_reg()(Continue reading)
2 Jul 2009 02:10
Re: Do 11n rates available in ad-hoc mode
<austinxxh-ath9k <at> yahoo.com>
2009-07-02 00:10:43 GMT
2009-07-02 00:10:43 GMT
In my experiments with adhoc/mesh/AP mode of ath9k, I can see AP/STA-mode supports all the HT speeds. when set ath9k to adhoc or mesh mode, the highest speed in rcstat is only 54mbps, which says 11n HT speed does not even exist for ath9k. Anyone is interested in adding HT to adhoc/mesh mode on ath9k/mac80211...or just me? Thanks, X Xiao --- On Fri, 6/26/09, Tianji Li <Tianji.Li <at> nuim.ie> wrote: > From: Tianji Li <Tianji.Li <at> nuim.ie> > Subject: Re: [ath9k-devel] Do 11n rates available in ad-hoc mode > To: > Cc: "ath9k-devel <at> lists.ath9k.org" <ath9k-devel <at> lists.ath9k.org> > Date: Friday, June 26, 2009, 3:36 AM > Luis R. Rodriguez wrote: > > On Sun, Jun 21, 2009 at 03:17:12PM -0700, Rakesh Kumar > wrote: > > > >>> No, its not something in the IEEE standard so > such support won't likely > >>> get merged into mac80211. You might be able to > use MCS rates in ad-hoc > >>> mode but if that's possible its just becuase > we haven't fixed the code > >>> paths to not allow for it. > >>>(Continue reading)
2 Jul 2009 15:12
Re: Do 11n rates available in ad-hoc mode
Peter Tarjan <peter.tarjan <at> birdtelecom.hu>
2009-07-02 13:12:13 GMT
2009-07-02 13:12:13 GMT
n Thu, Jul 2, 2009 at 2:10 AM, <austinxxh-ath9k <at> yahoo.com> wrote:
Anyone is interested in adding HT to adhoc/mesh mode on ath9k/mac80211...or just me?
I would be also glad if it worked...
It is not clear to me if in a previous version it was enabled and later disabled?
Luis R. Rodriguez wrote:
"You can probably use MCS rates with ath9k in both ad-hoc and in mesh mode but that's just by chance -- in the future we could decide just disable that."
and later
"You might be able to use MCS rates in ad-hoc mode but if that's possible its just becuase we haven't fixed the code paths to not
allow for it."
--
Peter T.
_______________________________________________ ath9k-devel mailing list ath9k-devel <at> lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
2 Jul 2009 15:54
Re: Do 11n rates available in ad-hoc mode
xxiao <austinxxh-ath9k <at> yahoo.com>
2009-07-02 13:54:33 GMT
2009-07-02 13:54:33 GMT
Luis, Can you elaborate a bit further or give some guidance? I would like to first give MCS a try but don't know how to do it. If adding HT code to mesh/ibss is the only way to go, it will involve both mac80211/ath9k, I began to check ht.c, ibss.c, mlme.c and any advice will be greatly appreciated. Thanks, X Xiao (xxiao) --- On Thu, 7/2/09, Peter Tarjan <peter.tarjan <at> birdtelecom.hu> wrote: > From: Peter Tarjan <peter.tarjan <at> birdtelecom.hu> > Subject: Re: [ath9k-devel] Do 11n rates available in ad-hoc mode > To: "ath9k-devel <at> lists.ath9k.org" <ath9k-devel <at> lists.ath9k.org> > Date: Thursday, July 2, 2009, 8:12 AM > n Thu, Jul 2, > 2009 at 2:10 AM, <austinxxh-ath9k <at> yahoo.com> > wrote: > > > Anyone is interested in adding HT to adhoc/mesh mode on > ath9k/mac80211...or just me? > > > I would be also glad if it worked... > > It is not clear to me if in a previous version it was > enabled and later disabled? > > Luis R. Rodriguez wrote: > "You can probably use MCS rates with ath9k in both > ad-hoc and in mesh mode but that's just by chance -- in > the future we could decide just disable that." > > and later > "You might be able to use MCS rates in ad-hoc mode but > if that's possible its just becuase we haven't fixed > the code paths to not > > allow for it." > > -- > Peter T. > > > -----Inline Attachment Follows----- > > _______________________________________________ > ath9k-devel mailing list > ath9k-devel <at> lists.ath9k.org > https://lists.ath9k.org/mailman/listinfo/ath9k-devel >
6 Jul 2009 18:32
adhoc 11n support
Quoting Jouni's response to me regarding 11n "adhoc" as per IEEE:
<jm> mcgrof: IBSS support in 802.11n is not a specific part of the draft, i.e., one needs to go through
the full draft.. for example, there are IBSS-related specification in 7.3.2.57, 9.13.3.1, 10.3.2.2.2,
11.5.1.1, 11.9.7.2, 11.14.1, 11.14.2; in addition, some AP mode requirements apply, e.g., for radar
detection/DFS, but we are currently handling those by just denying IBSS on channels that could require DFS
So if you get a chance please be sure to read through all that and then send patches for mac80211.
Luis
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@...
More majordomo info at http://vger.kernel.org/majordomo-info.html
9 Jul 2009 23:12
[PATCH] ath9k: Fix enabling OFDM weak signal detection
Steven Luo <steven <at> steven676.net>
2009-07-09 21:12:21 GMT
2009-07-09 21:12:21 GMT
From: Steven Luo <steven <at> steven676.net> It seems that OFDM weak signal detection should be enabled after an ANI state reset, as indicated by the initial setting of ofdmWeakSigDetectOff and what the open Atheros HAL does. Unfortunately, the reversed sense of ofdmWeakSigDetectOff (true if weak signal detection is NOT enabled) seems to have resulted in a mixup here, causing weak signal detection to be disabled. This patch significantly improves reception and throughput from distant stations for my AR5416-based AP running compat-wireless 2009-06-25. Signed-off-by: Steven Luo <steven <at> steven676.net> Cc: stable <at> kernel.org --- --- a/drivers/net/wireless/ath/ath9k/ani.c 2009-06-24 21:14:00.000000000 -0700 +++ b/drivers/net/wireless/ath/ath9k/ani.c 2009-07-06 02:45:57.000000000 -0700 <at> <at> -482,7 +482,7 <at> <at> void ath9k_ani_reset(struct ath_hw *ah) ath9k_hw_ani_control(ah, ATH9K_ANI_SPUR_IMMUNITY_LEVEL, 0); ath9k_hw_ani_control(ah, ATH9K_ANI_FIRSTEP_LEVEL, 0); ath9k_hw_ani_control(ah, ATH9K_ANI_OFDM_WEAK_SIGNAL_DETECTION, - !ATH9K_ANI_USE_OFDM_WEAK_SIG); + ATH9K_ANI_USE_OFDM_WEAK_SIG); ath9k_hw_ani_control(ah, ATH9K_ANI_CCK_WEAK_SIGNAL_THR, ATH9K_ANI_CCK_WEAK_SIG_THR);
10 Jul 2009 20:02
Re: [PATCH] ath9k: Fix enabling OFDM weak signal detection
Luis R. Rodriguez <mcgrof <at> gmail.com>
2009-07-10 18:02:58 GMT
2009-07-10 18:02:58 GMT
On Thu, Jul 9, 2009 at 2:12 PM, Steven Luo<steven <at> steven676.net> wrote: > From: Steven Luo <steven <at> steven676.net> > > It seems that OFDM weak signal detection should be enabled after an ANI > state reset, as indicated by the initial setting of ofdmWeakSigDetectOff > and what the open Atheros HAL does. Unfortunately, the reversed sense > of ofdmWeakSigDetectOff (true if weak signal detection is NOT enabled) > seems to have resulted in a mixup here, causing weak signal detection to > be disabled. > > This patch significantly improves reception and throughput from distant > stations for my AR5416-based AP running compat-wireless 2009-06-25. > > Signed-off-by: Steven Luo <steven <at> steven676.net> > Cc: stable <at> kernel.org > --- NACK for now, please give us a chance to review this -- this may actually be correct. Luis > --- a/drivers/net/wireless/ath/ath9k/ani.c 2009-06-24 21:14:00.000000000 -0700 > +++ b/drivers/net/wireless/ath/ath9k/ani.c 2009-07-06 02:45:57.000000000 -0700 > <at> <at> -482,7 +482,7 <at> <at> void ath9k_ani_reset(struct ath_hw *ah) > ath9k_hw_ani_control(ah, ATH9K_ANI_SPUR_IMMUNITY_LEVEL, 0); > ath9k_hw_ani_control(ah, ATH9K_ANI_FIRSTEP_LEVEL, 0); > ath9k_hw_ani_control(ah, ATH9K_ANI_OFDM_WEAK_SIGNAL_DETECTION, > - !ATH9K_ANI_USE_OFDM_WEAK_SIG); > + ATH9K_ANI_USE_OFDM_WEAK_SIG); > ath9k_hw_ani_control(ah, ATH9K_ANI_CCK_WEAK_SIGNAL_THR, > ATH9K_ANI_CCK_WEAK_SIG_THR); > > > _______________________________________________ > ath9k-devel mailing list > ath9k-devel <at> lists.ath9k.org > https://lists.ath9k.org/mailman/listinfo/ath9k-devel > _______________________________________________ ath9k-devel mailing list ath9k-devel <at> lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
10 Jul 2009 20:08
Re: [PATCH] ath9k: Fix enabling OFDM weak signal detection
Luis R. Rodriguez <mcgrof <at> gmail.com>
2009-07-10 18:08:32 GMT
2009-07-10 18:08:32 GMT
On Fri, Jul 10, 2009 at 11:02 AM, Luis R. Rodriguez<mcgrof <at> gmail.com> wrote: > On Thu, Jul 9, 2009 at 2:12 PM, Steven Luo<steven <at> steven676.net> wrote: >> From: Steven Luo <steven <at> steven676.net> >> >> It seems that OFDM weak signal detection should be enabled after an ANI >> state reset, as indicated by the initial setting of ofdmWeakSigDetectOff >> and what the open Atheros HAL does. Unfortunately, the reversed sense >> of ofdmWeakSigDetectOff (true if weak signal detection is NOT enabled) >> seems to have resulted in a mixup here, causing weak signal detection to >> be disabled. >> >> This patch significantly improves reception and throughput from distant >> stations for my AR5416-based AP running compat-wireless 2009-06-25. >> >> Signed-off-by: Steven Luo <steven <at> steven676.net> >> Cc: stable <at> kernel.org >> --- > > NACK for now, please give us a chance to review this -- this may > actually be correct. Benny, Jouni indicated this matches current Fusion, know Fusion correct? Do we know if AR5416 should have OFDM weak signal detection enabled after an ANI state reset? It seemed to help this particular user. Or do we know for sure it should be disabled for all 11n cards? Since this may come up for legacy cards, how about for that case? Luis > Luis > >> --- a/drivers/net/wireless/ath/ath9k/ani.c 2009-06-24 21:14:00.000000000 -0700 >> +++ b/drivers/net/wireless/ath/ath9k/ani.c 2009-07-06 02:45:57.000000000 -0700 >> <at> <at> -482,7 +482,7 <at> <at> void ath9k_ani_reset(struct ath_hw *ah) >> ath9k_hw_ani_control(ah, ATH9K_ANI_SPUR_IMMUNITY_LEVEL, 0); >> ath9k_hw_ani_control(ah, ATH9K_ANI_FIRSTEP_LEVEL, 0); >> ath9k_hw_ani_control(ah, ATH9K_ANI_OFDM_WEAK_SIGNAL_DETECTION, >> - !ATH9K_ANI_USE_OFDM_WEAK_SIG); >> + ATH9K_ANI_USE_OFDM_WEAK_SIG); >> ath9k_hw_ani_control(ah, ATH9K_ANI_CCK_WEAK_SIGNAL_THR, >> ATH9K_ANI_CCK_WEAK_SIG_THR); >> >> >> _______________________________________________ >> ath9k-devel mailing list >> ath9k-devel <at> lists.ath9k.org >> https://lists.ath9k.org/mailman/listinfo/ath9k-devel >> > _______________________________________________ ath9k-devel mailing list ath9k-devel <at> lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
RSS Feed