From: Sven Eckelmann <sven@narfation.org>
To: "ath11k@lists.infradead.org" <ath11k@lists.infradead.org>,
"Seevalamuthu M (QUIC)" <quic_seevalam@quicinc.com>
Cc: sw@simonwunderlich.de, Jan Fuchs <jf@simonwunderlich.de>
Subject: Re: ath11k: incorrect board_id retrieval
Date: Thu, 16 Dec 2021 09:40:53 +0100 [thread overview]
Message-ID: <273277150.CoJFBkXrIx@ripper> (raw)
In-Reply-To: <DM8PR02MB81992A2920F672C9200B083DF6769@DM8PR02MB8199.namprd02.prod.outlook.com>
[-- Attachment #1.1: Type: text/plain, Size: 646 bytes --]
On Wednesday, 15 December 2021 18:42:13 CET Seevalamuthu M (QUIC) wrote:
> [seevalam] : Incase of QCN9074 in x86 setup, need to program OTP with board_id. Please fuse board id in OTP and try.
Thank you for the confirmation. So it seems like 8devices and Compex aren't
correctly setting the OTP for board_id retrieval when
they manufacture the card. Which basically breaks the retrieval of the
correct BDF (especially when having cards with different board_ids in the
device).
I am now just guessing that it is the same for WCN6855 v2.0 - which would mean
that EmWicon/jjPlus are also not correctly initializing the OTP.
Kind regards,
Sven
[-- 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
next prev parent reply other threads:[~2021-12-16 8:41 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 [this message]
2022-02-18 13:52 ` Sven Eckelmann
2022-04-13 7:01 ` Kalle Valo
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=273277150.CoJFBkXrIx@ripper \
--to=sven@narfation.org \
--cc=ath11k@lists.infradead.org \
--cc=jf@simonwunderlich.de \
--cc=quic_seevalam@quicinc.com \
--cc=sw@simonwunderlich.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.