ath11k: incorrect board_id retrieval

[Sven Eckelmann]

On Friday, 26 November 2021 15:48:17 CET Sven Eckelmann wrote:
> I've noticed that manufacturers of cards gave me various information what 
> board_id they expected a device (QCN9074) is detected as. But ath11k only 
> retrieves the board id as 0xff - thus the ath11k driver is always loading the 
> wrong BDF. Commercially available boards with a problem like this are:
>
> * 8devices Pineapple
>   - 2GHz: 160 (0xa0)
>   - 5GHz: 161 (0xa1)
>   - 6GHz: 162 (0xa2)
> * Compex WLE3000H5
> * (maybe there is not a single one which works?)

Just retrieved the next card (EmWicon WMX7205 - could be the same as jjPlus 
WMX7205) and it has exactly the same problem:

    ath11k_pci 0000:05:00.0: failed to fetch board data for bus=pci,vendor=17cb,device=1103,subsystem-vendor=17cb,subsystem-device=0108,qmi-chip-id=2,qmi-board-id=255 from ath11k/WCN6855/hw2.0/board-2.bin
    ath11k_pci 0000:05:00.0: failed to fetch board-2.bin or board.bin from WCN6855/hw2.

Of course, the only provided keys (all with board_id != 255) are:

* bus=pci,vendor=17cb,device=1103,subsystem-vendor=17cb,subsystem-device=3374,qmi-chip-id=2,qmi-board-id=262
* bus=pci,vendor=17cb,device=1103,subsystem-vendor=17cb,subsystem-device=3374,qmi-chip-id=2,qmi-board-id=266
* bus=pci,vendor=17cb,device=1103,subsystem-vendor=17cb,subsystem-device=3374,qmi-chip-id=18,qmi-board-id=266

So until now, I could not find a single card for which ath11k returned a 
board-id != 255 (unless it was overwritten via the devicetree).

> So my question would be: Is the ath11k based board_id retrieval just broken? 
> Or are these cards broken?

Kind regards,
	Sven