From: "Ingo A. Kubbilun" <ingo.kubbilun@gmail.com>
To: Jeff Johnson <jjohnson@kernel.org>
Cc: linux-wireless@vger.kernel.org, ath11k@lists.infradead.org,
linux-kernel@vger.kernel.org,
"Ingo A. Kubbilun" <ingo.kubbilun@gmail.com>
Subject: [PATCH] wifi: ath11k: use the NFA765 firmware on the ASUS Vivobook S16 S3607QA
Date: Fri, 20 Nov 2026 21:09:34 +0100 [thread overview]
Message-ID: <20261120200940.81577-1-ingo.kubbilun@gmail.com> (raw)
The ASUS Vivobook S 16 S3607QA carries a WCN6855 hw2.1 NFA765 module
(Windows board data: bdwlan_wcn685x_2p1_nfa765a_AS_SA_S3607QA.elf).
With the default WCN6855 hw2.1 firmware the target crashes right after
the board data download; the NFA765 build from linux-firmware
(ath11k/WCN6855/hw2.1/nfa765/) works.
Add the machine to the usecase firmware table, replacing the deprecated
firmware-name property in the device tree.
Developed with the help of an AI coding assistant (Anthropic Claude),
which drafted the changes from the Windows ACPI tables, existing device
trees and test logs; reviewed, built and tested on the device by the
submitter.
Signed-off-by: Ingo A. Kubbilun <ingo.kubbilun@gmail.com>
---
drivers/net/wireless/ath/ath11k/core.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/net/wireless/ath/ath11k/core.c b/drivers/net/wireless/ath/ath11k/core.c
index 766ae27306f4..37e443a18d31 100644
--- a/drivers/net/wireless/ath/ath11k/core.c
+++ b/drivers/net/wireless/ath/ath11k/core.c
@@ -1049,6 +1049,7 @@ static const struct __ath11k_core_usecase_firmware_table {
const char *compatible;
const char *firmware_name;
} ath11k_core_usecase_firmware_table[] = {
+ { ATH11K_HW_WCN6855_HW21, "asus,vivobook-s16-s3607qa", "nfa765"},
{ ATH11K_HW_WCN6855_HW21, "qcom,hamoa-iot-evk", "nfa765"},
{ ATH11K_HW_WCN6855_HW21, "qcom,lemans-evk", "nfa765"},
{ ATH11K_HW_WCN6855_HW21, "qcom,monaco-evk", "nfa765"},
base-commit: 6d582d78fad9d828e575ca0cdcff8ea47a77220b
prerequisite-patch-id: ae6c33cce4db2472b5aa360b5e6cbf29763cfd69
prerequisite-patch-id: 85373c0c0ff98ec4cda496c612feffd19f715d52
prerequisite-patch-id: d752bf7c6f8768fa3d4d39387455c3d4551a8481
prerequisite-patch-id: 56220a324770319f2420a2b114db8fd8c0c6b7e9
prerequisite-patch-id: 78692cb7c49dbb17552ec082f147c878aaf38761
--
2.47.3
reply other threads:[~2026-11-20 20:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261120200940.81577-1-ingo.kubbilun@gmail.com \
--to=ingo.kubbilun@gmail.com \
--cc=ath11k@lists.infradead.org \
--cc=jjohnson@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.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
all inboxes | Powered by JetHome®