From: poma <pomidorabelisima@gmail.com>
To: linux-wireless <linux-wireless@vger.kernel.org>
Cc: Kalle Valo <kvalo@codeaurora.org>
Subject: ath10k QCA6174 firmwares match
Date: Sun, 10 Jan 2016 17:43:28 +0100 [thread overview]
Message-ID: <56928A30.6010803@gmail.com> (raw)
It's not that they fully correspond,
however here is a brief overview
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Ath10k drivers can't find firmware"
https://bugzilla.redhat.com/show_bug.cgi?id=1208986
- dmesg -2:
ath10k/QCA6174/hw2.1/board.bin
ath10k/QCA6174/hw2.1/firmware-2.bin
ath10k/QCA6174/hw2.1/firmware-3.bin
ath10k/QCA6174/hw2.1/firmware-4.bin
- linux-firmware-20151214-60.gitbbe4917c:
/usr/lib/firmware/ath10k/QCA6174/hw2.1/
board.bin
firmware-5.bin
- github.com/kvalo/ath10k-firmware.git:
ath10k-firmware/QCA6174/hw2.1/
board.bin
firmware-5.bin
- modinfo ath10k_pci | grep QCA6174/hw2.1
firmware: ath10k/QCA6174/hw2.1/board-2.bin
firmware: ath10k/QCA6174/hw2.1/board.bin
firmware: ath10k/QCA6174/hw2.1/firmware-5.bin
firmware: ath10k/QCA6174/hw2.1/firmware-4.bin
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Qualcomm Atheros QCA6174 not working"
https://bugzilla.redhat.com/show_bug.cgi?id=1294263
- dmesg -2:
ath10k/QCA6174/hw3.0/board.bin
ath10k/QCA6174/hw3.0/firmware-5.bin
- linux-firmware-20151214-60.gitbbe4917c:
/usr/lib/firmware/ath10k/QCA6174/hw3.0/
board.bin
firmware-4.bin
- github.com/kvalo/ath10k-firmware.git:
ath10k-firmware/QCA6174/hw3.0/
board-2.bin
board.bin
firmware-4.bin
- modinfo ath10k_pci | grep QCA6174/hw3.0
firmware: ath10k/QCA6174/hw3.0/board-2.bin
firmware: ath10k/QCA6174/hw3.0/board.bin
firmware: ath10k/QCA6174/hw3.0/firmware-5.bin
firmware: ath10k/QCA6174/hw3.0/firmware-4.bin
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Qualcomm Atheros QCA6164 not working"
https://bugzilla.redhat.com/show_bug.cgi?id=1257500
firmware?
reply other threads:[~2016-01-10 16:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=56928A30.6010803@gmail.com \
--to=pomidorabelisima@gmail.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.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 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.