During driver load below warn logs are printed in the console.
Since driver may not implement all wmi events sent by fw and
all of them are non-fatal, move this log to debug level to
remove un-necessary warn message on console.
[ 361.887230] ath10k_snoc a00.wifi: Unknown eventid: 16393
[
> > How can I make sure this is the case?
>
> ath10k prints lots of information to dmesg after it has initialised the
> device, so check that. You should see the firmware version and what api
> is used (the number N from firmware-N.bin).
Ok, I have checked and it is:
[9.883661] ath10k_pci
Anil Duggirala writes:
>> > I don't have a QCA6174 hw3.0 but I would guess that ath10k loaded the
>> > firmware-4.bin after it failed to load the firmware-5.bin.
>
> How can I make sure this is the case?
ath10k prints lots of information to dmesg after it has initialised the
device, so check
> > I don't have a QCA6174 hw3.0 but I would guess that ath10k loaded the
> > firmware-4.bin after it failed to load the firmware-5.bin.
How can I make sure this is the case? I have had a couple of issues with my
bluetooth, how can I test it?
thanks very much,
> It was introduced in v4.18 so once you upgrade the kernel to v4.18 or
> later you should not see the warnings anymore.
I see that I am running kernel 4.9.0-8. It may be quite some time before I get
to 4.18 right?
thanks,
___
ath10k mailing list
Sven Eckelmann writes:
> On Freitag, 16. November 2018 08:38:51 CET Anil Duggirala wrote:
>> hello,
>> I am getting this message at boot.
>>
>> [ 10.678576] ath10k_pci :03:00.0: firmware: failed to load
>> ath10k/pre-cal-pci-:03:00.0.bin (-2)
>> [ 10.678631] ath10k_pci :03:00.0:
Govind Singh writes:
> HOST capability interface data structures are updated
> in HL3.1 fw version. Update the qmi host capability
> members for compatibility across different firmware
> versions.
> With this change HL2.0 fw upgrade is required as this
> change breaks the backward compatibility
