From: smagar@codeaurora.org
To: linux-firmware@kernel.org, jwboyer@kernel.org
Cc: mka@chromium.org, linux-kernel@vger.kernel.org,
linux-bluethoth@vger.kernel.org, linux-arm-msm@vger.kernel.org,
hemantg@codeaurora.org, abhishekpandit@chromium.org,
bgodavar@codeaurora.org, adhudase@codeaurora.org,
sampnimm@codeaurora.org
Subject: Re: Request to update WCN6750 FW file
Date: Wed, 11 Aug 2021 12:39:51 +0530 [thread overview]
Message-ID: <2a70be94a1529153aed2a158e7b1e523@codeaurora.org> (raw)
In-Reply-To: <9196f77c4b203dce3982e31d241392de@codeaurora.org>
On 2021-07-27 10:03, smagar@codeaurora.org wrote:
> Hello Team,
>
> Please include new firmware bins for QCA BT SoC WCN6750.
>
> Snapshot of pull request is as below, let me know if anything is
> missing.
>
>
>
> The following changes since commit
> 168452ee695b5edb9deb641059bc110b9c5e8fc7:
>
> Merge tag 'iwlwifi-fw-2021-07-19' of
> git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware
> into main (2021-07-19 14:35:47 -0400)
>
> are available in the git repository at:
>
> https://github.com/suraj714/linux-firmware-bluetooth master
>
> for you to fetch changes up to
> 5dd32d878e7561789422f3e1fe0f7c48fcc00e04:
>
> qca: Add firmware files for BT chip WCN6750. (2021-07-26 16:38:01
> +0530)
>
> ----------------------------------------------------------------
> smagar (1):
> qca: Add firmware files for BT chip WCN6750.
>
> WHENCE | 6 ++++++
> qca/msbtfw11.mbn | Bin 0 -> 129348 bytes
> qca/msbtfw11.tlv | Bin 0 -> 117136 bytes
> qca/msnv11.bin | Bin 0 -> 5633 bytes
> 4 files changed, 6 insertions(+)
> create mode 100644 qca/msbtfw11.mbn
> create mode 100644 qca/msbtfw11.tlv
> create mode 100644 qca/msnv11.bin
>
>
>
> Regards,
> Suraj Magar
Hi Team,
Any update on this?
next prev parent reply other threads:[~2021-08-11 7:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-27 4:33 Request to update WCN6750 FW file smagar
2021-08-11 7:09 ` smagar [this message]
2021-08-12 13:20 ` Josh Boyer
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=2a70be94a1529153aed2a158e7b1e523@codeaurora.org \
--to=smagar@codeaurora.org \
--cc=abhishekpandit@chromium.org \
--cc=adhudase@codeaurora.org \
--cc=bgodavar@codeaurora.org \
--cc=hemantg@codeaurora.org \
--cc=jwboyer@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-bluethoth@vger.kernel.org \
--cc=linux-firmware@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mka@chromium.org \
--cc=sampnimm@codeaurora.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.