ath11k: incorrect board_id retrieval

[Sven Eckelmann]

On Friday, 26 November 2021 15:48:17 CET Sven Eckelmann wrote:
[...]
> * 8devices Pineapple
>   - 2GHz: 160 (0xa0)
>   - 5GHz: 161 (0xa1)
>   - 6GHz: 162 (0xa2)
> * Compex WLE3000H5
> * (maybe there is not a single one which works?)
> 
> If I would use these boards in one with a devicetree then I could just 
> overwrite it using qcom,board_id (and/or qcom,ath11k-calibration-variant). But 
> this isn't the case when I want to use a couple of these cards in a simple x86 
> system. All off them (even when they are significantly different) are reported
> as
> 
>     ath11k_pci 0000:03:00.0: chip_id 0x0 chip_family 0x0 board_id 0xff soc_id 0xffffffff

I've send my 6GHz modules back to 8devices. They told me that this problem was 
identified and fixed in their calibration process. I've just got them back 
from them and now I see following reported by ath11k:

    ath11k_pci 0000:03:00.0: chip_id 0x0 chip_family 0x0 board_id 0xa2 soc_id 0xffffffff

So it is definitely not a firmware problem and it should be fixed by the 
manufacturers (similar to what 8devices did).

Kind regards,
	Sven
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.infradead.org/pipermail/ath11k/attachments/20220218/e37c4cec/attachment.sig>