Re: [ath9k-devel] Tplink TL-WN822N drops out connections randomly on Arch Linux with Kernel 3.9.4 (Mark Lee)
On 3 June 2013 11:44, Mark E. Lee wrote: > I couldn't find hostapd.conf on my access point. > > I did however switch the algorithm from WPA2 to WEP and found that I no > longer lost connection during skype calls. That kinda points at the rekey or the crypto handling in general. Please find and enable hostapd logging on your AP. I've seen and fixed bugs in freebsd recently where traffic would fill up buffers and cause the EAPOL rekey packets to get discarded by the driver. Thus a group rekey would fail, and the unit would be disconnected. adrian ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
[ath9k-devel] So long, and thanks for all the fish (kinda)
Hi all, This Friday will be my last day at Qualcomm Atheros. I've enjoyed working with the extremely bright and driven engineers and designers that make the wireless chips and SoCs that people everywhere take for granted. I've achieved a bunch of goals both with their internal product development and open source. But now it's time to move onto different things. I'd especially like to thank Luis Rodriguez for introducing me to the QCA folk and helping me get access to the Atheros open source project, as well as the follow-up discussions that led to me being hired. The open source wireless community has been driving innovation in a lot of areas for a number of years. I'd like to hope that I've had a small, positive effect on that. I wish you all the best of luck in pushing forward and continuing to innovate. Now, I'm still NDA-enabled and I quite like hacking on this wireless stuff so I won't be quitting hacking on things. I will just have other things on my mind. Good luck to you all! Adrian ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] Tplink TL-WN822N drops out connections randomly on Arch Linux with Kernel 3.9.4 (Mark Lee)
I couldn't find hostapd.conf on my access point. I did however switch the algorithm from WPA2 to WEP and found that I no longer lost connection during skype calls. -- Mark E. Lee signature.asc Description: This is a digitally signed message part ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] AR9287; WiFi AP Mode - Increase interbeacon duration of 100ms
On 06/03/2013 03:15 AM, sandeep suresh wrote: > Hello All, > Gentle reminder; really will be greatful, if you can give me some > directions on this, Please. > Regards > Sandeep > > *From:* sandeep suresh > *To:* Adrian Chadd ; ath9k-devel > > *Cc:* "linux-wirel...@vger.kernel.org" > *Sent:* Monday, 27 May 2013 1:40 PM > *Subject:* AR9287; WiFi AP Mode - Increase interbeacon duration of 100ms > > Hello All, > This is regarding the inter beacon timing for AR9287 WiFi module when > configured in WiFi Access Point mode. In this mode, the beacons are generated > every > 100ms by the WiFi AP. I have the following questions: > 1. As per documentation available on the internet, the minimum inter beacon > timing is 100ms. But can we increase the the inter beacon timing above this > value? > say 250ms, 500ms etc > 2. As per standard, does increase in inter beacon time > 100ms, have any > impact on the WiFi Clients connected to AR9287 WiFi AP? Even though I might > test with > some WiFi clients without any side effects but there may be some WiFi clients > (which I might be unaware of )that might not work. > 3. Has anyone attempted to do this? Please let me know if you have any > observations on this? We have been using a default of 250ms beacon timer for years in our ath9k APs. Seems to work just fine, but we mostly use them for internal testing with other ath9k systems acting as the stations. Thanks, Ben > Thanks & regards > Sandeep > > > > > ___ > ath9k-devel mailing list > ath9k-devel@lists.ath9k.org > https://lists.ath9k.org/mailman/listinfo/ath9k-devel > -- Ben Greear Candela Technologies Inc http://www.candelatech.com ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] [PATCH 7/7] ath10k: detect htt pending tx limit at runtime
On 2013-05-16 11:09 AM, Michal Kazior wrote: > The real limit for sending htt tx is either > msdu_id storage type (u16 - 65536 different > values) or the HIF tx pipe queue length (2047 in > case of our PCI HIF). > > The htt tx pipe does not use interrupts - it must > be polled. It is polled either on RX > unconditionally or on TX if HIF tx pipe has used > over 50% of the resources. > > With this patch we should finally trigger the TX > polling properly. What this really means we should > have a smoother tx. Not because the tx limit is > greater, but simply because we'll be triggering > the polling properly in case of heavy tx. > > Signed-off-by: Michal Kazior I think a queue length of 2047 is completely excessive. It causes way too much buffering and latency under load, and I suspect it may be significantly hurting TCP throughput as well (if TCP manages to get the queue filled up). As long as there is no way to dynamically determine a *reasonable* queue size, introducing an arbitrary limit is *much* better than just letting the firmware gobble up as much as it wants. For reference: ath9k limits the number of pending tx packets to 128 per WMM queue, and even at the highest MCS rates with 3x3 and HT40 this is much more than what's actually needed. - Felix ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] AR9287; WiFi AP Mode - Increase interbeacon duration of 100ms
Hello All, Gentle reminder; really will be greatful, if you can give me some directions on this, Please. Regards Sandeep From: sandeep suresh To: Adrian Chadd ; ath9k-devel Cc: "linux-wirel...@vger.kernel.org" Sent: Monday, 27 May 2013 1:40 PM Subject: AR9287; WiFi AP Mode - Increase interbeacon duration of 100ms Hello All, This is regarding the inter beacon timing for AR9287 WiFi module when configured in WiFi Access Point mode. In this mode, the beacons are generated every 100ms by the WiFi AP. I have the following questions: 1. As per documentation available on the internet, the minimum inter beacon timing is 100ms. But can we increase the the inter beacon timing above this value? say 250ms, 500ms etc 2. As per standard, does increase in inter beacon time > 100ms, have any impact on the WiFi Clients connected to AR9287 WiFi AP? Even though I might test with some WiFi clients without any side effects but there may be some WiFi clients (which I might be unaware of )that might not work. 3. Has anyone attempted to do this? Please let me know if you have any observations on this? Thanks & regards Sandeep___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] [PATCH 0/2] ath9k: add STBC Rx flags (repost untill some one asnwers)
Am 03.06.2013 11:59, schrieb Sujith Manoharan: > Oleksij Rempel wrote: >> One more repost of old patches. I need, please, at least some kind of answer: >> "we don't wont patches from you" or "you are doing some thing wrong". > > Both the patches have already been merged in wireless-testing. ah... i didn't noticed that. thank you ;) > commit b0a1ae976d6cd40ff90ba87883e17eb2610dae3d > Author: Oleksij Rempel > Date: Fri May 24 20:30:59 2013 +0200 > > ath9k: check for Rx-STBC flag and pass it to ieee80211 > > This patch make use of STBC flag in DMA RX descriptor. > Only devices after ar9280 can provide this information. > > If card support it we will set HAVE_STBC flag, to show > clint programm thet STBC is supported but not received. > > Signed-off-by: Oleksij Rempel > Signed-off-by: John W. Linville > > commit ab276103357637fb26cc851369b5abbdc42afbf4 > Author: Oleksij Rempel > Date: Fri May 24 12:18:30 2013 +0200 > > ath9k: remove useless flag conversation. > > some flags used only outside of ath9k - In this case we can use > "enum mac80211_rx_flags" and pass it upstream without extra > conversation. > > Signed-off-by: Oleksij Rempel > Signed-off-by: John W. Linville > > Sujith > -- Regards, Oleksij ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] [PATCH 0/2] ath9k: add STBC Rx flags (repost untill some one asnwers)
Oleksij Rempel wrote: > One more repost of old patches. I need, please, at least some kind of answer: > "we don't wont patches from you" or "you are doing some thing wrong". Both the patches have already been merged in wireless-testing. commit b0a1ae976d6cd40ff90ba87883e17eb2610dae3d Author: Oleksij Rempel Date: Fri May 24 20:30:59 2013 +0200 ath9k: check for Rx-STBC flag and pass it to ieee80211 This patch make use of STBC flag in DMA RX descriptor. Only devices after ar9280 can provide this information. If card support it we will set HAVE_STBC flag, to show clint programm thet STBC is supported but not received. Signed-off-by: Oleksij Rempel Signed-off-by: John W. Linville commit ab276103357637fb26cc851369b5abbdc42afbf4 Author: Oleksij Rempel Date: Fri May 24 12:18:30 2013 +0200 ath9k: remove useless flag conversation. some flags used only outside of ath9k - In this case we can use "enum mac80211_rx_flags" and pass it upstream without extra conversation. Signed-off-by: Oleksij Rempel Signed-off-by: John W. Linville Sujith ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
[ath9k-devel] [PATCH 0/2] ath9k: add STBC Rx flags (repost untill some one asnwers)
One more repost of old patches. I need, please, at least some kind of answer: "we don't wont patches from you" or "you are doing some thing wrong". ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
[ath9k-devel] [PATCH 1/2] ath9k: remove useless flag conversation.
some flags used only outside of ath9k - In this case we can use
"enum mac80211_rx_flags" and pass it upstream without extra
conversation.
Signed-off-by: Oleksij Rempel
---
drivers/net/wireless/ath/ath9k/ar9003_mac.c | 5 +++--
drivers/net/wireless/ath/ath9k/mac.c| 11 +++
drivers/net/wireless/ath/ath9k/mac.h| 1 +
drivers/net/wireless/ath/ath9k/recv.c | 5 +
4 files changed, 12 insertions(+), 10 deletions(-)
diff --git a/drivers/net/wireless/ath/ath9k/ar9003_mac.c
b/drivers/net/wireless/ath/ath9k/ar9003_mac.c
index 301bf72..5163abd 100644
--- a/drivers/net/wireless/ath/ath9k/ar9003_mac.c
+++ b/drivers/net/wireless/ath/ath9k/ar9003_mac.c
@@ -469,6 +469,7 @@ int ath9k_hw_process_rxdesc_edma(struct ath_hw *ah, struct
ath_rx_status *rxs,
rxs->rs_status = 0;
rxs->rs_flags = 0;
+ rxs->flag = 0;
rxs->rs_datalen = rxsp->status2 & AR_DataLen;
rxs->rs_tstamp = rxsp->status3;
@@ -493,8 +494,8 @@ int ath9k_hw_process_rxdesc_edma(struct ath_hw *ah, struct
ath_rx_status *rxs,
rxs->rs_isaggr = (rxsp->status11 & AR_RxAggr) ? 1 : 0;
rxs->rs_moreaggr = (rxsp->status11 & AR_RxMoreAggr) ? 1 : 0;
rxs->rs_antenna = (MS(rxsp->status4, AR_RxAntenna) & 0x7);
- rxs->rs_flags = (rxsp->status4 & AR_GI) ? ATH9K_RX_GI : 0;
- rxs->rs_flags |= (rxsp->status4 & AR_2040) ? ATH9K_RX_2040 : 0;
+ rxs->flag |= (rxsp->status4 & AR_GI) ? RX_FLAG_SHORT_GI : 0;
+ rxs->flag |= (rxsp->status4 & AR_2040) ? RX_FLAG_40MHZ : 0;
rxs->evm0 = rxsp->status6;
rxs->evm1 = rxsp->status7;
diff --git a/drivers/net/wireless/ath/ath9k/mac.c
b/drivers/net/wireless/ath/ath9k/mac.c
index 498fee0..a52081d 100644
--- a/drivers/net/wireless/ath/ath9k/mac.c
+++ b/drivers/net/wireless/ath/ath9k/mac.c
@@ -547,6 +547,7 @@ int ath9k_hw_rxprocdesc(struct ath_hw *ah, struct ath_desc
*ds,
rs->rs_status = 0;
rs->rs_flags = 0;
+ rs->flag = 0;
rs->rs_datalen = ads.ds_rxstatus1 & AR_DataLen;
rs->rs_tstamp = ads.AR_RcvTimestamp;
@@ -586,10 +587,12 @@ int ath9k_hw_rxprocdesc(struct ath_hw *ah, struct
ath_desc *ds,
rs->rs_moreaggr =
(ads.ds_rxstatus8 & AR_RxMoreAggr) ? 1 : 0;
rs->rs_antenna = MS(ads.ds_rxstatus3, AR_RxAntenna);
- rs->rs_flags =
- (ads.ds_rxstatus3 & AR_GI) ? ATH9K_RX_GI : 0;
- rs->rs_flags |=
- (ads.ds_rxstatus3 & AR_2040) ? ATH9K_RX_2040 : 0;
+
+ /* directly mapped flags for ieee80211_rx_status */
+ rs->flag |=
+ (ads.ds_rxstatus3 & AR_GI) ? RX_FLAG_SHORT_GI : 0;
+ rs->flag |=
+ (ads.ds_rxstatus3 & AR_2040) ? RX_FLAG_40MHZ : 0;
if (ads.ds_rxstatus8 & AR_PreDelimCRCErr)
rs->rs_flags |= ATH9K_RX_DELIM_CRC_PRE;
diff --git a/drivers/net/wireless/ath/ath9k/mac.h
b/drivers/net/wireless/ath/ath9k/mac.h
index 5865f92..3f1e775 100644
--- a/drivers/net/wireless/ath/ath9k/mac.h
+++ b/drivers/net/wireless/ath/ath9k/mac.h
@@ -149,6 +149,7 @@ struct ath_rx_status {
u32 evm2;
u32 evm3;
u32 evm4;
+ u32 flag; /* see enum mac80211_rx_flags */
};
struct ath_htc_rx_status {
diff --git a/drivers/net/wireless/ath/ath9k/recv.c
b/drivers/net/wireless/ath/ath9k/recv.c
index 8be2b5d..b4b758d 100644
--- a/drivers/net/wireless/ath/ath9k/recv.c
+++ b/drivers/net/wireless/ath/ath9k/recv.c
@@ -868,10 +868,7 @@ static int ath9k_process_rate(struct ath_common *common,
if (rx_stats->rs_rate & 0x80) {
/* HT rate */
rxs->flag |= RX_FLAG_HT;
- if (rx_stats->rs_flags & ATH9K_RX_2040)
- rxs->flag |= RX_FLAG_40MHZ;
- if (rx_stats->rs_flags & ATH9K_RX_GI)
- rxs->flag |= RX_FLAG_SHORT_GI;
+ rxs->flag |= rx_stats->flag;
rxs->rate_idx = rx_stats->rs_rate & 0x7f;
return 0;
}
--
1.8.1.2
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
[ath9k-devel] [PATCH v4 2/2] ath9k: check for Rx-STBC flag and pass it to ieee80211
This patch make use of STBC flag in DMA RX descriptor.
Only devices after ar9280 can provide this information.
If card support it we will set HAVE_STBC flag, to show
clint programm thet STBC is supported but not received.
Signed-off-by: Oleksij Rempel
---
drivers/net/wireless/ath/ath9k/init.c | 10 --
drivers/net/wireless/ath/ath9k/mac.c | 5 +
drivers/net/wireless/ath/ath9k/mac.h | 3 ++-
3 files changed, 15 insertions(+), 3 deletions(-)
diff --git a/drivers/net/wireless/ath/ath9k/init.c
b/drivers/net/wireless/ath/ath9k/init.c
index aba4151..b9c97d4 100644
--- a/drivers/net/wireless/ath/ath9k/init.c
+++ b/drivers/net/wireless/ath/ath9k/init.c
@@ -21,6 +21,7 @@
#include
#include
#include
+#include
#include "ath9k.h"
@@ -769,8 +770,13 @@ void ath9k_set_hw_capab(struct ath_softc *sc, struct
ieee80211_hw *hw)
IEEE80211_HW_REPORTS_TX_ACK_STATUS |
IEEE80211_HW_SUPPORTS_RC_TABLE;
- if (sc->sc_ah->caps.hw_caps & ATH9K_HW_CAP_HT)
-hw->flags |= IEEE80211_HW_AMPDU_AGGREGATION;
+ if (sc->sc_ah->caps.hw_caps & ATH9K_HW_CAP_HT) {
+ hw->flags |= IEEE80211_HW_AMPDU_AGGREGATION;
+
+ if (AR_SREV_9280_20_OR_LATER(ah))
+ hw->radiotap_mcs_details |=
+ IEEE80211_RADIOTAP_MCS_HAVE_STBC;
+ }
if (AR_SREV_9160_10_OR_LATER(sc->sc_ah) || ath9k_modparam_nohwcrypt)
hw->flags |= IEEE80211_HW_MFP_CAPABLE;
diff --git a/drivers/net/wireless/ath/ath9k/mac.c
b/drivers/net/wireless/ath/ath9k/mac.c
index a52081d..d055e38 100644
--- a/drivers/net/wireless/ath/ath9k/mac.c
+++ b/drivers/net/wireless/ath/ath9k/mac.c
@@ -593,6 +593,11 @@ int ath9k_hw_rxprocdesc(struct ath_hw *ah, struct ath_desc
*ds,
(ads.ds_rxstatus3 & AR_GI) ? RX_FLAG_SHORT_GI : 0;
rs->flag |=
(ads.ds_rxstatus3 & AR_2040) ? RX_FLAG_40MHZ : 0;
+ if (AR_SREV_9280_20_OR_LATER(ah))
+ rs->flag |=
+ (ads.ds_rxstatus3 & AR_STBC) ?
+ /* we can only Nss=1 STBC */
+ (1 << RX_FLAG_STBC_SHIFT) : 0;
if (ads.ds_rxstatus8 & AR_PreDelimCRCErr)
rs->rs_flags |= ATH9K_RX_DELIM_CRC_PRE;
diff --git a/drivers/net/wireless/ath/ath9k/mac.h
b/drivers/net/wireless/ath/ath9k/mac.h
index 3f1e775..b02dfce 100644
--- a/drivers/net/wireless/ath/ath9k/mac.h
+++ b/drivers/net/wireless/ath/ath9k/mac.h
@@ -534,7 +534,8 @@ struct ar5416_desc {
#define AR_2040 0x0002
#define AR_Parallel40 0x0004
#define AR_Parallel40_S 2
-#define AR_RxStatusRsvd30 0x00f8
+#define AR_STBC 0x0008 /* on ar9280 and later */
+#define AR_RxStatusRsvd30 0x00f0
#define AR_RxAntenna 0xff00
#define AR_RxAntenna_S 8
--
1.8.1.2
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
