From: Ryan Hsu <ryanhsu@qti.qualcomm.com>
To: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: failed to fetch board data QCA6174
Date: Mon, 11 Sep 2017 21:15:12 +0000 [thread overview]
Message-ID: <bb97e4da-20bb-60bc-b7ec-4d59ea44cc8a@qti.qualcomm.com> (raw)
In-Reply-To: <53332261-4d0b-3c45-05c5-e129feaad594@gmail.com>
On 09/11/2017 09:54 AM, Luka Karinja wrote:
> Hello. I'm trying to get a M.2 QCA6174 working on my MSI B150Mortar motherboard. i did try all the various firmware versions from https://github.com/kvalo/ath10k-firmware more or less with the same errors as bellow
>
> in dmesg i get: failed to fetch board data for bus=pci,vendor=168c,device=003e,subsystem-vendor=0000,subsystem-device=0000 from ath10k/QCA6174/hw3.0/board-2.bin
>
> when trying to get the device up i get: RTNETLINK answers: Resource temporarily unavailable
>
> [ 2026.219245] ath10k_pci 0000:05:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
> [ 2026.477510] ath10k_pci 0000:05:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 0000:0000
> [ 2026.477517] ath10k_pci 0000:05:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0
> [ 2026.478640] ath10k_pci 0000:05:00.0: firmware ver WLAN.RM.4.4.1-00026-QCARMSWP-1 api 6 features wowlan,ignore-otp,raw-mode crc32 7b90c3fc
> [ 2026.542196] ath10k_pci 0000:05:00.0: failed to fetch board data for bus=pci,vendor=168c,device=003e,subsystem-vendor=0000,subsystem-device=0000 from ath10k/QCA6174/hw3.0/board-2.bin
>
Not sure what kernel and driver do you have?
This should already fix this case - https://patchwork.kernel.org/patch/9486941/
--
Ryan Hsu
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2017-09-11 21:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 16:54 failed to fetch board data QCA6174 Luka Karinja
2017-09-11 21:15 ` Ryan Hsu [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-09-11 22:03 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
[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
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=bb97e4da-20bb-60bc-b7ec-4d59ea44cc8a@qti.qualcomm.com \
--to=ryanhsu@qti.qualcomm.com \
--cc=ath10k@lists.infradead.org \
/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