From: James Prestwood <prestwoj@gmail.com>
To: Arend van Spriel <arend.vanspriel@broadcom.com>,
KeithG <ys3al35l@gmail.com>
Cc: linux-wireless@vger.kernel.org, brcm80211@lists.linux.dev,
Ting-Ying Li <tingying.li@cypress.com>,
Ting-Ying Li <tingying.li@infineon.com>
Subject: Re: [RFT] brcmfmac: Fix structure size for WPA3 external SAE
Date: Wed, 12 Feb 2025 05:42:18 -0800 [thread overview]
Message-ID: <69874369-495c-4698-af1f-502d21371f7d@gmail.com> (raw)
In-Reply-To: <20241215120401.238320-1-arend.vanspriel@broadcom.com>
Hi Arend,
On 12/15/24 4:04 AM, Arend van Spriel wrote:
> From: Ting-Ying Li <tingying.li@cypress.com>
>
> Add pmkid parameter in "brcmf_auth_req_status_le" structure to
> align the buffer size defined in firmware "wl_auth_req_status"
> structure.
>
> Signed-off-by: Ting-Ying Li <tingying.li@infineon.com>
> [arend: adapted path to apply to per-vendor variant]
> Signed-off-by: Arend van Spriel <arend.vanspriel@broadcom.com>
> ---
> .../net/wireless/broadcom/brcm80211/brcmfmac/cyw/fwil_types.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cyw/fwil_types.h b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cyw/fwil_types.h
> index 18129adb5dc2..1cbe66526d82 100644
> --- a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cyw/fwil_types.h
> +++ b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cyw/fwil_types.h
> @@ -54,6 +54,7 @@ struct brcmf_auth_req_status_le {
> u8 peer_mac[ETH_ALEN];
> __le32 ssid_len;
> u8 ssid[IEEE80211_MAX_SSID_LEN];
> + u8 pmkid[WLAN_PMKID_LEN];
> };
>
> /**
>
> base-commit: 1cac3bd863bef434d43e6b0554ac5d7f7f6350fe
> prerequisite-patch-id: d5b3eb93d54bd6a0508a91f4627ec3e59a810928
> prerequisite-patch-id: 653281e1349a038c7f48b3513243f3211fffab9e
> prerequisite-patch-id: 0e47ab711ef159237e20c860834d3ac269b05eb2
I've tested this and can also confirm it does fix external auth on
brcmfmac. I adapted it to work with the upstream 6.6 raspi kernel and
had no issues using IWD + external auth to connect to a WPA3 network. Is
this something that can be upstreamed?
This is the firmware I'm using (no changes to the default raspi distro):
Firmware: BCM4345/6 wl0: Aug 29 2023 01:47:08 version 7.45.265 (28bca26
CY) FWID 01-b677b91b
Thanks,
James
next prev parent reply other threads:[~2025-02-12 13:42 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 14:30 brcmfmac SAE/WPA3 negotiation KeithG
2024-12-12 14:24 ` KeithG
2024-12-12 17:48 ` James Prestwood
2024-12-12 20:17 ` Arend van Spriel
2024-12-13 15:13 ` KeithG
2024-12-13 17:35 ` Arend Van Spriel
2024-12-14 0:40 ` KeithG
2024-12-14 13:34 ` KeithG
2024-12-15 12:04 ` [RFT] brcmfmac: Fix structure size for WPA3 external SAE Arend van Spriel
2025-02-12 13:42 ` James Prestwood [this message]
2025-02-12 14:13 ` KeithG
2025-02-12 14:25 ` James Prestwood
2024-12-15 12:12 ` brcmfmac SAE/WPA3 negotiation Arend van Spriel
2024-12-15 16:08 ` KeithG
2024-12-15 17:33 ` Arend Van Spriel
2024-12-16 0:17 ` KeithG
2024-12-16 9:43 ` Arend van Spriel
2024-12-16 9:47 ` Arend van Spriel
2024-12-16 12:21 ` KeithG
2024-12-16 19:49 ` Arend van Spriel
2024-12-17 0:13 ` KeithG
2024-12-17 13:47 ` Arend van Spriel
2024-12-18 0:21 ` KeithG
2024-12-18 10:21 ` Arend van Spriel
2024-12-18 14:10 ` KeithG
2024-12-19 1:46 ` KeithG
2024-12-19 12:46 ` James Prestwood
2024-12-19 13:38 ` KeithG
2024-12-19 13:42 ` James Prestwood
2024-12-19 14:22 ` KeithG
2024-12-21 16:14 ` KeithG
2024-12-22 5:30 ` KeithG
2024-12-22 22:02 ` KeithG
2024-12-29 4:07 ` KeithG
2024-12-29 7:39 ` Arend Van Spriel
2024-12-29 23:08 ` KeithG
2025-01-04 18:28 ` brcmfmac SAE/WPA3 negotiation - Part 2 KeithG
2025-01-06 0:41 ` KeithG
2025-01-06 15:26 ` Denis Kenzior
2025-01-06 17:13 ` KeithG
2025-01-10 2:19 ` KeithG
2025-01-25 16:37 ` KeithG
2025-01-27 14:28 ` James Prestwood
2025-01-27 15:09 ` KeithG
2025-01-27 15:20 ` James Prestwood
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=69874369-495c-4698-af1f-502d21371f7d@gmail.com \
--to=prestwoj@gmail.com \
--cc=arend.vanspriel@broadcom.com \
--cc=brcm80211@lists.linux.dev \
--cc=linux-wireless@vger.kernel.org \
--cc=tingying.li@cypress.com \
--cc=tingying.li@infineon.com \
--cc=ys3al35l@gmail.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