Linux on Apple ARM platform development
 help / color / mirror / Atom feed
From: Paul Fertser <fercerpav@gmail.com>
To: Daniel Berlin <dberlin@dberlin.org>
Cc: Hector Martin <marcan@marcan.st>, asahi@lists.linux.dev
Subject: Re: Testing bits/080-wifi on BCM4345/6 (was: Re: [PATCH] wifi: brcmfmac: cfg80211: Use WSEC to set SAE password)
Date: Sat, 23 Dec 2023 18:28:13 +0300	[thread overview]
Message-ID: <ZYb8jf3a/CsI3/D2@home.paul.comp> (raw)
In-Reply-To: <CAF4BwTXJWYGT+8jp9dzxmSN7wbk7xZuy4tNSQDhxJ66UzhhgWw@mail.gmail.com>

Hey Daniel,

Thank you for a rather elaborate reply, wishing you a joyful and
refreshing vacation.

On Sat, Dec 23, 2023 at 09:07:17AM -0600, Daniel Berlin wrote:
> The freq differences below are regulatory - the default of the driver before
> fixing would get stuck in it's default custom regulatory domain, which is 20dbm
> for everything.

I don't complain, just noticed it changed. What bothers me more is
every other channel in 5 GHz disabled by default which would make only
VHT20 work there.

> They should get re enabled if you move to a real domain.

I will try it later.

> I am happy to fix the sae issue when I get back if you are willing to recompile
> with the tracing flags on and get me some logs.

Sure.

> If it becomes complex I'll buy apinebook pro to test with.

I do not recommend that at all, it would be much much easier to use a
popular (so that it's supported by upstream kernel) SBC with same SDIO
module and just boot the kernel + minimal initramfs userspace via TFTP
over wired Ethernet.

> AP mode I'll see if I can fix it - it's not really tested well.  I can probably
> make local progress on this first.

Again, I'm not complaining, just tested what I could quickly test. I'm
surprised Asahi users seem to have not yet explored the topic of
allowed interface combinations, it would be curious to learn how it
works on those "more advanced" broadcom modules you got.

> P2P will also likely break if you haven't tried it.

Not even once in my life :)

-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercerpav@gmail.com

  parent reply	other threads:[~2023-12-23 15:28 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-07  6:05 [PATCH] wifi: brcmfmac: cfg80211: Use WSEC to set SAE password Hector Martin
2023-11-08 11:12 ` Neal Gompa
2023-12-17 11:25 ` Kalle Valo
2023-12-19  8:52   ` Arend Van Spriel
2023-12-19  8:57     ` Kalle Valo
2023-12-19 11:01     ` Hector Martin
2023-12-19 13:46       ` Arend van Spriel
2023-12-19 14:26         ` Julian Calaby
2023-12-21 20:39           ` Marcel Holtmann
2023-12-22  0:03             ` Neal Gompa
2023-12-22  6:16               ` Marcel Holtmann
2023-12-24  9:03               ` Arend van Spriel
     [not found]         ` <CAF4BwTXNtu30DAgBXo4auDaDK0iWc9Ch8f=EH+facQ-_F-oMUQ@mail.gmail.com>
2023-12-19 14:42           ` Kalle Valo
2023-12-20  0:06             ` Hector Martin
2023-12-20  1:44               ` Linus Torvalds
2023-12-20  4:16                 ` Hector Martin
2023-12-20 11:05                   ` Bagas Sanjaya
2023-12-20 10:20                 ` Kalle Valo
2023-12-20 15:55                   ` Kalle Valo
2023-12-20 16:42                     ` Eric Curtin
2023-12-20 18:14                   ` Hector Martin
2023-12-20 19:36                     ` Arend van Spriel
2023-12-21  0:49                       ` Hector Martin
2023-12-21  9:57                         ` Arend van Spriel
2023-12-22  5:10                           ` Hector Martin
2023-12-22 12:25                             ` Eric Curtin
2024-01-07  9:51                             ` Arend van Spriel
2023-12-20 11:32                 ` Eric Curtin
2023-12-20 10:16 ` Paul Fertser
2023-12-20 18:02   ` Hector Martin
2023-12-23 10:28     ` Testing bits/080-wifi on BCM4345/6 (was: Re: [PATCH] wifi: brcmfmac: cfg80211: Use WSEC to set SAE password) Paul Fertser
     [not found]       ` <CAF4BwTXJWYGT+8jp9dzxmSN7wbk7xZuy4tNSQDhxJ66UzhhgWw@mail.gmail.com>
2023-12-23 15:28         ` Paul Fertser [this message]
     [not found]           ` <CAF4BwTXm62PxBTM2bNX2MkTF4XUypNJAMpxMFaQ3LP5MHrfBZA@mail.gmail.com>
2023-12-24 19:29             ` Testing bits/080-wifi on BCM4345/6 Paul Fertser
     [not found]               ` <CAF4BwTWpVRZJxQnsqKgvNxvruAnN7C=zH23bSvvJOikg5YiMsg@mail.gmail.com>
2023-12-25  2:24                 ` Daniel Berlin
2024-01-27 14:40       ` SAE AP on BCM4345/6 (was: Re: Testing bits/080-wifi on BCM4345/6) Paul Fertser

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=ZYb8jf3a/CsI3/D2@home.paul.comp \
    --to=fercerpav@gmail.com \
    --cc=asahi@lists.linux.dev \
    --cc=dberlin@dberlin.org \
    --cc=marcan@marcan.st \
    /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