From: Francesco Dolcini <francesco@dolcini.it>
To: Brian Norris <briannorris@chromium.org>
Cc: Francesco Dolcini <francesco@dolcini.it>,
rafael@beims.me, Rafael Beims <rafael.beims@toradex.com>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] wifi: mwifiex: enable host mlme on sdio W8997 chipsets
Date: Thu, 29 May 2025 09:20:28 +0200 [thread overview]
Message-ID: <20250529072028.GA75868@francesco-nb> (raw)
In-Reply-To: <aDdCP_lvlyvk9J3n@google.com>
Hello Brian,
On Wed, May 28, 2025 at 10:05:03AM -0700, Brian Norris wrote:
> On Fri, May 23, 2025 at 09:26:04AM +0200, Francesco Dolcini wrote:
> > On Thu, May 22, 2025 at 10:24:14AM -0700, Brian Norris wrote:
> > > On Wed, May 21, 2025 at 07:19:34AM -0300, rafael@beims.me wrote:
> > > > From: Rafael Beims <rafael.beims@toradex.com>
> > > >
> > > > Enable the host mlme flag for W8997 chipsets so WPA3 can be used.
> > > > This feature depends on firmware support (V2 API key), which may not be
> > > > available in all available firmwares.
> > >
> > > Is it available in *any* W8997 firmware? Or particularly, is it
> > > available in the firmware in linux-firmware.git? Judging by its git
> > > history, the answer is "no", in which case this is definitely NAK'd.
> >
> > mrvl/sdsd8997_combo_v4.bin, from linux-firmware GIT, 16.92.21.p137
> > version. From an off-list chat with Rafael he confirmed me that this is
> > what he used for testing.
>
> linux-firmware.git claims to hold W16.68.1.p197.1. Either WHENCE is
> wrong, or that sounds like a completely different branch. Are you sure
> about that?
Nope, I did a mistake :-). Wrong copy/paste.
[ 5.956510] mwifiex_sdio mmc2:0001:1: info: FW download over, size 623352 bytes
...
[ 6.825456] mwifiex_sdio mmc2:0001:1: WLAN FW is active
...
[ 12.171950] mwifiex_sdio mmc2:0001:1: host_mlme: enable, key_api: 2
[ 12.226206] mwifiex_sdio mmc2:0001:1: info: MWIFIEX VERSION: mwifiex 1.0 (16.68.1.p197)
root@verdin-imx8mm-14700070:~# strings /lib/firmware/mrvl/sdsd8997_combo_v4.bin |grep 16
$Id: w8997o-V4, RF878X, FP68_LINUX, 16.68.1.p197.1 $
f62026ad508304fdadd9ebb5b500a6b4 /lib/firmware/mrvl/sdsd8997_combo_v4.bin
from commit 211fbc287a0b ("linux-firmware: Update FW files for MRVL SD8997 chips")
> The firmware versions above don't match up to me. But if we confirm
> that:
> (a) this API is available in a linux-firmware.git firmware for this chip
> and
> (b) someone includes a valid linux-firmware.git version that they tested
> in the changelog
>
> then maybe this is OK. As it stands now though, no.
Right, my fault, now it should be clarified. Rafael, can you prepare a
v2 patch with all this information properly written in the commit message?
Francesco
next prev parent reply other threads:[~2025-05-29 7:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-21 10:19 [PATCH] wifi: mwifiex: enable host mlme on sdio W8997 chipsets rafael
2025-05-22 17:24 ` Brian Norris
2025-05-23 7:26 ` Francesco Dolcini
2025-05-28 17:05 ` Brian Norris
2025-05-29 7:20 ` Francesco Dolcini [this message]
2025-05-28 10:48 ` Francesco Dolcini
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=20250529072028.GA75868@francesco-nb \
--to=francesco@dolcini.it \
--cc=briannorris@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=rafael.beims@toradex.com \
--cc=rafael@beims.me \
/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