On Wed, May 16, 2018 at 07:28:21PM +0200, Erik Stromdahl wrote:
> Hello Niklas
>
> Quick question:
> Are you using my patch: "ath10k: add htt_tx num_pending window"?
Nope, but I definitely think that your patch should be merged,
since the current code can lock/unlock/lock a lot of times for
no
On Thu, 17 May 2018 at 16:16, Niklas Cassel
wrote:
> diff --git a/drivers/net/wireless/ath/ath10k/txrx.c
b/drivers/net/wireless/ath/ath10k/txrx.c
> index cda164f6e9f6..1d3b2d2c3fee 100644
> --- a/drivers/net/wireless/ath/ath10k/txrx.c
> +++
The following problem was observed when running iperf:
[ 3] 0.0- 1.0 sec 2.00 MBytes 16.8 Mbits/sec
[ 3] 1.0- 2.0 sec 3.12 MBytes 26.2 Mbits/sec
[ 3] 2.0- 3.0 sec 3.25 MBytes 27.3 Mbits/sec
[ 3] 3.0- 4.0 sec 655 KBytes 5.36 Mbits/sec
[ 3] 4.0- 5.0 sec 0.00 Bytes 0.00 bits/sec
Hi Jay,
On 05/16/2018 10:00 PM, Jay Foster wrote:
Other issues that I have observed (probably FW related):
1) In STA mode, I observe several messages from the driver "received tx completion
for invalid msdu_id: 0". A Google search led me to
https://github.com/erstrom/linux-ath/issues/1, but