> From: Marcel Holtmann <marcel@xxxxxxxxxxxx> > Sent: Wednesday, April 24, 2024 4:11 PM > To: David Lin <yu-hao.lin@xxxxxxx> > Cc: Brian Norris <briannorris@xxxxxxxxxxxx>; linux-wireless@xxxxxxxxxxxxxxx; > LKML <linux-kernel@xxxxxxxxxxxxxxx>; Kalle Valo <kvalo@xxxxxxxxxx>; > francesco@xxxxxxxxxx; Pete Hsieh <tsung-hsien.hsieh@xxxxxxx>; rafael.beims > <rafael.beims@xxxxxxxxxxx>; Francesco Dolcini > <francesco.dolcini@xxxxxxxxxxx> > Subject: Re: [EXT] [PATCH v10 0/2] wifi: mwifiex: add code to support host > mlme > > Hi David, > > > Johannes agreed that cfg80211 is the correct way for the development > > of mwifiex > > (mac80211 can't offload association process to driver/FW). > > that was never my question here. > This is previous topic discussed with Johannes to confirm cfg80211 is correct decision for NXP FW. > > This patch is used to fully leverage SME of wpa_supplicant and hostapd > which can complete the missing WPA3 feature of mwifiex. > > The patch series had been reviewed and discussed. It looks like there is no > more comments for patch v10. > > I wonder can patch v10 be accepted by you? > > If your hardware is a FullMac hardware then what is the point in now > separating auth/assoc out. Is this done just for WPA3 or also for WPA2/WPA1. Yes. Our FW can's support WPA3, so this patch is used to hook separating auth/assoc to leverage SME of wpa_supplicant and hostapd. WPA2 is also handled by SME of wpa_supplicant and hostapd. > Are you no longer a FullMac hardware? You can check previous discussion with Johannes, FW still needs to involve association process, so mac80211 is not suitable for NXP FW. > > You keep saying that you just want to support WPA3 and if previously the HW > worked as FullMac hardware, then external_auth should be the way to go for > having SAE handled by wpa_supplicant (or iwd for that matter). Although external_auth is one way to support SAE, but we think hook separating auth/assoc will be the better way to resolve this issue. In this way, offloading SME to wpa_supplicant/hostpad will let any future changes be easy to support (we only need to check if there is anything that we should do when converting association request to the association command supported by FW). > > Now if you are fully embracing to auth/assoc and we can remove the support > for the connect ops, then lets do it. However I don’t see anything properly > described in the commit message. You keep saying WPA3 support and nothing > else explain what the new Key V2 API of the firmware would do. We give a flag to let user to decide to use connect ops or separating auth/assoc. We will remove connect ops for our new nxpwifi driver. New key V2 API supports more key solutions. > > Regards > > Marcel Thanks, David
