Re: [PATCH 3/3] arm64: dts: qcom: sc8280xp: Add Huawei Matebook E Go (sc8280xp)

[Pengyu Luo]

On Sat, Dec 14, 2024 at 9:39 PM Dmitry Baryshkov <dmitry.baryshkov@xxxxxxxxxx> wrote:

> On Sat, Dec 14, 2024 at 08:23:00PM +0800, Pengyu Luo wrote:
>> On Fri, Dec 13, 2024 at 1:13 AM Konrad Dybcio <konrad.dybcio@xxxxxxxxxxxxxxxx> wrote:
>>
>> [...]
>>
>> >> +
>> >> +          /* /lib/firmware/ath11k/WCN6855/hw2.1/board-2.bin
>> >> +           * there is no calibrate data for huawei,
>> >> +           * but they have the same subsystem-device id
>> >> +           */
>> >> +          qcom,ath11k-calibration-variant = "LE_X13S";
>> >
>> > Oh, this can be taken care of! See [2], [3].
>>
>> [...]
>>
>> Hi, Konrad
>>
>> I want to distrub you again.
>>
>> Finally, I found something, after I enabled ath11k boot dbg, I got my
>> id_string='bus=pci,vendor=17cb,device=1103,subsystem-vendor=17cb,subsystem-device=0108,qmi-chip-id=2,qmi-board-id=255`
>>
>> With qca-swiss-army-knife (see [1])
>>
>> $ ./ath11k-bdencoder -e board-2.bin | grep -i "$id_string"
>> bus=pci,vendor=17cb,device=1103,subsystem-vendor=17cb,subsystem-device=0108,qmi-chip-id=2,qmi-board-id=255.bin created size: 60048
>>
>> It have already been here. So that means I don't need to extract from
>> Windows. I just extract it from linux-firmware then give it a variant
>> name and send patches to ath11k, right?
> 
> No. Usually 255 is an ID that is used by a variety of boards. So,
> basically, you have to extract board data from Windows, add a proper
> calibration variant that is specific to your board and then send the
> resulting data to the ath11k mailing list.
> 

But how? Is it possible that some boards have no  calibration data?
I tried to track the access time of files, the result shows that these
bdwlan* are never touched. According to my observation, these files
should have been accessed, (like BT firmware on windows).

>>
>> Pengyu
>>
>> [1] https://github.com/qca/qca-swiss-army-knife
>
> --
> With best wishes
> Dmitry


Pengyu