All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alvin =?unknown-8bit?q?=C5=A0ipraga?= <ALSI@bang-olufsen.dk>
To: iwd@lists.01.org
Subject: Re: [PATCH 6/6] station: disable roaming logic for auto-roaming cards
Date: Thu, 11 Mar 2021 19:02:05 +0000	[thread overview]
Message-ID: <4bc419fb-cfe3-ac16-63f2-f947246ab5f0@bang-olufsen.dk> (raw)
In-Reply-To: <8890bcc3b9f00a5441f1392f1a4005cb333330d9.camel@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2785 bytes --]

Hi James,

On 3/11/21 6:32 PM, James Prestwood wrote:
> Hi Alvin,
> 
> <snip>
> 
>> So to answer your question, I don't know directly, but then I did
>> some
>> searching online and found this thread[1] where a guy does the same
>> grep:
>>
>> $ strings /lib/firmware/brcm/brcmfmac43455-sdio.bin | grep Version
>> 43455c0-roml/43455_sdio-pno-aoe-pktfilter-pktctx-wfds-mfp-dfsradar-
>> wowlpf-idsup-idauth-noclminc-clm_min-obss-obssdump-swdiv-gtkoe-
>> roamprof-txbf-ve-sae-sr-okc-bpd
>> Version: ...
>>
>> And there I can see 'sae', so there's a good chance that this
>> firmware
>> supports SAE offload. For WPA3 and FT offload I don't know what the
>> corresponding string is but I believe (firmware driven) FT is a
>> standard
>> feature so it might not have its own string. More on that later...
> 
> As a side note here on SAE, would you mind just doing 'iw list' and
> seeing if SAE_OFFLOAD is listed in the extended feature list (for your
> card). I also see 'sae' when I grep the FW, but its still not included
> in ext features.

Sure - I just checked and `iw list | grep SAE` doesn't show anything.

> 
> I have trying this on a Raspberry Pi, which is the brcmfac43455-
> sdio.bin FW. I see you mentioned "cyfmac43455-sdio.bin", which I'm
> guessing is a non-released version or something? I got my FW from an
> official cypress release, Nov. 2020 I believe it was.

Hmm ok, so maybe the 'sae' string doesn't mean anything after all... 
sorry for the noise.

Regarding the filename stuff: Cypress decided to change the FW filenames 
at some point last year, which is a bit maddening because I believe this 
stuff is also considered ABI. But the brcmfmac* and cyfmac* 
.bin/clm_blob/txt files are pretty much interchangeable AFAIK, so long 
as the numerical part of the chipsets matche, regardless of the BCM or 
CYW prefix. If you use a mainline kernel, I think it expects brcmfmac* 
files. If you use the Cypress release (see link in my last reply), then 
it will want the cyfmac* files.

If you search the internet you will find RPi users also confused by 
this, and that it seems like both Broadcom and Cypress claim to be 
vendors of the RPi wireless chipset. KeithG seems to have the same 
experience. But renaming the files to whatever your driver is expecting 
is all you have to do.

The cyw*.bin files I grepped are from the Cypress FMAC/FW release I 
linked in my last mail. It's the same thing KeithG linked too - just 
that he linked the .zip directly. Another source of firmwares is from 
muRata, who make SoMs based on the Cypress chipsets. They have a 
separate release repository for firmwares[1] and maybe one of those 
might have SAE support. Otherwise I'm out of ideas...

Kind regards,
Alvin

  parent reply	other threads:[~2021-03-11 19:02 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-10 20:27 [PATCH 1/6] netdev: use NL80211_STA_INFO_SIGNAL rather than average James Prestwood
2021-03-10 20:27 ` [PATCH 2/6] scan: allow 'faked' scan_bss results James Prestwood
2021-03-10 22:25   ` Denis Kenzior
2021-03-10 20:27 ` [PATCH 3/6] nl80211util: add WIPHY_FREQ to parse_attrs support James Prestwood
2021-03-10 21:08   ` Denis Kenzior
2021-03-10 20:27 ` [PATCH 4/6] netdev: station: support full mac roaming James Prestwood
2021-03-10 20:27 ` [PATCH 5/6] wiphy: parse NL80211_ATTR_ROAM_SUPPORT flag James Prestwood
2021-03-10 20:27 ` [PATCH 6/6] station: disable roaming logic for auto-roaming cards James Prestwood
2021-03-10 21:01   ` Denis Kenzior
2021-03-10 21:15     ` James Prestwood
2021-03-10 21:27       ` Denis Kenzior
2021-03-10 21:48         ` James Prestwood
2021-03-11  0:16           ` Alvin =?unknown-8bit?q?=C5=A0ipraga?=
2021-03-11  2:36             ` Denis Kenzior
2021-03-11 11:06               ` Alvin =?unknown-8bit?q?=C5=A0ipraga?=
2021-03-11 17:32                 ` James Prestwood
2021-03-11 18:18                   ` KeithG
2021-03-11 18:45                     ` James Prestwood
2021-03-11 19:02                   ` Alvin =?unknown-8bit?q?=C5=A0ipraga?= [this message]
2021-03-10 21:12 ` [PATCH 1/6] netdev: use NL80211_STA_INFO_SIGNAL rather than average Denis Kenzior
2021-03-10 21:16   ` 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=4bc419fb-cfe3-ac16-63f2-f947246ab5f0@bang-olufsen.dk \
    --to=alsi@bang-olufsen.dk \
    --cc=iwd@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.