On 2015-01-16 09:00, Rico Derrer wrote:
Hi Felix
Felix Fietkau wrote:
diff --git a/drivers/net/wireless/ath/ath9k/main.c
b/drivers/net/wireless/ath/ath9k/main.c
index 9a72640..62b0bf4 100644
--- a/drivers/net/wireless/ath/ath9k/main.c
+++ b/drivers/net/wireless/ath/ath9k/main.c
@@
Felix Fietkau n...@openwrt.org writes:
To fix invalid hardware accesses, the commit
ath9k: do not access hardware on IRQs during reset made the irq
handler ignore interrupts emitted after queueing a hardware reset (which
disables the IRQ). This left a small time window for the IRQ to get
Rico Derrer rico.der...@neratec.com writes:
This part completely blocks the system on a AR9350. Loading the
module works but configuring it hangs the system until watchdog
restarts it.
What kernel/software are you running on there? When I committed this
patch to OpenWrt, it uncovered IRQ
Hi Felix
Felix Fietkau wrote:
diff --git a/drivers/net/wireless/ath/ath9k/main.c
b/drivers/net/wireless/ath/ath9k/main.c
index 9a72640..62b0bf4 100644
--- a/drivers/net/wireless/ath/ath9k/main.c
+++ b/drivers/net/wireless/ath/ath9k/main.c
@@ -285,6 +285,7 @@ static int
Felix Fietkau wrote:
To fix invalid hardware accesses, the commit
ath9k: do not access hardware on IRQs during reset made the irq
handler ignore interrupts emitted after queueing a hardware reset (which
disables the IRQ). This left a small time window for the IRQ to get
re-enabled by the
On 2015-01-15 10:09, Sujith Manoharan wrote:
Felix Fietkau wrote:
To fix invalid hardware accesses, the commit
ath9k: do not access hardware on IRQs during reset made the irq
handler ignore interrupts emitted after queueing a hardware reset (which
disables the IRQ). This left a small time
