RE: qca: Update firmware files for BT chip WCN3991.

[SURAJ ASHOK MAGAR (Temp) (QUIC)]

Yes,
Please ignore the rest and pull 0e8f546c4c66a61981fd0341ec0a84563d1cfaaa .

Regards,
Suraj Magar

-----Original Message-----
From: Josh Boyer <jwboyer@xxxxxxxxxx> 
Sent: Monday, September 26, 2022 7:54 PM
To: SURAJ ASHOK MAGAR (Temp) (QUIC) <quic_smagar@xxxxxxxxxxx>
Cc: linux-firmware@xxxxxxxxxx; linux-bluethooth@xxxxxxxxxxxxxxx; mka@xxxxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx; linux-arm-msm@xxxxxxxxxxxxxxx; Balakrishna Godavarthi (QUIC) <quic_bgodavar@xxxxxxxxxxx>; Sai Teja Aluvala (Temp) (QUIC) <quic_saluvala@xxxxxxxxxxx>; Atul Dhudase (QUIC) <quic_adhudase@xxxxxxxxxxx>; Sampath Nimmala (Temp) (QUIC) <quic_sampnimm@xxxxxxxxxxx>
Subject: Re: qca: Update firmware files for BT chip WCN3991.

On Fri, Sep 16, 2022 at 2:54 AM SURAJ ASHOK MAGAR (Temp) (QUIC) <quic_smagar@xxxxxxxxxxx> wrote:
>
> Hello Team,
>
>
>
> Please include firmware bins for WCN3991.
>
>
>
> Changes includes updated firmware files with:
>
> BQR enhancements
> LE priority changes
> Braktooth issue fix
> RSSI Fix
>
> Snapshot of pull request is as below, let me know if anything is missing.
>
>
>
>
>
>
>
>
>
> The following changes since commit 3593bb7d8f6f18c442a6b0b3f3d43e4d5d7fc2be:
>
>
>
>   Removing crnv32 (2022-09-15 11:09:50 +0530)
>
>
>
> are available in the Git repository at:
>
>
>
>   https://github.com/suraj714/Bluetooth-upstream.git main
>
>
>
> for you to fetch changes up to 0e8f546c4c66a61981fd0341ec0a84563d1cfaaa:
>
>
>
>   qca: Update firmware files for BT chip WCN3991. (2022-09-16 10:44:17 
> +0530)
>
>
>
> ----------------------------------------------------------------
>
> Suraj Magar (1):
>
>       qca: Update firmware files for BT chip WCN3991.
>
>
>
> qca/crbtfw32.tlv | Bin 126036 -> 117664 bytes
>
> qca/crnv32.bin   | Bin 0 -> 5407 bytes
>
> qca/crnv32u.bin  | Bin 0 -> 5407 bytes
>
> 3 files changed, 0 insertions(+), 0 deletions(-)
>
> create mode 100644 qca/crnv32.bin
>
> create mode 100644 qca/crnv32u.bin

This diff stat looks odd, and there's an additional commit in your branch not mentioned.  Should I just pull 0e8f546c4c66a61981fd0341ec0a84563d1cfaaa and ignore the rest?

josh