Hi,
while I was testing testmode patches I noticed ath10k was crashing
during rmmod. Further investigation showed that I actually see the crash
also without testmode patches (using commit 346c16654356) . I just need
to reload ath10k modules in sequence, usually 10-15 times is enough to
reprocuce
We need this function to send wmi packets from testmode.c.
Signed-off-by: Kalle Valo kv...@qca.qualcomm.com
---
drivers/net/wireless/ath/ath10k/wmi.c |5 ++---
drivers/net/wireless/ath/ath10k/wmi.h |4
2 files changed, 6 insertions(+), 3 deletions(-)
diff --git
Michal Kazior michal.kaz...@tieto.com writes:
On 28 August 2014 08:58, Kalle Valo kv...@qca.qualcomm.com wrote:
[ 123.552499] Call Trace:
[ 123.554957] [fe576c1b] ath10k_pci_tasklet+0x1b/0x60 [ath10k_pci]
[ 123.557436] [c1053fbe] tasklet_action+0x9e/0xb0
[ 123.559874] [c10534f1]
Hi,
This cleans up the monitor code a bit and
introduces a workaround for a fw bug (leading to a
fw crash) when station interface associates while
a monitor vdev is running.
People have been complaining about the fw crash
for some time now. I guess we have no choice but
to make a workaround in
This makes it easier to log and debug via tracing
with more than 1 ath10k device on a system.
Signed-off-by: Michal Kazior michal.kaz...@tieto.com
---
Not sure if pulling core.h in trace.h and using ar
pointer is the best approach here. Alternative is
to not pull core.h and pass ar-dev directly
Hi,
as always after a merge window, I have rebased ath.git master branch to
3.17.0-rc2-wl-ath. So please be careful when updating it.
--
Kalle Valo
___
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
Michal Kazior michal.kaz...@tieto.com writes:
This makes it easier to log and debug via tracing
with more than 1 ath10k device on a system.
Signed-off-by: Michal Kazior michal.kaz...@tieto.com
In ath-next-test I had a simple conflict in wmi.c. Please check my
conflict resolution:
