From: Eric Park <me@ericswpark.com>
To: Kalle Valo <kvalo@kernel.org>
Cc: ath10k@lists.infradead.org
Subject: Re: QCA6174 showing terrible performance when connecting via WPA3-SAE
Date: Wed, 15 May 2024 07:23:48 +0900 [thread overview]
Message-ID: <c707de9b-2b55-4720-a9f8-1654946c6616@ericswpark.com> (raw)
In-Reply-To: <87pltoifbq.fsf@kernel.org>
On 5/15/2024 12:27 AM, Kalle Valo wrote:
> But James is reporting[1] that 802.11w is working for him. So it doesn't
> seem to be completely broken even if you are having problems and
> removing the 802.11w support from the driver doesn't sound right.
>
> [1] https://lore.kernel.org/all/ce0e2043-5085-4dd6-86bd-89dca6f566be@gmail.com/
I actually didn't see that email -- I'm not very familiar with how
mailing lists work but I guess I have to be subscribed to receive
updates, even for mail chains that I've started. So thank you for
linking me his email.
I'm unsure what to test next, if it can be triaged at all. It's an
outdated card in a really old laptop and I can always work around it
with a USB WiFi adapter. If anyone has any suggestions I'm all ears but
otherwise I think this would be a good place to stop.
- Eric
next prev parent reply other threads:[~2024-05-14 22:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-09 15:08 QCA6174 showing terrible performance when connecting via WPA3-SAE Eric Park
2024-03-11 10:21 ` Kalle Valo
2024-03-21 4:05 ` Eric Park
2024-04-25 9:51 ` Kalle Valo
2024-04-28 3:04 ` Eric Park
2024-04-29 12:18 ` Kalle Valo
2024-04-29 13:26 ` Eric Park
2024-04-29 16:32 ` Kalle Valo
2024-04-29 17:53 ` Eric Park
2024-05-03 21:52 ` Eric Park
2024-05-06 9:04 ` Kalle Valo
2024-05-07 1:37 ` Eric Park
2024-05-14 15:27 ` Kalle Valo
2024-05-14 22:23 ` Eric Park [this message]
2024-05-15 8:04 ` Kalle Valo
2024-05-17 8:43 ` Eric Park
2024-05-17 9:41 ` Kalle Valo
2024-04-29 18:23 ` 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=c707de9b-2b55-4720-a9f8-1654946c6616@ericswpark.com \
--to=me@ericswpark.com \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@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 read-only IMAP folder(s) and NNTP newsgroup(s).