From: Abhishek Pandit-Subedi <abhishekpandit@chromium.org>
To: asitshah@codeaurora.org
Cc: linux-firmware@kernel.org, jwboyer@kernel.org,
Matthias Kaehlcke <mka@chromium.org>,
LKML <linux-kernel@vger.kernel.org>,
Bluez mailing list <linux-bluetooth@vger.kernel.org>,
linux-arm-msm@vger.kernel.org, Hemantg <hemantg@codeaurora.org>,
Venkata Lakshmi Narayana Gubba <gubbaven@codeaurora.org>,
Balakrishna Godavarthi <bgodavar@codeaurora.org>
Subject: Re: Update WCN3991 FW file
Date: Mon, 19 Oct 2020 14:37:44 -0700 [thread overview]
Message-ID: <CANFp7mXMfvHrAcaJhY7q2oZk3MtqOMxLGOEpNc-hnzVSyA+LZA@mail.gmail.com> (raw)
In-Reply-To: <b74ea9cb201bb98691ecbfb3893d2a49@codeaurora.org>
Nack.
This resulted in a boot loop on ChromeOS. It looks like only
'crbtfw32.tlv' was changed and not 'crnv32.bin'.
Abhishek
On Sat, Oct 17, 2020 at 8:33 AM <asitshah@codeaurora.org> wrote:
>
>
> Hi Team,
>
> Please include updated firmware bin for WCN3991.
>
> Snapshot of pull request is as below, let me know if anything is
> missing.
>
> >>>>>
>
> The following changes since commit
> 58d41d0facca2478d3e45f6321224361519aee96:
>
> ice: Add comms package file for Intel E800 series driver (2020-10-05
> 08:09:03 -0400)
>
> are available in the git repository at:
>
> https://github.com/shahasit/bt-linux-firmware/tree/master
>
> for you to fetch changes up to 8877322c1254f327f47c86ec02c46013b68b9a47:
>
> QCA : Updated firmware file for WCN3991 (2020-10-17 20:53:36 +0530)
>
> ----------------------------------------------------------------
> Asit Shah (1):
> QCA : Updated firmware file for WCN3991
>
> qca/crbtfw32.tlv | Bin 126300 -> 126832 bytes
> 1 file changed, 0 insertions(+), 0 deletions(-)
>
> <<<<<<
>
> Regards,
> Asit
next prev parent reply other threads:[~2020-10-19 21:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-17 15:33 Update WCN3991 FW file asitshah
2020-10-19 21:37 ` Abhishek Pandit-Subedi [this message]
2020-10-19 21:37 ` Abhishek Pandit-Subedi
2020-10-20 20:41 ` Abhishek Pandit-Subedi
2020-10-20 20:41 ` Abhishek Pandit-Subedi
2020-10-23 12:06 ` 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=CANFp7mXMfvHrAcaJhY7q2oZk3MtqOMxLGOEpNc-hnzVSyA+LZA@mail.gmail.com \
--to=abhishekpandit@chromium.org \
--cc=asitshah@codeaurora.org \
--cc=bgodavar@codeaurora.org \
--cc=gubbaven@codeaurora.org \
--cc=hemantg@codeaurora.org \
--cc=jwboyer@kernel.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 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.