All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: Mariusz <enebeo@gmail.com>
Cc: walde <waldemar.stroh@uni-siegen.de>,
	"ath11k@lists.infradead.org" <ath11k@lists.infradead.org>
Subject: Re: Wallys DR9074-6E(PN02.7) QCN9074 refuses to work on 6GHz band
Date: Tue, 06 Dec 2022 09:56:22 +0100	[thread overview]
Message-ID: <23529001.ouqheUzb2q@ripper> (raw)
In-Reply-To: <3684626.iIbC2pHGDl@sven-l14>


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

On Friday, 18 November 2022 15:05:49 CET Sven Eckelmann wrote:
> Wallystech has to find the correct document on createpoint which describes the 
> process. It was something like "module" "board id" "fusing". But it is not the 
> "Board ID Fusing for 802.11ax WLAN AP Chipsets" which only describes the way 
> how you would to it for thei internal wifi of the IPQ807x/IPQ60xx/... SoC.
> You/they are searching for the corresponding document for Pine IPQ9074. Most 
> likely hidden in some QDART documents.

It seems like this can be found easier via the search terms "Steps to fuse 
board ID in OTP for QCN9074". For example in document "80-YC644-3 Rev. A" on 
page 62. Qualcomm wrote there that this is needed for cards but can be skipped 
for internal radio - must likely referring there to the possibility to 
overwrite the board_id via devicetree (or using other hacks like providing 
only the specific board.bin instead of the board-2.bin).

I cannot say much about the document but is basically telling them to use 
QDART and enable the option to write a specific "bdf version" (yes, Qualcomm 
has many names for the same things).

There is also another documents which describe similar methods for various 
chips. For example "Fusing board ID to OTP in QCN61xx" in 80-19559-1 Rev. AA 
on page 76. Here they have a lot less steps - only the ones which set the
"bdf version".

At the end, these are documents which are only released under NDA and which 
need tools which you also can only get under NDA. So the manufacturer of these 
devices has to take care to write the board_id (or "bdf version") to the OTP 
before shipping them out to customers or resellers.

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

  parent reply	other threads:[~2022-12-06  8:56 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.7.1667674802.1691884.ath11k@lists.infradead.org>
2022-11-07 16:07 ` Wallys DR9074-6E(PN02.7) QCN9074 refuses to work on 6GHz band Nagarajan Maran (QUIC)
2022-11-07 18:57   ` Mariusz
2022-11-08 21:03     ` Mariusz
     [not found]   ` <CAJrE-q73Jt8MfGn4bbyPs_VEb5DcjLMb7BWBp5MjMDjhZ2g5Wg@mail.gmail.com>
     [not found]     ` <MW2PR02MB38992059ED67678172D6604DED059@MW2PR02MB3899.namprd02.prod.outlook.com>
2022-11-15 10:02       ` Mariusz
2022-11-15 18:29         ` walde
2022-11-15 19:18           ` Mariusz
2022-11-18 11:26           ` Sven Eckelmann
2022-11-18 12:48             ` Mariusz
2022-11-18 14:05               ` Sven Eckelmann
2022-11-19 13:39                 ` Mariusz
2022-11-19 15:16                   ` Robert Marko
2022-11-19 16:09                     ` Mariusz
2022-11-20  8:13                     ` Mariusz
2022-11-22 15:14                       ` Mariusz
2022-12-06  8:56                 ` Sven Eckelmann [this message]
2022-11-17 16:51         ` Mariusz
2022-11-05 11:23 Mariusz
2022-12-17 10:31 ` 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=23529001.ouqheUzb2q@ripper \
    --to=sven@narfation.org \
    --cc=ath11k@lists.infradead.org \
    --cc=enebeo@gmail.com \
    --cc=waldemar.stroh@uni-siegen.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.