From: Luka Karinja <luka.karinja@gmail.com>
To: Ryan Hsu <ryanhsu@qti.qualcomm.com>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: failed to fetch board data QCA6174
Date: Wed, 13 Sep 2017 08:00:51 +0200 [thread overview]
Message-ID: <323b1df8-741e-77cd-708b-bb306696f092@gmail.com> (raw)
In-Reply-To: <d4b43397-3267-abff-fbc1-48cbd9d58073@qti.qualcomm.com>
On 09/13/2017 01:14 AM, Ryan Hsu wrote:
> On 09/12/2017 12:24 AM, Luka Karinja wrote:
>
>> [ 3.662941] ath10k_pci 0000:05:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 0000:0000
> Hmm, where did you get this module? it seems like this module is not calibrated or assigned a sub IDs information, that why it cause the failure, since incorrect board file will lead to the firmware crash.
>
> You might want to contact your module provider to give you the correct board file (board.bin) and replace it under the same firmware folder for testing/developing.
>
Hello. Its a module from ebay. So probably i can't do much with it
without the right board.bin?
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2017-09-13 6:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 22:03 failed to fetch board data QCA6174 Luka Karinja
2017-09-11 22:25 ` Ryan Hsu
2017-09-12 7:24 ` Luka Karinja
2017-09-12 7:39 ` Luka Karinja
2017-09-12 23:14 ` Ryan Hsu
2017-09-13 0:15 ` Carsten Haitzler
2017-09-13 5:06 ` Ryan Hsu
2017-09-13 12:56 ` Carsten Haitzler
2017-09-13 18:23 ` Ryan Hsu
2017-09-14 0:38 ` Carsten Haitzler
2017-09-13 6:00 ` Luka Karinja [this message]
[not found] ` <8b76e913-1205-db34-915b-658fdc017afe@gmail.com>
2017-09-13 7:00 ` Ryan Hsu
2017-09-13 19:24 ` Luka Karinja
2017-09-13 22:14 ` Ryan Hsu
-- strict thread matches above, loose matches on Subject: below --
2017-09-11 16:54 Luka Karinja
2017-09-11 21:15 ` Ryan Hsu
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=323b1df8-741e-77cd-708b-bb306696f092@gmail.com \
--to=luka.karinja@gmail.com \
--cc=ath10k@lists.infradead.org \
--cc=ryanhsu@qti.qualcomm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox