Wallys DR9074-6E(PN02.7) QCN9074 refuses to work on 6GHz band

[Sven Eckelmann]

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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.infradead.org/pipermail/ath11k/attachments/20221118/df6bde44/attachment.sig>