On 2015-08-06 20:45, Peter Oh wrote:
On 08/06/2015 12:59 AM, Felix Fietkau wrote:
On 2015-08-06 09:43, Vasanthakumar Thiagarajan wrote:
On Wednesday 05 August 2015 05:51 PM, Felix Fietkau wrote:
On 2015-07-21 13:36, Vasanthakumar Thiagarajan wrote:
Add vendor/device id of QCA99X0 V2.0 to
On 6 August 2015 at 16:42, Lapo Calamandrei calamand...@gmail.com wrote:
Hi Michal, first of all thank you for your time. So, looks like the
patch provided makes no difference [to me], attached the dmesg output
with and without the patch applied against a fresh checkout.
This is weird. I'm
Once HTT Tx queue got full offchannel queue was
stopped and never woken up again. This broke, e.g.
P2P. This could be reproduced after running a lot
of traffic enough to saturate 100% of the driver
Tx queue and then trying to send offchannel
traffic.
Fixes: 96d828d45e16 (ath10k: rework tx queue
In case someone has time an interest, I would be curious if upstream
firmware/kernels see this problem. Unfortunately, it takes a bit of
setup to do this test (namely, constant tx source, and if doing this with
something like ath9k, then you might need a variable attenuator).
Possibly just a
Still get a firmware crash after 'boot hif start', but different
behaviour this time. Here is the dmesg output:
[6.058379] ath10k_pci :02:00.0: pci probe
[6.058933] ath10k_pci :02:00.0: boot pci_mem 0xc90002c0
[6.060960] ath10k_pci :02:00.0: pci irq msi-x
On 08/06/2015 12:59 AM, Felix Fietkau wrote:
On 2015-08-06 09:43, Vasanthakumar Thiagarajan wrote:
On Wednesday 05 August 2015 05:51 PM, Felix Fietkau wrote:
On 2015-07-21 13:36, Vasanthakumar Thiagarajan wrote:
Add vendor/device id of QCA99X0 V2.0 to pci id table and
On 2015-08-06 09:43, Vasanthakumar Thiagarajan wrote:
On Wednesday 05 August 2015 05:51 PM, Felix Fietkau wrote:
On 2015-07-21 13:36, Vasanthakumar Thiagarajan wrote:
Add vendor/device id of QCA99X0 V2.0 to pci id table and
QCA99X0_HW_2_0_CHIP_ID_REV to ath10k_pci_supp_chips[] for
QCA99X0 to
Hi Michal, first of all thank you for your time. So, looks like the
patch provided makes no difference [to me], attached the dmesg output
with and without the patch applied against a fresh checkout.
Ciao
Lapo
2015-08-06 7:03 GMT+02:00 Michal Kazior michal.kaz...@tieto.com:
On 5 August 2015 at
...and this is the dmesg output with yesterday's build with the patch applied.
2015-08-06 15:52 GMT+02:00 Lapo Calamandrei calamand...@gmail.com:
Hi Michal, first of all thank you for your time. So, looks like the
patch provided makes no difference [to me], attached the dmesg output
with and
