ATH11K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: Kalle Valo <kvalo@kernel.org>
Cc: ath11k@lists.infradead.org
Subject: Re: ath11k: incorrect board_id retrieval
Date: Wed, 13 Apr 2022 09:20:50 +0200	[thread overview]
Message-ID: <10773580.hMCCILeT51@ripper> (raw)
In-Reply-To: <87wnftmppe.fsf@kernel.org>


[-- Attachment #1.1: Type: text/plain, Size: 2121 bytes --]

On Wednesday, 13 April 2022 09:01:49 CEST Kalle Valo wrote:
> 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?

8devices Pineapple (after RMA) - yes.

For Compex WLE3000H5 - not that I would know about any fixed HW revision.

And for the EmWicon WMX7205/jjPlus WMX7205, it seems like the 
vendor=17cb,device=1103,subsystem-vendor=17cb,subsystem-device=0108 is used 
for identification of the actual vendor/product [0] (and not the board_id like 
on other devices). But as you can see, they say that it 
is a QCA product while it actually isn't actually one

And the manufacturer is also not able to provide a BDF which is compatible 
(signed? [1]) for the usage with ath11k's firmware blob.

Kind regards,
	Sven

[0] https://lore.kernel.org/all/CACT4oud4hmkjrAPkOr0sG1DNNgcgQaKT2JNJzcivZey9b5Hpiw@mail.gmail.com/
[1] https://lore.kernel.org/all/DM6PR02MB69248F37B55ACCC868F8B82BE0769@DM6PR02MB6924.namprd02.prod.outlook.com/

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 102 bytes --]

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

      reply	other threads:[~2022-04-13  7:21 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
2022-04-13  7:20     ` Sven Eckelmann [this message]

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=10773580.hMCCILeT51@ripper \
    --to=sven@narfation.org \
    --cc=ath11k@lists.infradead.org \
    --cc=kvalo@kernel.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