[ath9k-devel] TX power control, WAS: Rate Selection problems in mixed 802.11b/802.11g IBSS
Luis, I'm retracting my observation. Trying to reproduce it with the logs you asked for did show that the ath9k node tried to increase the tx data rate from time to time and that the signal strength was very low. I don't quite understand this, but now I do not think that the RC algorithm is to blame. Another question popped up, however. I'm evaluating ath9k and Atheros 802.11n cards for a project we are working on. Together with a co-worker we did some measurements of the tx power. What we found is, that using iwconfig to change the tx power had no measurable effect on the tx power on the antenna port. Even if I configured the tx power down to 1db the measured value remained constant at 27mW. So, tx power control seems not to be implemented in ath9k. Is this correct and if so, will this change? -- Regards Joerg - Ursprüngliche Mail Von: Luis R. Rodriguez mcg...@gmail.com An: Joerg Pommnitz pommn...@yahoo.com CC: ath9k-devel@lists.ath9k.org Gesendet: Dienstag, den 17. November 2009, 18:07:12 Uhr Betreff: Re: [ath9k-devel] Rate Selection problems in mixed 802.11b/802.11g IBSS On Tue, Nov 17, 2009 at 12:34 AM, Joerg Pommnitz wrote: Hello all, I have seen a problem using ath9k in an IBSS network formed from two nodes: one AR5xxx running Madwifi and one A9xxx using ath9k. The network was running on channel 14 which Madwifi limits to 802.11b for regulatory reasons (we have permission to use this channel). The strange part was ath9k: Using iwdevwlan0 stations dump I could see that the TX rate to the Madwifi node was stuck at 1 Mbit/s. An iperf run confirmed the miserable data rate. I could force the rate with iwconfigwlan0 rate 11M to something reasonable (once again measured with iperf). In the latter case, iw still claimed a TX rate of 1Mbit/s but iperf did show the expected data rate. The Madwifi node on the other end was happily selecting 11Mbit/s on its own. Any ideas? Yeah I'm curious can you try on the ath9k station: iw list And then please try monitoring the rcstat file as root: watch cat /sys/kernel/debug/ath9k/phy0/rcstat When you run iperf what rates do you see being used? After a while of running iperf (3 times) with UDP: iperc -c ip-address-of-server -u -i 1 -b 30M please paste the output of the rcstat file. Luis __ Do You Yahoo!? Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails. http://mail.yahoo.com ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] Kernel Oops AR9220
On Fri, Nov 20, 2009 at 6:35 AM, Douglass, Woodrow woodrow.dougl...@qinetiq-na.com wrote: After installing the compat-wireless-2.6 package from november 18th, the system locks up completely after bringing the interface up, instead of just the oops. Thank you in advance for any help you guys can provide. compat-wireless is bleeding edge so can have bugs, for stable use the stable snapshots. I can't reproduce yet -- but please followup on the linux-wireless thread instead. Luis ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] [PATCH] ath9k: This patch fix RX unpadding for any received frame.
Luis R. Rodriguez a écrit :
On Thu, Nov 19, 2009 at 1:19 PM, Benoit Papillault
benoit.papilla...@free.fr wrote:
From: Benoit PAPILLAULT ben...@benoit-laptop.(none)
It has been tested with a 802.11 frame generator and by checking the FCS
field
of each received frame with the value reported by the Atheros hardware. This
patch is useful if you are trying to analyze non standard 802.11 frame going
over the air.
Thank you for your patch! But can you please elaborate on your commit
log entry? This just tells me that you've tested it and how its useful
but it in no way tells me what you found was wrong and also does not
explain how you fixed it.
Sure. I use a 802.11 frame generator that generates every value for the
first 2 bytes (frame control field) and a varying length. What was wrong
is that using ath9k and a monitor interface, I was getting frames with
padding still inside or unpadding done at the wrong position and as
such, wrong FCS. In order to fix it, I use the FCS field of received
frame and tried every position and size for unpadding. This way I found
a formula that gives me the exact position and size for proper
unpadding. I then put this formula into ath9k. This formula is different
from 802.11 hdrlen.
Signed-off-by: Benoit PAPILLAULT ben...@benoit-laptop.(none)
---
drivers/net/wireless/ath/ath9k/common.c | 19 ++-
1 files changed, 14 insertions(+), 5 deletions(-)
diff --git a/drivers/net/wireless/ath/ath9k/common.c
b/drivers/net/wireless/ath/ath9k/common.c
index 2f1e161..4a13632 100644
--- a/drivers/net/wireless/ath/ath9k/common.c
+++ b/drivers/net/wireless/ath/ath9k/common.c
@@ -231,26 +231,35 @@ void ath9k_cmn_rx_skb_postprocess(struct ath_common
*common,
{
struct ath_hw *ah = common-ah;
struct ieee80211_hdr *hdr;
- int hdrlen, padsize;
+ int hdrlen, padpos, padsize;
u8 keyix;
__le16 fc;
/* see if any padding is done by the hw and remove it */
hdr = (struct ieee80211_hdr *) skb-data;
hdrlen = ieee80211_get_hdrlen_from_skb(skb);
+ padpos = 24;
fc = hdr-frame_control;
+ if ((fc cpu_to_le16(IEEE80211_FCTL_FROMDS|IEEE80211_FCTL_TODS)) ==
+ cpu_to_le16(IEEE80211_FCTL_FROMDS|IEEE80211_FCTL_TODS)) {
+ padpos += 6; /* ETH_ALEN */
+ }
How about just using ETH_ALEN then?
Indeed. I was just in a hurry.
+ if ((fc
cpu_to_le16(IEEE80211_STYPE_QOS_DATA|IEEE80211_FCTL_FTYPE)) ==
+ cpu_to_le16(IEEE80211_STYPE_QOS_DATA|IEEE80211_FTYPE_DATA)) {
+ padpos += 2;
+ }
/* The MAC header is padded to have 32-bit boundary if the
* packet payload is non-zero. The general calculation for
* padsize would take into account odd header lengths:
-* padsize = (4 - hdrlen % 4) % 4; However, since only
+* padsize = (4 - padpos % 4) % 4; However, since only
* even-length headers are used, padding can only be 0 or 2
* bytes and we can optimize this a bit. In addition, we must
* not try to remove padding from short control frames that do
* not have payload. */
- padsize = hdrlen 3;
- if (padsize hdrlen = 24) {
- memmove(skb-data + padsize, skb-data, hdrlen);
+ padsize = padpos 3;
+ if (padsize skb-len=padpos+padsize+FCS_LEN) {
+ memmove(skb-data + padsize, skb-data, padpos);
skb_pull(skb, padsize);
}
If the skb-len would have been short ieee80211_get_hdrlen_from_skb()
would have picked up on this and 0 would have been used for hdrlen
therefore skipping this operation. With this patch even if skb-len
was 0 your padsize is always based on some static value. Additionally
its unclear to me how and why you substitute
ieee80211_get_hdrlen_from_skb() to a static 24 + something.
The substitution is indeed the key of this patch. The check about
skb-len is to make sure that the frame is large enough to contain the
computed padding, which cannot be contained in the FCS field itself.
Also the possible static values for padpos are either (24 + 2) or (24
+ 6) right? Well these 3 will always give true. So you are always
padding and this changes the way this was being implemented.
It can be 24, 24+6=30, 24+2=26 or 24+6+2=28. With the 3 mask, this
gives : 0 (for 24), 2 (for 30), 2 (for 26) and 0 (for 28).
Unless I'm missing something.
Luis
--
To unsubscribe from this list: send the line unsubscribe linux-wireless in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Regards,
Benoit
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] 802.11n HT for adhoc?
neither on 11s I'm hacking on it slowly, due to limited time after work. --- On Thu, 11/19/09, Yongheng Qi jete...@gmail.com wrote: From: Yongheng Qi jete...@gmail.com Subject: Re: [ath9k-devel] 802.11n HT for adhoc? To: Duy Nguyen dnl...@gmail.com Cc: ath9k-devel@lists.ath9k.org Date: Thursday, November 19, 2009, 7:38 PM ad hoc is not support on 11n. 11s, I don't know. 2009/11/19 Duy Nguyen dnl...@gmail.com Hi everyone, I've been browsing through the ath9k list, and it seems that many users here are interested 802.11n ad hoc HT. However, this function is not presently supported, and the maximum throughput you can get is the same as 802.11g. Someone mentions two options for implementing it: mac80211 and 80211s. I have the following questions. 1) Is anyone currently working HT feature for 802.11n in ad hoc? 2) If I were to give a stab at it, should I implement this function in ath9k driver, mac80211, or 80211s(since 802.11s requires ad hoc mode for nodes anyway?). Duy ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- Yongheng Qi Mobile: +86 1390 119 7481 -Inline Attachment Follows- ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] Kernel config for eepc
Luis, as an addendum to this I am using suse 11.2 on an eeepc. 2.6.32-rc7-wl-1-desktop-W. When I boot using the original kernel and compile wireless testing it compiles ok. However, If I boot to the wireless-testing kernel(r6) then it does not compile. It complains about a preload file being missing, during the modules_install. I can rerun and get the exact message if you like. My wireless network appears to be working fine using 11g. I have not been able to get 11n yet. Would you like a copy of my config? Thanks, Brian On Fri, 20 Nov 2009 12:34:32 -0800 Luis R. Rodriguez mcg...@gmail.com wrote: Sam, should we use the Ubuntu karmic config to test against the eepc or are there some tweaks on the config you might be aware of. Thanks, Luis ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] Kernel config for eepc
COMO CRESTA DESACTIVO ESTA WEA NO ME INTERESA LINUX!!! ME GUSTA MAC!!!PORFAVOR SI ME PUEDEN AYUDAR Y OJALA LO RESUELVAN!!!SALUDOS Y AYUDENME Date: Sat, 21 Nov 2009 14:38:59 +1000 From: b...@netspeed.com.au To: ath9k-devel@lists.ath9k.org Subject: Re: [ath9k-devel] Kernel config for eepc Luis, as an addendum to this I am using suse 11.2 on an eeepc. 2.6.32-rc7-wl-1-desktop-W. When I boot using the original kernel and compile wireless testing it compiles ok. However, If I boot to the wireless-testing kernel(r6) then it does not compile. It complains about a preload file being missing, during the modules_install. I can rerun and get the exact message if you like. My wireless network appears to be working fine using 11g. I have not been able to get 11n yet. Would you like a copy of my config? Thanks, Brian On Fri, 20 Nov 2009 12:34:32 -0800 Luis R. Rodriguez mcg...@gmail.com wrote: Sam, should we use the Ubuntu karmic config to test against the eepc or are there some tweaks on the config you might be aware of. Thanks, Luis ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel _ No salgas de tu casa sin saber cómo va a estar el clima. Revísalo antes en MSN. http://tiempo.cl.msn.com/___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
