From: Josh Boyer <jwboyer@kernel.org>
To: asitshah@codeaurora.org
Cc: Linux Firmware <linux-firmware@kernel.org>,
mka@chromium.org,
"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>,
BlueZ development <linux-bluetooth@vger.kernel.org>,
Linux-arm Msm <linux-arm-msm@vger.kernel.org>,
Hemantg <hemantg@codeaurora.org>,
gubbaven@codeaurora.org, abhishekpandit@chromium.org,
Balakrishna Godavarthi <bgodavar@codeaurora.org>
Subject: Re: Update WCN3991 FW with new enhancement
Date: Mon, 5 Oct 2020 08:04:23 -0400 [thread overview]
Message-ID: <CA+5PVA5Z1gDLXQjBqRMRDz-bVw1NVGvBSs+=veGjcAwrrQXycQ@mail.gmail.com> (raw)
In-Reply-To: <d4a4a37625f6b562c5096cbe1a6ccb61@codeaurora.org>
Pulled and pushed out.
josh
On Thu, Oct 1, 2020 at 2:51 AM <asitshah@codeaurora.org> wrote:
>
>
> Hi Team,
>
> Please include updated firmware bins for WCN3991.
>
> Snapshot of pull request is as below, let me know if anything is
> missing.
>
>
> >>>>>>>>>>>>>>
>
> The following changes since commit
> b78a66c909c7150601e1b2a810b0e7c8f98d920c:
>
> linux-firmware: Update firmware for Cadence MHDP8546 DP bridge
> (2020-09-28 11:38:27 -0400)
>
> are available in the git repository at:
>
> https://github.com/shahasit/linux-firmware-bt/tree/master
>
> for you to fetch changes up to ad1da95d52f1a9206da3ef52f3484f3b89ec6615:
>
> QCA : Updated firmware files for WCN3991 (2020-10-01 12:03:01 +0530)
>
> ----------------------------------------------------------------
> Asit Shah (1):
> QCA : Updated firmware files for WCN3991
>
> WHENCE | 1 +
> qca/crbtfw32.tlv | Bin 125896 -> 126300 bytes
> qca/crnv32.bin | Bin 5299 -> 5407 bytes
> qca/crnv32u.bin | Bin 0 -> 5407 bytes
> 4 files changed, 1 insertion(+)
> create mode 100644 qca/crnv32u.bin
>
>
> Regards,
> Asit
prev parent reply other threads:[~2020-10-05 12:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-01 6:51 Update WCN3991 FW with new enhancement asitshah
2020-10-01 6:51 ` asitshah
2020-10-05 12:04 ` Josh Boyer [this message]
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='CA+5PVA5Z1gDLXQjBqRMRDz-bVw1NVGvBSs+=veGjcAwrrQXycQ@mail.gmail.com' \
--to=jwboyer@kernel.org \
--cc=abhishekpandit@chromium.org \
--cc=asitshah@codeaurora.org \
--cc=bgodavar@codeaurora.org \
--cc=gubbaven@codeaurora.org \
--cc=hemantg@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=mka@chromium.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).