From: Kalle Valo <kvalo@kernel.org>
To: Sven Eckelmann <sven@narfation.org>
Cc: ath11k@lists.infradead.org
Subject: Re: ath11k: incorrect board_id retrieval
Date: Wed, 13 Apr 2022 10:01:49 +0300 [thread overview]
Message-ID: <87wnftmppe.fsf@kernel.org> (raw)
In-Reply-To: <4611744.eon2OSsH4K@ripper> (Sven Eckelmann's message of "Fri, 18 Feb 2022 14:52:06 +0100")
Sven Eckelmann <sven@narfation.org> writes:
> 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).
So the device is working fine now?
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
next prev parent reply other threads:[~2022-04-13 7:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-26 14:48 ath11k: incorrect board_id retrieval Sven Eckelmann
2021-12-02 14:43 ` Sven Eckelmann
2021-12-14 13:31 ` Sven Eckelmann
2021-12-15 17:42 ` Seevalamuthu M (QUIC)
2021-12-16 8:40 ` Sven Eckelmann
2022-02-18 13:52 ` Sven Eckelmann
2022-04-13 7:01 ` Kalle Valo [this message]
2022-04-13 7:20 ` Sven Eckelmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wnftmppe.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=sven@narfation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox