From: Joseph Salisbury <joseph.salisbury@canonical.com>
To: Kalle Valo <kvalo@qca.qualcomm.com>,
Michal Kazior <michal.kazior@tieto.com>
Cc: 1436940@bugs.launchpad.net, Arnd Bergmann <arnd@arndb.de>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: unknown qca6164 model 0x0041
Date: Thu, 13 Aug 2015 06:37:43 -0400 [thread overview]
Message-ID: <55CC7377.4060800@canonical.com> (raw)
In-Reply-To: <87zj1vo4ti.fsf@kamboji.qca.qualcomm.com>
On 08/13/2015 06:34 AM, Kalle Valo wrote:
> Michal Kazior <michal.kazior@tieto.com> writes:
>
>> On 12 August 2015 at 21:33, Joseph Salisbury
>> <joseph.salisbury@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.
>
Thanks for such a fast response!
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2015-08-13 10:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 19:33 unknown qca6164 model 0x0041 Joseph Salisbury
2015-08-13 5:04 ` Michal Kazior
2015-08-13 10:34 ` Kalle Valo
2015-08-13 10:37 ` Joseph Salisbury [this message]
2015-08-17 17:37 ` Joseph Salisbury
2015-08-18 5:07 ` Michal Kazior
-- strict thread matches above, loose matches on Subject: below --
2015-03-19 12:17 Arnd Bergmann
2015-03-19 12:26 ` Michal Kazior
2015-03-19 13:31 ` Arnd Bergmann
2015-03-20 15:56 ` Kalle Valo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55CC7377.4060800@canonical.com \
--to=joseph.salisbury@canonical.com \
--cc=1436940@bugs.launchpad.net \
--cc=arnd@arndb.de \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@qca.qualcomm.com \
--cc=michal.kazior@tieto.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.