Re: QCA NVM file for the X13s (WCN6855)

[Johan Hovold]

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.

Much appreciated, thank you.

Johan