Re: [ath9k-devel] Ath9k installation help

hi, On Wed, Apr 11, 2012 at 3:03 AM, Kareem Khalil wrote: > I'm running linux mint from my usb and I'm trying to install the ath9k > driver. After downloading it, I try to type in the commands that are posted > on the linux site but it keeps saying file does not exist. Is there another > way to i

Re: [ath9k-devel] Is there a way to tell if an antenna is connected?

Hi Ben/Adrian, On Wed, Apr 11, 2012 at 2:31 AM, Adrian Chadd wrote: > On 10 April 2012 10:11, Ben Greear wrote: >> Any register to query or other way to tell if an antenna is >> actually connected to the NIC?  I'd like to be able to warn >> users if the connector pops off for whatever reason...

Re: [ath9k-devel] DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02000020 DMADBG_7=0x00006400

On 04/10/2012 02:59 PM, Adrian Chadd wrote: > Ok. Lets get it upstream so we can get more debugging from userd. > > Same deal for ps issues- they may show up as mac-access-while-sleep > interrupts. I'm working on merging all my wifi/ath9k patches into wireless-testing now. It seems little or non

Re: [ath9k-devel] DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02000020 DMADBG_7=0x00006400

Ok. Lets get it upstream so we can get more debugging from userd. Same deal for ps issues- they may show up as mac-access-while-sleep interrupts. Adrian Sent from my Palm Pre on AT&T On Apr 10, 2012 2:35 PM, Ben Greear wrote: On 04/10/2012 01:59 PM, Adrian Chadd wro

[ath9k-devel] Ath9k installation help

I'm running linux mint from my usb and I'm trying to install the ath9k driver. After downloading it, I try to type in the commands that are posted on the linux site but it keeps saying file does not exist. Is there another way to install the driver other than typing commands in the terminal or am I

Re: [ath9k-devel] DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02000020 DMADBG_7=0x00006400

On 04/10/2012 01:59 PM, Adrian Chadd wrote: > Ben, > > Have your interrupt statistics patches made it into upstream yet? > > I'd like to see if he sees any bus errors. No idea, but my 3.3 tree has it and the rest of my stats related patches: http://dmz2.candelatech.com/git/gitweb.cgi Thanks, Ben

Re: [ath9k-devel] Is there a way to tell if an antenna is connected?

On 10 April 2012 10:11, Ben Greear wrote: > Any register to query or other way to tell if an antenna is > actually connected to the NIC?  I'd like to be able to warn > users if the connector pops off for whatever reason... Not that I know of. I'd look at the NF sample readings and if they're too

Re: [ath9k-devel] DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02000020 DMADBG_7=0x00006400

Ben, Have your interrupt statistics patches made it into upstream yet? I'd like to see if he sees any bus errors. Adrian ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel

[ath9k-devel] Is there a way to tell if an antenna is connected?

Any register to query or other way to tell if an antenna is actually connected to the NIC? I'd like to be able to warn users if the connector pops off for whatever reason... Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com

Re: [ath9k-devel] DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02000020 DMADBG_7=0x00006400

On 04/10/2012 04:01 AM, Fredrik Karlsson wrote: > I have a problem on ar9330 on 3.2.13 where the AP quite frequently stops > responding and the driver spits out the following message, > > ath: DMA failed to stop in 10 ms AR_CR=0x0024 AR_DIAG_SW=0x0220 > DMADBG_7=0x6400 > ath: Could not

Re: [ath9k-devel] DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02000020 DMADBG_7=0x00006400

Fredrik Karlsson wrote: > I have a problem on ar9330 on 3.2.13 where the AP quite frequently stops > responding and the driver spits out the following message, > > ath: DMA failed to stop in 10 ms AR_CR=0x0024 AR_DIAG_SW=0x0220 > DMADBG_7=0x6400 > ath: Could not stop RX, we could be co

[ath9k-devel] [RFC 1/1] cfg80211: have consistent checks for adding new entries in scan list

