unknown qca6164 model 0x0041

[Michal Kazior]

On 17 August 2015 at 19:37, Joseph Salisbury
<joseph.salisbury at canonical.com> wrote:
> On 08/13/2015 06:34 AM, Kalle Valo wrote:
>> Michal Kazior <michal.kazior at tieto.com> writes:
>>
>>> On 12 August 2015 at 21:33, Joseph Salisbury
>>> <joseph.salisbury at canonical.com> wrote:
>>>> Hello,
>>>>
>>>> There are still new folks reporting this issue in the Launchpad bug
>>>> report[0].  Has there been any progress on the firmware problem reported
>>>> in the comment by Kalle Valo on March 26, 2015[1]?
>>>>
>>>> Thanks in advance,
>>> Thanks for pinging.
>>>
>>> Recently we finally found a way to boot qca6164 with unofficial
>>> windows-extracted firmware images on ath10k[1]. We still don't have an
>>> official firmware release for qca61x4 family for ath10k though.
>> I just pushed the firmware here:
>>
>> https://github.com/kvalo/ath10k-firmware/commit/7f7e7dda33676ced293de477b03711199ffe5256
>>
>> Please let me know how it works (or not). And really sorry for taking so
>> long with this.
>>
> With the new files, a reporter in the bug says that he still gets the
> ath10k/QCA6174/hw2.1/firmware-4.bin errors. Does the kernel need to be
> updated for a new driver that looks for a -5 firmware?

Yes - either 4.2-rc or newer, or use Kalle's tree[1].

The qca6174 hw2.1 fix has been pulled into 4.1-stable[2] but it
doesn't understand the ignore_otp_result firmware feature flag so if
you rename the firmware-5.bin[3] to firmware-4.bin you'll need to load
ath10k_core module with "skip_otp=y" parameter.


Michał


[1]: https://github.com/kvalo/ath
[2]: https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?h=linux-4.1.y&id=b235edce5cbe4e978d44d8c57ec15afc4ba27d50
[3]: https://github.com/kvalo/ath10k-firmware/blob/7f7e7dda33676ced293de477b03711199ffe5256/ath10k/QCA6174/hw2.1/firmware-5.bin