Linux-Wireless Archive mirror
 help / color / mirror / Atom feed
From: David Lin <yu-hao.lin@nxp.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"briannorris@chromium.org" <briannorris@chromium.org>,
	Kalle Valo <kvalo@kernel.org>,
	"francesco@dolcini.it" <francesco@dolcini.it>,
	Pete Hsieh <tsung-hsien.hsieh@nxp.com>,
	rafael.beims <rafael.beims@toradex.com>,
	Francesco Dolcini <francesco.dolcini@toradex.com>
Subject: RE: [EXT] Re: [PATCH v10 0/2] wifi: mwifiex: add code to support host mlme
Date: Thu, 18 Apr 2024 09:08:25 +0000	[thread overview]
Message-ID: <PA4PR04MB963815B9FDA6119683A28CADD10E2@PA4PR04MB9638.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <0ED16BAB-6E7D-487C-BBCA-E63FEF37C60D@holtmann.org>

> From: Marcel Holtmann <marcel@holtmann.org>
> Sent: Thursday, April 18, 2024 2:48 PM
> To: David Lin <yu-hao.lin@nxp.com>
> Cc: linux-wireless@vger.kernel.org; LKML <linux-kernel@vger.kernel.org>;
> briannorris@chromium.org; Kalle Valo <kvalo@kernel.org>;
> francesco@dolcini.it; Pete Hsieh <tsung-hsien.hsieh@nxp.com>; rafael.beims
> <rafael.beims@toradex.com>; Francesco Dolcini
> <francesco.dolcini@toradex.com>
> Subject: [EXT] Re: [PATCH v10 0/2] wifi: mwifiex: add code to support host
> mlme
> 
> Hi David,
> 
> > With host mlme:
> > Tested-by: <rafael.beims@toradex.com> #Verdin AM62 IW416 SD Without
> > host mlme:
> > Tested-by: Francesco Dolcini <francesco.dolcini@toradex.com> #
> > 88W8997-SD
> >
> > This series add host based MLME support to the mwifiex driver, this
> > enables WPA3 support in both client and AP mode.
> > To enable WPA3, a firmware with corresponding V2 Key API support is
> > required.
> > The feature is currently only enabled on NXP IW416 (SD8978), and it
> > was internally validated by NXP QA team. Other NXP Wi-Fi chips
> > supported in current mwifiex are not affected by this change.
> 
> I am a bit confused here. If this is just for WPA3 support, then wasn’t this
> suppose to be solved with external_auth support?
> 
> Regards
> 
> Marcel

FW can't support WPA3. In order to support WPA3, driver should leverage MLME of wpa_supplicant and hostapd.
This patch is used to let MLME is running by wpa_supplicant and hostapd instead of handling by FW.

David 

  reply	other threads:[~2024-04-18  9:08 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-18  6:06 [PATCH v10 0/2] wifi: mwifiex: add code to support host mlme David Lin
2024-04-18  6:06 ` [PATCH v10 1/2] wifi: mwifiex: add host mlme for client mode David Lin
2024-04-18  6:37   ` Francesco Dolcini
2024-04-18  8:24     ` [EXT] " David Lin
2024-05-23  0:53   ` Brian Norris
2024-05-24  9:46     ` [EXT] " David Lin
2024-05-24 17:02       ` Brian Norris
2024-05-24 22:00         ` David Lin
2024-05-24 22:54           ` Brian Norris
2024-05-25  0:50             ` David Lin
2024-05-25 11:24               ` David Lin
2024-06-14  2:18               ` David Lin
2024-04-18  6:06 ` [PATCH v10 2/2] wifi: mwifiex: add host mlme for AP mode David Lin
2024-05-23  0:59   ` Brian Norris
2024-05-23  2:20     ` [EXT] " David Lin
2024-06-12 13:11   ` Sascha Hauer
2024-06-14  2:06     ` [EXT] " David Lin
2024-06-14  6:31       ` Sascha Hauer
2024-04-18  6:47 ` [PATCH v10 0/2] wifi: mwifiex: add code to support host mlme Marcel Holtmann
2024-04-18  9:08   ` David Lin [this message]
2024-04-18  9:15     ` [EXT] " Marcel Holtmann
2024-04-19  4:00       ` David Lin
2024-04-19 21:42         ` Brian Norris
2024-04-22  8:34           ` David Lin
2024-04-23  2:29             ` David Lin
2024-04-24  8:11               ` Marcel Holtmann
2024-04-25  2:40                 ` David Lin
2024-04-26  1:08                   ` Brian Norris
2024-05-02  8:34                     ` David Lin
2024-05-13  1:27                       ` David Lin
2024-05-23  0:50                         ` Brian Norris
2024-04-26  1:00               ` Brian Norris
2024-04-26  3:04                 ` David Lin
2024-04-25  2:09             ` David Lin

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=PA4PR04MB963815B9FDA6119683A28CADD10E2@PA4PR04MB9638.eurprd04.prod.outlook.com \
    --to=yu-hao.lin@nxp.com \
    --cc=briannorris@chromium.org \
    --cc=francesco.dolcini@toradex.com \
    --cc=francesco@dolcini.it \
    --cc=kvalo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=rafael.beims@toradex.com \
    --cc=tsung-hsien.hsieh@nxp.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).