From: Mohammed Shafi Shajakhan *decide to traverse the RB tree in right - if the center frequency of new scan list entry is greater than the already available entries - if the IE length of new scan list entry is greater than the already available entries this

[ath9k-devel] [WIP 11/11] ath9k: do not disable hardware while wow is enabled

From: Mohammed Shafi Shajakhan Signed-off-by: Mohammed Shafi Shajakhan --- drivers/net/wireless/ath/ath9k/pci.c |3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) diff --git a/drivers/net/wireless/ath/ath9k/pci.c b/drivers/net/wireless/ath/ath9k/pci.c index 9b25299..32608ea 100644 -

[ath9k-devel] [WIP 10/11] ath9k: Add debug messages for WoW

From: Mohammed Shafi Shajakhan add sufficient debug messages in the driver for debugging WoW Signed-off-by: Mohammed Shafi Shajakhan --- drivers/net/wireless/ath/ath9k/main.c | 91 + 1 files changed, 80 insertions(+), 11 deletions(-) diff --git a/drivers/net/

[ath9k-devel] [WIP 09/11] ath: Add Wake-on-Wireless debug mask

From: Mohammed Shafi Shajakhan to help the developers and users to debug/know whats happening with WoW Signed-off-by: Mohammed Shafi Shajakhan --- drivers/net/wireless/ath/ath.h |2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) diff --git a/drivers/net/wireless/ath/ath.h b/drivers/n

[ath9k-devel] [WIP 08/11] ath9k: Add WoW related mac80211 callbacks

From: Mohammed Shafi Shajakhan add suspend/resume/set_wakeup callbacks to the driver *suspend - bail out only if all the conditions for configuring WoW is fine, currently multivif case is not handled - check for associated state - map wow triggers from user space data - add deauth/disassoc pa

[ath9k-devel] [WIP 07/11] ath9k_hw: Add hardware code for WoW

From: Mohammed Shafi Shajakhan add a new file wow.c which takes care of the hardware code for WoW. *program the descriptors and data words to periodically send Keep Alive Frames. *program the user defined patterns/masks and pattern length in the hardware registers. *'ath9k_hw_wow_enable' is call

[ath9k-devel] [WIP 06/11] ath9k_hw: INI changes for WoW for AR9002 chipsets

From: Mohammed Shafi Shajakhan for AR9002 family of chipsets and for WoW sleep, we reprogram the SerDes so that the PLL and CHK REQ are both enabled. this uses more power but in certain cases this is required as otherwise WoW sleep is unstable and chip may disappear. Signed-off-by: Luis R. Rodri

[ath9k-devel] [WIP 05/11] ath9k: advertise supported WoW flags to upper layer

From: Mohammed Shafi Shajakhan currently the code supports WoW triggers due to *magic packet *user defined patterns *deauth and disassoc patterns *disconnect - beacon miss, last beacon received timeout, no ack for keeep alive frames. we need to support other WoW offload features in the near futu

[ath9k-devel] [WIP 04/11] ath9k_hw: advertise WoW support for capable chipsets

From: Mohammed Shafi Shajakhan support WoW for all chipsets starting from AR9280, AR9285, AR9287, AR9380, AR9382, AR9485, AR9462. Really all hardware may not support WoW even though the flag is set and the WoW working depends on your laptop, BIOS apart from the hardware. Signed-off-by: Luis R. R

[ath9k-devel] [WIP 03/11] ath9k_hw: Add WoW hardware capability flags

From: Mohammed Shafi Shajakhan have seperate wow capability flags for *basic wow support *device capable of matching exact user defined pattern or de-authentication/disassoc pattern *device such AR9280 requires first four bytest for all sort of patterns Signed-off-by: Luis R. Rodriguez Signed-o

[ath9k-devel] [WIP 02/11] ath9k: Add definitions and structures to support WoW

From: Mohammed Shafi Shajakhan *add structures, macros and variables for WoW, so that the driver can make use of it. *maintain a list for user enabled patterns and masks *track pattern slots for the hardware limitation on the maximum number of patterns that can be stored. *track interrupts enable

[ath9k-devel] [WIP 01/11] ath9k_hw: Add register definitions for WoW support

