linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Prestwood <prestwoj@gmail.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: SAE offload on brcmfmac (BCM4345)
Date: Mon, 15 Mar 2021 10:46:56 -0700	[thread overview]
Message-ID: <0378ea17e0a8bdb72d635430ff14edc428591690.camel@gmail.com> (raw)
In-Reply-To: <1262e6e9c7d2ab499c15a3d297ed87206e49711b.camel@gmail.com>

Maybe a simpler question: What brcmfmac cards *do* support SAE offload?
So far I have tried:

BCM4345 (raspberry pi 3 B+)
BCM43602
BCM43242

The last two are quite old (fw dated 2013/2015) so I wouldn't expect
those to work. According to the documentation the BCM4345 should
support SAE offload, but me and several others have tried checking the
extended features and it is not enabled.

Thanks,
James

On Thu, 2021-03-04 at 11:29 -0800, James Prestwood wrote:
> Hi,
> 
> I am trying to get SAE offload support on a BCM4345 (raspberry pi
> B+).
> From what I can tell it appears the Cypress firmware is not enabling
> the right bits. It looks like the brcmfmac driver has all the code to
> enable the extended feature. Here is what I have done so far:
> 
> Cloned raspi linux kernel v5.4
> 
> Downloaded latest Cypress firmware:
> https://community.cypress.com/t5/Resource-Library/Cypress-Linux-WiFi-Driver-Release-FMAC-2020-09-25/ta-p/251089
> 
> Applied the patches from above. Note not *all* the patches applied
> (could be due to already upstreamed), but most did. I did have to fix
> an include issue so brcmfmac/cfg80211.c could reference
> LINUX_CODE_VERSION/LINUX_VERSION.
> 
> Built new kernel/installed etc.
> 
> After that everything built, and I do see SAE offload source code
> which
> sets the ext feature if BRCMF_FEAT_SAE is enabled.
> 
> I see my new kernel here:
> 
> Linux raspberrypi 5.4.83-v7+ #2 SMP Thu Mar 4 10:54:16 PST 2021
> armv7l
> GNU/Linux
> 
> and dmesg shows the new firmware loading:
> 
> [    7.315275] brcmfmac: F1 signature read @0x18000000=0x15264345
> [    7.337608] brcmfmac: brcmf_fw_alloc_request: using
> brcm/brcmfmac43455-sdio for chip BCM4345/6
> [    7.338104] usbcore: registered new interface driver brcmfmac
> [    7.606184] brcmfmac: brcmf_fw_alloc_request: using
> brcm/brcmfmac43455-sdio for chip BCM4345/6
> [    7.616186] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6
> wl0: Mar 23 2020 02:19:54 version 7.45.206 (r725000 CY) FWID 01-
> 88ee44ea
> 
> Yet iw does not have SAE_OFFLOAD set as an extended feature:
> 
> Supported extended features:
> 	* [ 4WAY_HANDSHAKE_STA_PSK ]: 4-way handshake with PSK in
> station mode
> 	* [ 4WAY_HANDSHAKE_STA_1X ]: 4-way handshake with 802.1X in
> station mode
> 	* [ DFS_OFFLOAD ]: DFS offload
> 
> Thanks,
> James
> 


  reply	other threads:[~2021-03-15 17:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-04 19:29 SAE offload on brcmfmac (BCM4345) James Prestwood
2021-03-15 17:46 ` James Prestwood [this message]
2021-03-15 19:25   ` Alvin Šipraga

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=0378ea17e0a8bdb72d635430ff14edc428591690.camel@gmail.com \
    --to=prestwoj@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    /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 NNTP newsgroup(s).