Re: [PATCH] wifi: brcmfmac: configure SAE PWE method for external SAE AP
Gokul Sivakumar <[email protected]> Wed, 29 Jul 2026 12:07:09 +0000
| Newsgroups | dev.linux.lists.brcm80211,org.kernel.vger.linux-kernel,org.kernel.vger.linux-wireless |
|---|---|
| Message-ID | <7jvxg3jlrsxs4sy2pysyrtwzvczxjczeaxa5xzdojk27vcmrc6@bvaar7uqofby> |
On 07/29, Arend van Spriel wrote: > On 29/07/2026 07:34, Bogdan Nicolae wrote: > > When bringing up a WPA3-SAE SoftAP with external (user space) SAE, the > > driver never told the firmware which SAE Password Element (PWE) method to > > accept. The firmware was observed to corrupt its heap over time due to > > this omission, leading to firmware trap (data abort in heap allocator). > > > > Parse the beacon IEs on start_ap() and set the extsae_pwe iovar > > accordingly: 2 when the RSNX IE advertises H2E, 1 when an H2E-only > > membership selector is present, 0 otherwise. This matches the behaviour > > of the upstream/vendor driver and only applies to SAE-capable APs when > > external SAE is supported. > > This makes sense, but may I ask what device do you have? Suspect it is a > Cypress/Infineon chip. I could not find the iovar in our (Broadcom bca) > code base so I suspect it is vendor specific. Arend, yes, this an Infineon vendor specific Firmware IOVAR. Seems like he got the patch from Infineon's downstream brcmfmac github and applied it on upstream brcmfmac driver as it is with minor changes. Bogdan, from Infineon we are currently working on a patch to adopt our "extsae_pwe" vendor changes for the upstream brcmfmac driver. Because it can't be applied as it is on upstream brcmfmac without affecting other firmware vendors. We will submit our "extsae_pwe" patch for upstream review in a few days. Kindly wait. Regards, Gokul