linux-kernel - Re: QCA NVM file for the X13s (WCN6855)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <5aea3149-ba44-400f-acc6-1a3eca8a7e72@quicinc.com>
Date: Thu, 2 May 2024 20:56:12 +0800
From: quic_zijuhu <quic_zijuhu@...cinc.com>
To: Johan Hovold <johan@...nel.org>, Tim Jiang <quic_tjiang@...cinc.com>
CC: Janaki Ramaiah Thota <quic_janathot@...cinc.com>,
        <linux-bluetooth@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: QCA NVM file for the X13s (WCN6855)

On 5/2/2024 6:57 PM, Johan Hovold wrote:
> Hi Zijun and Tim,
> 
> I noticed that you have both submitted firmware and NVM files for
> QCA2066 to linux-firmware. [1][2]
> 
> I'm working on Linux support for the Lenovo ThinkPad X13s (Windows on
> Arm, Snapdragon), which has the related WCN6855 controller that uses the
> same firmware (hpbtfw21.tlv).
> 
which SOC type does the machine use?  WCN6855 or QCA2066?
> The current Linux driver is using the generic NVM file (hpnv21.bin) for
> WCN6855, but connectivity is quite bad and I only get 2-3 meters of
> range.
> > Switching to the board-specific NVM configuration (hpnv21b.b8c) that
it seems hpnv21b.b8c is a wrong NVM name.
is it hpnv21g.b8c?
> came with the Windows driver make all issues go away and the range is
> really good, but I'm not sure if that file is fully compatible with the
> firmware used by the Linux driver.
> 
> Could you help us submit an NVM configuration file for the controller
> with board id 0x008c to linux-firmware?
> 
For Windows OS, there are relevant channel to deliver BT firmware.
For Linux OS, we normally upload relevant BT firmware to linux-firmware.

it seems customer would like to use Linux OS instead of preinstalled
Windows OS for the machine.
right?

need customer to make a request for their requirements if the answer is
yes for above question.

> 	Bluetooth: hci0: setting up wcn6855
> 	Bluetooth: hci0: QCA Product ID   :0x00000013
> 	Bluetooth: hci0: QCA SOC Version  :0x400c1211
> 	Bluetooth: hci0: QCA ROM Version  :0x00000201
> 	Bluetooth: hci0: QCA Patch Version:0x000038e6
> 	Bluetooth: hci0: QCA controller version 0x12110201
> 	Bluetooth: hci0: QCA Downloading qca/hpbtfw21.tlv
> 	Bluetooth: hci0: qca_read_fw_board_id: bid = 8c
> 	Bluetooth: hci0: QCA Downloading qca/hpnv21.bin
> 
> It looks like the NVM files should be updated in lockstep with the
> firmware so if you could include that board in any future firmware
> updates too that would be really helpful.
> 
> Johan
> 
> 
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/qca?id=2ba1beaae0c649ce8a50baecc8df9e81cd524e65
> [2] https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/qca?id=598f5bd22361d7e92eebe8452d1f8013a1d35b9a