mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: quic_zijuhu <quic_zijuhu@quicinc.com>
To: Johan Hovold <johan@kernel.org>
Cc: Tim Jiang <quic_tjiang@quicinc.com>,
	Janaki Ramaiah Thota <quic_janathot@quicinc.com>,
	<linux-bluetooth@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: QCA NVM file for the X13s (WCN6855)
Date: Thu, 14 Nov 2024 14:57:45 +0800	[thread overview]
Message-ID: <5549d7e4-06cb-4305-8cec-10e93e5fbbff@quicinc.com> (raw)
In-Reply-To: <ZjOfdK41yLwkH25T@hovoldconsulting.com>

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
> 


  reply	other threads:[~2024-11-14  6:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-02 10:57 Johan Hovold
2024-05-02 12:56 ` quic_zijuhu
2024-05-02 13:25   ` Johan Hovold
2024-05-02 13:46     ` quic_zijuhu
2024-05-02 14:13       ` Johan Hovold
2024-11-14  6:57         ` quic_zijuhu [this message]
2024-11-14  8:27           ` Paul Menzel
2024-11-14  8:39             ` quic_zijuhu
2024-11-15  9:08           ` Johan Hovold

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=5549d7e4-06cb-4305-8cec-10e93e5fbbff@quicinc.com \
    --to=quic_zijuhu@quicinc.com \
    --cc=johan@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_janathot@quicinc.com \
    --cc=quic_tjiang@quicinc.com \
    /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

all inboxes | Powered by JetHome®