From: Rui Salvaterra <rsalvaterra@gmail.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: "Michael Büsch" <m@bues.ch>,
"Larry Finger" <Larry.Finger@lwfinger.net>,
linux-wireless@vger.kernel.org, b43-dev@lists.infradead.org
Subject: Re: [BUG?] b43: can't connect to WPA3 network (nohwcrypt=1)
Date: Fri, 22 May 2020 14:46:26 +0100 [thread overview]
Message-ID: <CALjTZvYiFfqN3UMSM89Pg1rB9fJga+L1hVkBriEDeaej7oXcPw@mail.gmail.com> (raw)
In-Reply-To: <87a720gpfb.fsf@tynnyri.adurom.net>
Hi, Kalle,
On Fri, 22 May 2020 at 12:49, Kalle Valo <kvalo@codeaurora.org> wrote:
>
> And did the "bad" performance even have any real visible changes to the
> user? IMHO this "bad" performance is small price to pay from getting
> WPA3 supported out-of-box, especially when the data throughput is
> unaffected.
I agree, I also believe the additional security provided by WPA3 is
more important. The CPU overhead impact exists and is measurable but,
to be honest, I didn't notice any worse performance while browsing the
web, for example (which is already slow enough on a G4 CPU, as you can
imagine).
Thanks,
Rui
next prev parent reply other threads:[~2020-05-22 13:46 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 14:18 [BUG?] b43: can't connect to WPA3 network (nohwcrypt=1) Rui Salvaterra
2020-05-19 20:30 ` Larry Finger
2020-05-19 20:36 ` Rui Salvaterra
2020-05-19 23:13 ` Rui Salvaterra
2020-05-20 0:16 ` Larry Finger
2020-05-20 8:24 ` Rui Salvaterra
2020-05-20 10:55 ` Rui Salvaterra
2020-05-20 20:08 ` Larry Finger
2020-05-20 20:28 ` Rui Salvaterra
2020-05-20 20:56 ` Larry Finger
2020-05-21 8:35 ` Rui Salvaterra
2020-05-21 9:07 ` Rui Salvaterra
2020-05-21 10:46 ` Michael Büsch
2020-05-21 11:30 ` Rui Salvaterra
2020-05-21 11:40 ` Michael Büsch
2020-05-21 14:10 ` Larry Finger
2020-05-21 14:52 ` Rui Salvaterra
2020-05-21 16:17 ` Rui Salvaterra
2020-05-21 18:59 ` Larry Finger
2020-05-21 19:19 ` Rui Salvaterra
2020-05-21 20:23 ` Rui Salvaterra
2020-05-21 21:47 ` Larry Finger
2020-05-22 10:19 ` Michael Büsch
2020-05-22 11:49 ` Kalle Valo
2020-05-22 13:46 ` Rui Salvaterra [this message]
2020-05-22 18:02 ` Larry Finger
2020-05-22 20:04 ` Rui Salvaterra
2020-05-22 20:40 ` Rui Salvaterra
2020-05-22 21:06 ` Larry Finger
2020-05-23 0:35 ` Rui Salvaterra
2020-05-23 21:17 ` Rafał Miłecki
2020-05-25 6:56 ` Kalle Valo
2020-05-22 17:15 ` Larry Finger
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=CALjTZvYiFfqN3UMSM89Pg1rB9fJga+L1hVkBriEDeaej7oXcPw@mail.gmail.com \
--to=rsalvaterra@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=b43-dev@lists.infradead.org \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=m@bues.ch \
/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).