From: Mohammed Shafi Shajakhan *MAC WoW registers back-off shift, MAC interrupt enable, magic packet enable, pattern match enable, aifs, slot wait period, keep alive frame failure count, beacon fail enable, beacon timeout, keep alive timeout, auto keep alive disable, keep alive fail disable and

[ath9k-devel] [WIP 00/11] Add support for Wake on Wireless

From: Mohammed Shafi Shajakhan *this patch set adds initial code support for WoW in ath9k, offloading features of WoW is not yet added. *this had to be completely tested, its not working currently and there are few known issues that need to be addressed. thanks to "Russell Hu" "Aeolus Yang"

Re: [ath9k-devel] [RFC] ath9k_hw: precedence bug in ath9k_hw_set_ofdm_nil()

On Tue, Apr 10, 2012 at 01:57:25PM +0300, Dan Carpenter wrote: > On Tue, Apr 10, 2012 at 11:58:26AM +0200, Felix Fietkau wrote: > > > if ((aniState->noiseFloor >= aniState->rssiThrHigh) && > > > - (!aniState->ofdmWeakSigDetectOff != > > > + (aniState->ofdmWeakSigDetectOff != > > Looking a

[ath9k-devel] DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02000020 DMADBG_7=0x00006400

I have a problem on ar9330 on 3.2.13 where the AP quite frequently stops responding and the driver spits out the following message, ath: DMA failed to stop in 10 ms AR_CR=0x0024 AR_DIAG_SW=0x0220 DMADBG_7=0x6400 ath: Could not stop RX, we could be confusing the DMA engine when we start

[ath9k-devel] [PATCH] ath9k: remove dead code

Clean up some orphaned code lines containing * unused variables (not referenced / write-only) * non-implemented function prototypes Signed-off-by: Zefir Kurtisi --- drivers/net/wireless/ath/ath9k/ar5008_phy.c|1 - drivers/net/wireless/ath/ath9k/ar9002_phy.c|1 - drivers/net/wirel

Re: [ath9k-devel] [RFC] ath9k_hw: precedence bug in ath9k_hw_set_ofdm_nil()

On Tue, Apr 10, 2012 at 11:58:26AM +0200, Felix Fietkau wrote: > > if ((aniState->noiseFloor >= aniState->rssiThrHigh) && > > - (!aniState->ofdmWeakSigDetectOff != > > + (aniState->ofdmWeakSigDetectOff != > Looking at other Atheros code, I think this patch is wrong, it should > be:

Re: [ath9k-devel] [PATCH 1/3] ath9k: add DFS pattern detector

On 04/06/2012 01:35 AM, Adrian Chadd wrote: > [top post] > > I think this is a good starting point. Let's aim to get this into the > tree and then start working on some further testing and debugging > APIs. > > Thanks so much for working on this! > > > > Adrian > Thanks for looking at it, Adr

Re: [ath9k-devel] 3.4-rc ath9k regression (Re: 3.3.1 ath9k regression)

Hi Michael, revert patch is sent by Sujith http://comments.gmane.org/gmane.linux.kernel.wireless.general/88543 got to fix unassociated idle case power save. -- thanks, shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.o

Re: [ath9k-devel] [RFC] ath9k_hw: precedence bug in ath9k_hw_set_ofdm_nil()

On 2012-04-10 11:04 AM, Dan Carpenter wrote: > This was introduced in 54da20d83f "ath9k_hw: improve ANI processing and > rx desensitizing parameters". It triggers a Smatch complaint because > the "if (!x != y) { ..." formation is a common precedence error. > > In this case, maybe the code was int

[ath9k-devel] [RFC] ath9k_hw: precedence bug in ath9k_hw_set_ofdm_nil()

This was introduced in 54da20d83f "ath9k_hw: improve ANI processing and rx desensitizing parameters". It triggers a Smatch complaint because the "if (!x != y) { ..." formation is a common precedence error. In this case, maybe the code was intended to be as it is. The "->ofdmWeakSigDetectOff" and