From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: KeithG <ys3al35l@gmail.com>
Cc: brcm80211@lists.linux.dev, linux-wireless@vger.kernel.org,
Denis Kenzior <denkenz@gmail.com>,
James Prestwood <prestwoj@gmail.com>
Subject: Re: brcmfmac SAE/WPA3 negotiation
Date: Mon, 16 Dec 2024 10:47:16 +0100 [thread overview]
Message-ID: <caa186d8-1e07-421d-a127-7bb6482ac704@broadcom.com> (raw)
In-Reply-To: <14ec6009-7b91-4a25-9943-f63da91d8c41@broadcom.com>
On 12/16/2024 10:43 AM, Arend van Spriel wrote:
> On 12/16/2024 1:17 AM, KeithG wrote:
>> On Sun, Dec 15, 2024 at 11:33 AM Arend Van Spriel
>> <arend.vanspriel@broadcom.com> wrote:
>>>
>>> On December 15, 2024 5:08:12 PM KeithG <ys3al35l@gmail.com> wrote:
>>>
>>>> On Sun, Dec 15, 2024 at 6:12 AM Arend van Spriel
>>>> <arend.vanspriel@broadcom.com> wrote:
>>>>>
>>>>> On 12/14/2024 2:34 PM, KeithG wrote:
>>>>>> Arend,
>>>>>>
>>>>>> I looked through the info where I got the latest firmware:
>>>>>> https://community.infineon.com/t5/Wi-Fi-Bluetooth-for-Linux/Wi-Fi-
>>>>>> A-class-Linux-Driver-release-FMAC-2024-11-21-Documents/td-p/905045
>>>>>> https://community.infineon.com/t5/AIROC-Wi-Fi-and-Wi-Fi-Bluetooth/
>>>>>> Cypress-Linux-WiFi-Driver-Release-FMAC-2024-11-21/td-p/902888
>>>>>> and did not find anything, but I really do not know what I am
>>>>>> looking for.
>>>>>
>>>>> I think I had a bit more luck and maybe found the needle. I sent out
>>>>> another RFT patch which hopefully gets rid of the BCME_BADLEN error.
>>>>>
>>>>> Regards,
>>>>> Arend
>>>> Arend,
>>>>
>>>> Can you send me a link to that patch? I want to try it.
>>>
>>> Hmm. I explicitly sent it to you, but here is a link to patchwork:
>>>
>>> https://patchwork.kernel.org/project/linux-wireless/
>>> patch/20241215120401.238320-1-arend.vanspriel@broadcom.com/
>>>
>>> You can apply it on top of the other 3 patches.
>>>
>>> Regards,
>>> Arend
>>>
>> Thanks! I got it.
>> I am building now and have tried to apply what I think are the correct
>> patches. They do not apply cleanly and I had to hand edit things. My
>> guess is I messed something up.
>> I will see what happens when I reboot. It'll take a few hours to build
>> on my Pi4 then for me to install it on the 3b+ to test.
>>
>> I hope I understand which are the '3 other' patches.
>>
>> This is the one I got from your link:
>> RFT-brcmfmac-Fix-structure-size-for-WPA3-external-SAE.diff
>>
>> These are what I understand are the '3 other patches'
>> RFT-v2-1-3-wifi-brcmfmac-support-per-vendor-cfg80211-callbacks-and-
>> firmware-events.patch.diff
>> RFT-v2-2-3-wifi-brcmfmac-make-per-vendor-event-map-const.patch.diff
>> RFT-v2-3-3-wifi-brcmfmac-cyw-support-external-SAE-authentication-in-
>> station-mode.patch.diff
>>
>> If they are not correct could you send me links to them and I'll try
>> again.
>
> You got it right. Kuddos.
Ignored my spelling checker, but apparently it should be "kudos".
Another lesson learned today.
Regards,
Arend
next prev parent reply other threads:[~2024-12-16 9:47 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
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 [this message]
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=caa186d8-1e07-421d-a127-7bb6482ac704@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=brcm80211@lists.linux.dev \
--cc=denkenz@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=prestwoj@gmail.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