From: Conn O'Griofa <connogriofa@gmail.com>
To: "Nagashima, Shunsuke" <shunsuke@nagashi.ma>,
Loic Poulain <loic.poulain@oss.qualcomm.com>
Cc: Jeff Johnson <jjohnson@kernel.org>,
linux-wireless@vger.kernel.org, ath10k@lists.infradead.org,
linux-kernel@vger.kernel.org, David Heidelberg <david@ixit.cz>,
Fabricio Akio <fabricioakio@gmail.com>,
Aleksei Kharlamov <aleksei.kharlamov@gmx.de>
Subject: Re: [PATCH ath-next 1/3] wifi: ath10k: set the PMF peer flag on WCN3990
Date: Mon, 2 Nov 2026 23:57:18 +0000 [thread overview]
Message-ID: <c45bdcae-63da-4552-9e35-59ec6a71621a@gmail.com> (raw)
In-Reply-To: <CACB3TCKq--tdL6j+uGR_dxGdy-gHxQhY8p0h6xxqi_4Fd3VEOQ@mail.gmail.com>
On 02/11/2026 22:51, Nagashima, Shunsuke wrote:
> Aleksei, Conn: a firmware file update only helps devices that load that
> file. If you have time, could you make the same change to the
> firmware-N.bin your device loads, test it, and send it to
> linux-firmware?
I can confirm that the unmodified driver with a patched firmware fixes
the issue on QCA9377 as well. I appended the mfp-support flag to the
existing flags for both firmware variants that are relevant to my device:
./ath10k-fwencoder --modify --features=ignore-otp-result,mfp-support
firmware-5.bin
./ath10k-fwencoder --modify
--features=wowlan,ignore-otp-result,mfp-support firmware-6.bin
Testing each firmware individually confirms the flag is now present, and
both firmware versions can now reach 300Mbps.
ath10k_pci 0000:02:00.0: firmware ver WLAN.TF.1.0-00002-QCATFSWPZ-5 api
5 features ignore-otp,mfpcrc32 18db2397
ath10k_pci 0000:02:00.0: firmware ver WLAN.TF.2.1-00021-QCARMSWP-1 api 6
features wowlan,ignore-otp,mfpcrc32 02bceae2
I would be happy to submit the modified firmware, but I am skeptical
that it would be accepted? I'm not sure if I've ever observed
unofficial/modified wifi firmware to ever have been accepted into
linux-firmware (which seems completely understandable, given the risks).
Conn
next prev parent reply other threads:[~2026-11-02 23:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 0:17 [PATCH ath-next 0/3] wifi: ath10k: WCN3990 station fixes for PMF and failed connections Shunsuke Nagashima via B4 Relay
2026-10-16 0:17 ` [PATCH ath-next 1/3] wifi: ath10k: set the PMF peer flag on WCN3990 Shunsuke Nagashima via B4 Relay
2026-10-19 23:04 ` Aleksei Kharlamov
2026-10-20 2:47 ` Nagashima, Shunsuke
2026-10-20 14:12 ` Aleksei Kharlamov
2026-10-30 18:17 ` Conn O'Griofa
2026-11-02 11:56 ` Loic Poulain
2026-11-02 22:51 ` Nagashima, Shunsuke
2026-11-02 23:57 ` Conn O'Griofa [this message]
2026-11-03 9:20 ` Loic Poulain
2026-11-03 11:07 ` Nagashima, Shunsuke
2026-10-16 0:17 ` [PATCH ath-next 2/3] wifi: ath10k: skip disassociation down for a station vdev that is not up Shunsuke Nagashima via B4 Relay
2026-10-16 0:17 ` [PATCH ath-next 3/3] wifi: ath10k: bring down a station vdev that never came up Shunsuke Nagashima via B4 Relay
2026-10-19 13:12 ` James Prestwood
2026-10-19 22:56 ` Nagashima, Shunsuke
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=c45bdcae-63da-4552-9e35-59ec6a71621a@gmail.com \
--to=connogriofa@gmail.com \
--cc=aleksei.kharlamov@gmx.de \
--cc=ath10k@lists.infradead.org \
--cc=david@ixit.cz \
--cc=fabricioakio@gmail.com \
--cc=jjohnson@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=loic.poulain@oss.qualcomm.com \
--cc=shunsuke@nagashi.ma \
/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®