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: Fri, 18 Nov 2022 15:05:49 +0100	[thread overview]
Message-ID: <3684626.iIbC2pHGDl@sven-l14> (raw)
In-Reply-To: <CAJrE-q7GshGMSoiP8Vb9itUvap2=tWHqQnDFnckzcRNNpya6Bw@mail.gmail.com>


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

On Friday, 18 November 2022 13:48:43 CET Mariusz wrote:
> Mine is from a different supplier - Wallys - and I bought it 2 weeks
> ago but not sure how old their stock is. PCB looks slightly different
> than Pinapple's. Is it likely to have the same issue?

It definitely has the same issue (because you reported that board_id is 
255/0xff) but I have no idea whether Wallytech ever fixed it. At least I was 
never in contact about this problem with them. But sending around precompiled 
kernel module binaries (for an unknown kernel build), with some hacks to fix 
their hardware production errors (missing module id fusing in the OTP for 
their separately sold modules), doesn't make me confident that they are able 
to solve this problem correctly.

In their defense, QCA doesn't make it really easy. It seems like their 
reference designs with Pine on 6Ghz are (mostly?) for (embedded Linux) APs 
which use the normal flash (NOR or NAND) to store the calibration data. And 
for these devices, they use the devicetree (or various other hacks) to load 
the correct board data.

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.


Regarding the problem that some countries are not allowing 6GHz: You have to 
either get a firmware from QCA which has it enabled or you modify the BDFs 
("board-" files in the board-2.bin) to enable 6GHz in the (enabled) embedded 
REGDB of the BDFs for the specific country. Unfortunately, the data structures 
of the BDF are not officially documented and you would need an official QSDK/
ATH.11.X release from QCA to fetch the bdf2txt.py, txt2bdf.py and the 
corresponding template for your BDF to extract and modify it.

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

  reply	other threads:[~2022-11-18 14:06 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 [this message]
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
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=3684626.iIbC2pHGDl@sven-l14 \
    --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.