From: Balakrishna Godavarthi <bgodavar@codeaurora.org>
To: Josh Boyer <jwboyer@kernel.org>
Cc: Hemantg <hemantg@codeaurora.org>,
Linux Firmware <linux-firmware@kernel.org>,
BlueZ development <linux-bluetooth@vger.kernel.org>,
"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>,
Linux-arm Msm <linux-arm-msm@vger.kernel.org>,
Nicolas Dechesne <nicolas.dechesne@linaro.org>,
Kalle Valo <kvalo@codeaurora.org>
Subject: Firmware files for QCA BT chip wcn3990
Date: Wed, 20 Feb 2019 18:31:13 +0530 [thread overview]
Message-ID: <26af87bceb0a7c355ba90cce863bfd1e@codeaurora.org> (raw)
Hi,
The following changes since commit
710963fe53ee3f227556d36839df3858daf6e232:
Merge https://github.com/ajaykuee/linux-firmware (2019-02-13 07:42:20
-0500)
are available in the Git repository at:
https://github.com/bgodavar/qca_bt_wcn3990_fw.git
for you to fetch changes up to f859d9fda9379205c9bcf2eab11fae68891085ee:
qca: Add firmware files for BT chip wcn3990. (2019-02-20 18:23:46
+0530)
----------------------------------------------------------------
Balakrishna Godavarthi (1):
qca: Add firmware files for BT chip wcn3990.
WHENCE | 2 +
qca/NOTICE.txt | 334
++++++++++++++++++++++++++++++++++++++++++++++++++++++++--------------------------------------------------------------------------------------------
qca/crbtfw21.tlv | Bin 0 -> 177060 bytes
qca/crnv21.bin | Bin 0 -> 4587 bytes
4 files changed, 129 insertions(+), 207 deletions(-)
create mode 100644 qca/crbtfw21.tlv
create mode 100644 qca/crnv21.bin
--
Regards
Balakrishna.
next reply other threads:[~2019-02-20 13:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 13:01 Balakrishna Godavarthi [this message]
2019-02-21 12:24 ` Firmware files for QCA BT chip wcn3990 Josh Boyer
-- strict thread matches above, loose matches on Subject: below --
2019-02-18 6:13 Firmware files for QCA BT chip WCN3990 Balakrishna Godavarthi
2019-02-18 8:38 ` Nicolas Dechesne
2019-02-18 9:07 ` Balakrishna Godavarthi
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=26af87bceb0a7c355ba90cce863bfd1e@codeaurora.org \
--to=bgodavar@codeaurora.org \
--cc=hemantg@codeaurora.org \
--cc=jwboyer@kernel.org \
--cc=kvalo@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-firmware@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.dechesne@linaro.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;
as well as URLs for NNTP newsgroup(s).