linux-firmware.lore.kernel.org archive mirror
 help / color / mirror / Atom feed
From: asitshah@codeaurora.org
To: linux-firmware@kernel.org, jwboyer@kernel.org
Cc: mka@chromium.org, linux-kernel@vger.kernel.org,
	linux-bluetooth@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	hemantg@codeaurora.org, gubbaven@codeaurora.org,
	abhishekpandit@chromium.org, bgodavar@codeaurora.org
Subject: Request to Update WCN3991 FW file
Date: Thu, 05 Nov 2020 12:36:02 +0530	[thread overview]
Message-ID: <71acb08c5c7e7b10f4112b350707ee82@codeaurora.org> (raw)
Message-ID: <20201105070602.em4cDPW56MGCQMU71zoAJe3_puDWJ3NuZRBRKObQ0PQ@z> (raw)

Hello Team,

Please include updated firmware bins for WCN3991. Change includes 
updated TLV file to fix BT SSR.

Snapshot of pull request is as below, let me know if anything is 
missing.

>>>>> 

The following changes since commit 
dae4b4cd084102cd49c37aa8b579b208028ab025:

   Merge branch 'v1.1.5' of 
https://github.com/irui-wang/linux_fw_vpu_v1.1.5 into main (2020-10-23 
08:10:37 -0400)

are available in the git repository at:

   https://github.com/shahasit/bt-linux-firmware.git master

for you to fetch changes up to d7793e53b156126f6ea09c8d6e17cc9a8fe0ca77:

   QCA : Fixed BT SSR due to command timeout / IO fatal error (2020-11-05 
12:26:32 +0530)

----------------------------------------------------------------
Asit Shah (1):
       QCA : Fixed BT SSR due to command timeout / IO fatal error

  qca/crbtfw32.tlv | Bin 126832 -> 126892 bytes
  1 file changed, 0 insertions(+), 0 deletions(-)

<<<<<

Regards,
Asit

             reply	other threads:[~2020-11-05  7:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-05  7:06 asitshah [this message]
2020-11-05  7:06 ` Request to Update WCN3991 FW file asitshah
2020-11-13 15:17 ` Josh Boyer
2021-08-12  8:05 Request to update " smagar
2021-08-12 13:22 ` 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=71acb08c5c7e7b10f4112b350707ee82@codeaurora.org \
    --to=asitshah@codeaurora.org \
    --cc=abhishekpandit@chromium.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 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).