AR9330 and most likely other chips like AR9285 seem to get stuck completely
after they worked a long period of time in special environments. It is
currently unknown which parameters causes this problem.
Symptom of these stuck is the exposure of 0xdeadbeef through different hardware
registers. An i
On 2012-09-14 11:47 AM, Sven Eckelmann wrote:
> AR9330 and most likely other chips like AR9285 seem to get stuck completely
> after they worked a long period of time in special environments. It is
> currently unknown which parameters causes this problem.
>
> Symptom of these stuck is the exposure
From: Mohammed Shafi Shajakhan
Update the 'hw_timer_enabled' to 'false' wherever we are stopping
hardware generic timers, excecpt the case where we start them
again immediately.
Signed-off-by: Mohammed Shafi Shajakhan
---
drivers/net/wireless/ath/ath9k/gpio.c | 14 +-
1 files cha
From: Mohammed Shafi Shajakhan
We need to have the promiscus mode enabled for older
chipset(ie rule out many frames being filtered in the
hardware itself)if 'FIF_OTHER_BSS' flag is set, when we
start the mesh mode. Fix this by enabling promiscus
mode for all chipsets whose macversion <= AR9160
ch
From: Thomas Wagner
We need to have the promiscus mode enabled for older
chipsets(i.e, rule out many frames being filtered in the
hardware itself) if 'FIF_OTHER_BSS' flag is set, when we
start the mesh mode. Fix this by enabling promiscus
mode for all the chipsets whose macversion <= AR9160
chips
On Friday 14 September 2012 08:16 PM, Mohammed Shafi Shajakhan wrote:
> From: Mohammed Shafi Shajakhan
>
> We need to have the promiscus mode enabled for older
> chipset(ie rule out many frames being filtered in the
> hardware itself)if 'FIF_OTHER_BSS' flag is set, when we
> start the mesh mode. F
On 2012-09-14 4:49 PM, Mohammed Shafi Shajakhan wrote:
> From: Thomas Wagner
>
> We need to have the promiscus mode enabled for older
> chipsets(i.e, rule out many frames being filtered in the
> hardware itself) if 'FIF_OTHER_BSS' flag is set, when we
> start the mesh mode. Fix this by enabling p
Hi,
> I'm really not sure about this being tied to sc->nvifs.
> If it's mesh related, how about just adding a check for the number of mesh
> interfaces [...]
No, it is not mesh related!
Several frames where filtered out.
I discovered this on trying to set up a mesh.
But the where filtered frames
Greetings,
I'm using a TP-Link WN822N v2 (ath9k_htc) as an AP with
compat-wireless-3.6-rc5-1, hostapd v1.0 and iw version 3.6.
Values as displayed by osx on the client: Transmit Rate: 130, MCS Index: 15
As you can see bi-directional iperf transfer is almost equal.
So tx bitrate displayed by iw on
