From: Sven Eckelmann <sven@narfation.org>
To: ath11k@lists.infradead.org, Lavanya Suresh <lavaks@codeaurora.org>
Cc: kvalo@codeaurora.org
Subject: ath11k: QCN9074: Incompatible board-2.bin for 6GHz
Date: Fri, 26 Nov 2021 11:52:42 +0100 [thread overview]
Message-ID: <2091899.pNsEtq2SQc@ripper> (raw)
Hi,
I wanted to use an 8devices Pineapple6 device on x86. But the board_id of this
card came always in as 255 (and not as a valid 6GHz capable board_id). I've
contacted the support and they told me to use the QCA BDF with the board_id
162 for this card. So I've downloaded
2.4.0.1.r1/WLAN.HK.2.4.0.1.r1-00019-QCAHKSWPL_SILICONZ-1/board-2.bin [1],
extracted it and moved it to /lib/firmware/ath11k/QCN9074/hw1.0/board.bin.
I've also added the (not yet upstreamed) 6GHz regulatory support to
ath11k [2]. But to my surprise, the WMI_REG_CHAN_LIST_CC_EXT_EVENTID never
came in. Instead, a WMI_REG_CHAN_LIST_CC_EVENTID was received. This resulted
in a output like:
ath11k_pci 0000:01:00.0: No reg rules available
ath11k_pci 0000:01:00.0: failed to extract regulatory info from received event
------------[ cut here ]------------
WARNING: at drivers/net/wireless/ath/ath11k/wmi.c:7255
The warning from ath11k (which breaks the device btw) is from
if (!(reg_info->num_2g_reg_rules + reg_info->num_5g_reg_rules)) {
ath11k_warn(ab, "No regulatory rules available in the event info\n");
kfree(tb);
return -EINVAL;
}
I found out that this is actually caused by the BDF. If I've extracted the
board.bin from the TIP board-2.bin [3] (which seems to come from the QCA
ATH.11.4 CS release). With this version, it seems to work fine. I haven't yet
found out what the relevant change is - but if someone has hints then this
would could be interesting for other devices which should be added to things
like OpenWrt.
Maybe Kalle Valo could upload a new board-2.bin for QCN9074 hw1.0 which has
the problem solved.
And it would also be nice when the authors of the
WMI_REG_CHAN_LIST_CC_EXT_EVENTID support would send this stuff upstream. I
just find it interesting that the assoc patches are already part of
upstream [4,5] - even when the reg support is still missing. There are a lot
more patches in there which are missing upstream.
Kind regards,
Sven
[1] https://github.com/kvalo/ath11k-firmware/commit/ae4f4f64ed14097dc24a8d686fa60e932cba4868/QCN9074/hw1.0/testing/2.4.0.1.r1/WLAN.HK.2.4.0.1.r1-00019-QCAHKSWPL_SILICONZ-1/board-2.bin
[2] https://source.codeaurora.org/quic/qsdk/oss/system/feeds/wlan-open/tree/mac80211/patches/302-ath11k-Add-support-to-parse-new-wmi-event-for-6G-reg.patch?h=NHSS.QSDK.11.4.0.5
[3] https://github.com/Telecominfraproject/wlan-ap/blob/main/feeds/wifi-ax/ath11k-firmware/files/QCN9000/board-2.bin
[4] https://source.codeaurora.org/quic/qsdk/oss/system/feeds/wlan-open/tree/mac80211/patches/206-ath11k-add-6ghz-params-in-peer-assoc-cmd.patch?h=NHSS.QSDK.11.4.0.5
[5] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c3a7d7eb4c9853bb457b792cef42ddd4a029a914
[6] https://source.codeaurora.org/quic/qsdk/oss/system/feeds/wlan-open/tree/mac80211/patches/302-ath11k-add-177-channel-to-5G-channel-list.patch?h=NHSS.QSDK.11.4.0.5
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
next reply other threads:[~2021-11-26 10:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-26 10:52 Sven Eckelmann [this message]
2021-11-26 14:54 ` ath11k: QCN9074: Incompatible board-2.bin for 6GHz John Crispin
2021-11-26 15:55 ` Mark Herbert
2021-11-29 17:19 ` Sven Eckelmann
2021-12-21 14:52 ` Kalle Valo
2021-12-21 22:58 ` Sven Eckelmann
2022-04-13 7:06 ` Kalle Valo
2022-04-13 7:26 ` Sven Eckelmann
2022-04-13 8:01 ` Kalle Valo
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=2091899.pNsEtq2SQc@ripper \
--to=sven@narfation.org \
--cc=ath11k@lists.infradead.org \
--cc=kvalo@codeaurora.org \
--cc=lavaks@codeaurora.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