On Fr, 2016-08-19 at 13:03 +0300, Kalle Valo wrote:
> Actually, I see two patches which might be related but not identical:
>
> ath9k: fix client mode beacon configuration
> https://patchwork.kernel.org/patch/9247699/
>
> ath9k: Fix beacon configuration assertion failure
>
analysing the PHY errors for DFS if radar detection is enabled.
Signed-off-by: Mathias Kretschmer <mathias.kretsch...@fit.fraunhofer.de>
Signed-off-by: Benjamin Berg <benja...@sipsolutions.net>
Signed-off-by: Simon Wunderlich <s...@simonwunderlich.de>
---
drivers/net/wireless/ath/ath9k
From: Benjamin Berg <benjamin.b...@open-mesh.com>
These changes make ath9k_hw_reset more consistent with other places that
handle the TSF value by using the same helper routine.
A slight improvement is to not assume that a fixed time of 1.5ms has
passed for the initval writes when co
From: Benjamin Berg <benjamin.b...@open-mesh.com>
Beacons were not send out at (timestamp % beacon_time == 0) for interfaces
other than the primary one. To send out beacons with the correct timestamp
according to 10.1.3.2 of the 802.11 standard the tsf_adjustment has to be
set to the ne
From: Benjamin Berg <benjamin.b...@open-mesh.com>
The ath9k TSF handling routines need to be aware of the channel context that
is being modified. With this change the TSF related values that are stored
in each channel context will be correctly tracked and the harware will only
be u
From: Benjamin Berg <benjamin.b...@open-mesh.com>
This patch fixes some issues with interface reconfiguration. It could
for example happen that an AP interface in beacon slot 0 was removed
leaving an IBSS station in one of the other slots. When this happens
the driver never sends out the
From: Benjamin Berg <benjamin.b...@open-mesh.com>
The removed ATH9K_SLOT_TIME_X constants simply map the value in microseconds
to the same integer. These constants were not used consistently, so fix the
inconsistency issue by replacing all occurances with the integer equivalent.
Sign
From: Benjamin Berg <benjamin.b...@open-mesh.com>
Signed-off-by: Benjamin Berg <benjamin.b...@open-mesh.com>
---
drivers/net/wireless/ath/ath9k/main.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/net/wireless/ath/ath9k/main.c
b/drivers/net/wireless/ath/ath9k/
From: Benjamin Berg <benjamin.b...@open-mesh.com>
This patch fixes some issues with interface reconfiguration. It could
for example happen that an AP interface in beacon slot 0 was removed
leaving an IBSS station in one of the other slots.
This patch approaches these failures by reconfi
From: Benjamin Berg <benjamin.b...@open-mesh.com>
Not much of a change. Only small fix is that we don't assume that
exactly 1.5ms have passed for the second AR91xx SoC TSF setting.
Signed-off-by: Benjamin Berg <benjamin.b...@open-mesh.com>
---
drivers/net/wireless/ath/ath
From: Benjamin Berg <benjamin.b...@open-mesh.com>
Signed-off-by: Benjamin Berg <benjamin.b...@open-mesh.com>
---
drivers/net/wireless/ath/ath9k/main.c | 21 ++---
1 file changed, 18 insertions(+), 3 deletions(-)
diff --git a/drivers/net/wireless/ath/ath9k/main.c
b
From: Benjamin Berg <benjamin.b...@open-mesh.com>
Signed-off-by: Benjamin Berg <benjamin.b...@open-mesh.com>
---
drivers/net/wireless/ath/ath9k/main.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/net/wireless/ath/ath9k/main.c
b/drivers/net/wirele
On Di, 2015-08-04 at 16:33 -0400, Marty Faltesek wrote:
> We are seeing a hang on ath9k where traffic and beacons stops anywhere
> from a few minutes to half a day. Log output continues. With debug
> enabled, we see this during the hang:
>
> ath: phy0: tx hung, resetting the chip.
>
> The issue
analysing the PHY errors for DFS if radar detection is enabled.
Reported-by: Mathias Kretschmer mathias.kretsch...@fokus.fraunhofer.de
Signed-off-by: Benjamin Berg benja...@sipsolutions.net
Signed-off-by: Simon Wunderlich s...@simonwunderlich.de
[v3.19+]
---
The patch does apply to 3.19+ with a bit
On Fr, 2015-03-13 at 15:27 +0100, Felix Fietkau wrote:
I sent the following patch yesterday - I think it addresses the exact
same issue. Please test it to see if it works for you as well.
The patch looks a lot better. I just backported it and it is working
just fine for me.
Benjamin
been configured yet (or configuration is scheduled)
and allows the configuration in that case. This works around the issue
here, but I have no idea whether it is a sane solution.
Signed-off-by: Benjamin Berg benja...@sipsolutions.net
---
drivers/net/wireless/ath/ath9k/beacon.c | 3 ++-
1 file changed
Right now there is a bug where beaconing might not be enabled correctly
if the user has configuring multiple VIFs.
The issue surfaces if the userspace first creates the AP devices and
only then configures the first VIF (ath9k_bss_info_changed is called).
In this case the current
17 matches
Mail list logo
