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: <5549d7e4-06cb-4305-8cec-10e93e5fbbff@quicinc.com>
Date: Thu, 14 Nov 2024 14:57:45 +0800
From: quic_zijuhu <quic_zijuhu@...cinc.com>
To: Johan Hovold <johan@...nel.org>
CC: Tim Jiang <quic_tjiang@...cinc.com>,
        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 10:13 PM, Johan Hovold wrote:
> On Thu, May 02, 2024 at 09:46:38PM +0800, quic_zijuhu wrote:
>> On 5/2/2024 9:25 PM, Johan Hovold wrote:
>>> On Thu, May 02, 2024 at 08:56:12PM +0800, quic_zijuhu wrote:
>>>> On 5/2/2024 6:57 PM, Johan Hovold wrote:
> 
>>> It's WCN6855 but the Linux driver currently uses the firmware you pushed
>>> for 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?
>>>
>> hpnv21g.b8c is the right NVM for the machine.
> 
> Ok, thanks. I'll try to find some time to test with this one as well.
> 
>>> What is the difference between those two?
> 
>> i am afraid that i can't answer your question due to company CCI policy
> 
> I understand.
> 
>>> Exactly. It's a Lenovo machine that comes with Windows pre-installed and
>>> we're working on enabling Linux on it with some help from Lenovo.
>>>
>>>> need customer to make a request for their requirements if the answer is
>>>> yes for above question.
>>>
>>> Lenovo has made requests for X13s firmware from Qualcomm and pushed it
>>> to linux-firmware [1], but they have not yet been able to get Qualcomm
>>> to provide an NVM configuration file for Bluetooth (I think the problem
>>> may be finding the right person to talk to inside Qualcomm).
>>>
>>> So I was hoping maybe you could help us with this since the difference
>>> between 'hpnv21.bin' that you pushed to linux-firmware and what came
>>> with Windows appears to be really small (e.g. just a few bytes).
>>>
>> let me try to find out the right person who will push this task at next
>> monday.
>> there are some other internal procedures before we can push BT firmware
>> into linux-firmware.
> 


have up-streamed 22 NVM files which come from WOS into linux-firmware as
shown by below link, both hpnv21g.b8c and hpnv21.b8c are also contained.

https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=77a11ffc5a0aaaadc870793d02f6c6781ee9f598

(^^)(^^).

> Much appreciated, thank you.
> 
> Johan
> 


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