Re: QCA6174 hw2.1?

2015-04-26 Thread Gabriele Martino
Hi Corin, the dissect.py script seems to work better than the disassemble.py: [ 6483.455435] ath10k_pci :03:00.0: pci irq msi-x interrupts 8 irq_mode 0 reset_mode 0 [ 6483.600747] ath10k_pci :03:00.0: Direct firmware load for ath10k/cal-pci-:03:00.0.bin failed with error -2 [

Re: attempting mesh on ath10k

2015-04-26 Thread Bob Copeland
On Fri, Apr 24, 2015 at 06:38:02PM -0700, Ben Greear wrote: I have IBSS support working, and at least non-encrypted raw transmit can work in my firmware, though raw tx requires Michal's RFC patch he posted some time ago. (Michal's RFC patch is in my repo.) So I got a bit further. I was still

Re: QCA6174 hw2.1?

2015-04-26 Thread Gabriele Martino
Just tried the kvalo's kernel. NetworkManager connected flawlessly at boot to my WPA2 home network on 2.4GHz. Will try 5GHz later. iwconfig reports a fixed 1Mb/s bitrate, but I can copy files to my nas (smb share) at about 3.3MB/s. That's a reasonable speed for b/g wireless. iwconfig: wlp3s0

Tips to debug Firmware crash

2015-04-26 Thread Venkat Ch
Hi All, I am an active developer of Atheros drivers for the last 10 years. I have been working on QCA 10.2.2 driver for the last few months and trying to understand the architecture of this offloading model. Though this forum is nothing to do with Atheros provided drivers, I took the liberty of

Re: First QCA6174 firmware release

2015-04-26 Thread Michal Kazior
On 25 April 2015 at 20:22, Oscar Rydberg oscarrydb...@gmail.com wrote: Olaf Dreyer olaf at dreyero.de writes: I have a new Acer Aspire VN7-591 Laptop with a Qualcom Atheros QCNF344 wireless chip, which is shown by lspci as: Qualcomm Atheros Device 003e (rev 20) Subsystem: Foxconn

Re: Ath10 Firmware

2015-04-26 Thread Michal Kazior
On 25 April 2015 at 11:14, Sunder Kumaresan sunder.kumare...@aricent.com wrote: Hi, Will Ath10 firmware work for big endian processor ? is it endian agnostic ? It works for little endian processor. You probably mean ath10k driver - not firmware. Firmware is run on the device chip itself