ath10k and QCA3977 - random transfer rate losses

[Tobias Predel]

Hello vagner,

I'm sorry but I don't believe that I can tell a solution instantly :(

But nevertheless that makes me wonder since the bluetooth of my model 
doesn't require additional files for Bluetooth - works 'out of the box'. 

On my Arch Linux I had to enable and start the systemd service Bluetooth (starts
the Bluez bluetoothd daemon) and load the btusb kernel module with 
# modprobe btusb

Maybe it's (also) soft blocked by rfkill?
# rfkill unblock bluetooth 
should then help, after that Bluetooth may appear in NetworkManager applet again.

In the bluetooth driver packages for Windows there are files named 
ramps_0x**********_**_*****.dfu, AtherosBT.bin and AthrBT_0x******.dfu.
But most of these files are firmware updates files that can be written
to the chipset with the dfu-util. I don't think that they are 
really needed for this (just for information). 

You may post the message buffer of the kernel with 'dmesg'? Maybe
much more skilled people than me can help. I'll try my best :)

Best regards,
Tobias

On Mon, Feb 22, 2016 at 11:12:55AM +0200, vagner_ wrote:
> Hi Tobias,
> 
> Do you think that aplying the right board.bin makes the Bluetooth work
> properly?
> My wireless card
> 
> Network controller: Qualcomm Atheros Device 0042 (rev 30)
> 
> Has got bluethooth capabilities, but does not work. On boot time it
> complains about a file called ranpatch (...).bin related to it  :(
> 
> ++++++++++++++++++++++++++++++++++++++++++
> 
> On 02/21/2016 11:54 PM, Tobias Predel wrote:
> >Hello Adrian,
> >
> >bug report can be found here <https://bugzilla.kernel.org/show_bug.cgi?id=112451#c10>
> >I added other firmware files. I don't know any other place.
> >
> >Tobias
> >
> >On Sun, Feb 21, 2016 at 11:25:52AM -0800, Adrian Chadd wrote:
> >>ok, well, we should file a bug report so this isn't forgotten.
> >>
> >>Where's the right place to create bug reports? is there an ath10k
> >>staging branch in github somewhere? or bugzilla.kernel.org ?
> >>
> >>
> >>-a
> >>
> >>
> >>On 21 February 2016 at 11:20, Tobias Predel <tobias.predel at gmail.com> wrote:
> >>>Yes. I confirm full functionality now.
> >>>
> >>>On Sun, Feb 21, 2016 at 10:33:26AM -0800, Adrian Chadd wrote:
> >>>>Right, so just to be clear - it's just the board file updates that
> >>>>make it all work fine?
> >>>>
> >>>>
> >>>>-a
> >>>>
> >>>>
> >>>>On 21 February 2016 at 06:44, Tobias Predel <tobias.predel at gmail.com> wrote:
> >>>>>Hello again,
> >>>>>
> >>>>>one last word about the the board files:
> >>>>>
> >>>>>I extracted the board files from an AsusTek Windows Driver installer
> >>>>>that included the Qualcomm driver files for diverse variants of QCA9377
> >>>>>built in Samsung, Asus (Askey), Acer, Lenovo notebooks.
> >>>>>
> >>>>>An archive with all these files can be found at the comment 10 of my bug report
> >>>>><https://bugzilla.kernel.org/show_bug.cgi?id=112451#c10>
> >>>>>including board files (eeprom_*.bin) for NFA425, NFA435 (A), NFA455.
> >>>>>
> >>>>>If some people experience trouble, those might look at the netathr10x.inf
> >>>>>to find out which eeprom board file is needed or try out by installing
> >>>>>it to /lib/firmware/ath10k/QCA9377/hw1.0/board.bin.
> >>>>>
> >>>>>Those board files are using api 1 and must be named board.bin.
> >>>>>firmware-5.bin is still to be pulled from kvalo's github repo.
> >>>>>
> >>>>>Thank you to all for your support. I wish the best!
> >>>>>
> >>>>>Tobias
> >>>>>
> >>>>>
> >>>>>On Fri, Feb 19, 2016 at 05:55:26PM +0000, Hsu, Ryan wrote:
> >>>>>>Glad that help!
> >>>>>>
> >>>>>>I've cc that file to Kalle, hope we can see that get merged soon.
> >>>>>>
> >>>>>>Ryan
> >>>>>>
> >>>>>>>-----Original Message-----
> >>>>>>>From: Tobias Predel [mailto:tobias.predel at gmail.com]
> >>>>>>>Sent: Friday, February 19, 2016 09:23 AM
> >>>>>>>To: Adrian Chadd
> >>>>>>>Cc: Hsu, Ryan; ath10k at lists.infradead.org; vagner_
> >>>>>>>Subject: Re: ath10k and QCA3977 - random transfer rate losses
> >>>>>>>
> >>>>>>>On Fri, Feb 19, 2016 at 08:07:49AM -0800, Adrian Chadd wrote:
> >>>>>>>>Ok, so it's a board file problem? this can be solved by telling kvalo@
> >>>>>>>>about it, right?
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>-a
> >>>>>>>Yes, they differ and the board-2.bin file isn't included neither in linux-
> >>>>>>>firmware nor in kvalo's repository.
> >>>>>>>
> >>>>>>>MD5 checksums:
> >>>>>>>73cca12b9398f0cecaa3cfa35c8961b7  board-2.bin
> >>>>>>>44349f6ae93cf9ceffb164f58d4fb124  board.bin
> >>>>>>>
> >>>>>>>I'll try to contact him and send the board file.
> >>>>>>>
> >>>>>>>Tobias
>