Bug 219454
| Summary: | ath11k: WCN6855: missing board file for bus=pci,vendor=17cb,device=1103,subsystem-vendor=17cb,subsystem-device=0108,qmi-chip-id=2|18,qmi-board-id=255,variant=MS_Volterra for Windows Dev Kit 2023 | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | Jens Glathe (jens.glathe) |
| Component: | Network | Assignee: | drivers_network (drivers_network) |
| Status: | NEW --- | ||
| Severity: | normal | CC: | jens.glathe |
| Priority: | P3 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | Subsystem: | ||
| Regression: | No | Bisected commit-id: | |
| Attachments: |
board-2.json file with WDK2023 entries
generated board-2.bin.zst file as it is in use here |
||
Created attachment 307117 [details] generated board-2.bin.zst file as it is in use here The corresponding Kernel patch is <20241030-jg-blackrock-for-upstream-v6-0-7cd7f7d8d97c@oldschoolsolutions.biz> . |
Created attachment 307116 [details] board-2.json file with WDK2023 entries Hi there, this is a request to add aforementioned board IDs to the board-2.bin for WCN6855. The module in question is in the Microsoft Windows Dev Kit 2023. It has Windows drivers, but no (good) matching calibration data in linux-firmware. By default the board string without variant is found and the calibration data is used, but it gives poor bandwidth and range. It's barely working with it. After some experimenting and research I found that using the calibration data from the Lenovo Thinkpad X13s, which have the same subsystem vendor and id, work best and give ~350..500Mbit/s connection and good range. These are the entries that need to be added: bus=pci,vendor=17cb,device=1103,subsystem-vendor=17cb,subsystem-device=0108,qmi-chip-id=2,qmi-board-id=255,variant=MS_Volterra bus=pci,vendor=17cb,device=1103,subsystem-vendor=17cb,subsystem-device=0108,qmi-chip-id=18,qmi-board-id=255,variant=MS_Volterra The "variant=MS_Volterra" part is chosen by me. I have this configuration in use for about a year now, works well.