ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Eric Park <me@ericswpark.com>
Cc: ath10k@lists.infradead.org
Subject: Re: QCA6174 showing terrible performance when connecting via WPA3-SAE
Date: Fri, 17 May 2024 12:41:32 +0300	[thread overview]
Message-ID: <87v83cg4hf.fsf@kernel.org> (raw)
In-Reply-To: <1489399e-4f49-4d37-8494-e9d575d656a4@ericswpark.com> (Eric Park's message of "Fri, 17 May 2024 17:43:47 +0900")

Eric Park <me@ericswpark.com> writes:

> On 5/15/24 5:04 PM, Kalle Valo wrote:
>
>> Eric Park <me@ericswpark.com> writes:
>>> 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.
>> One thing to try is to make sure your setup matches what James is using,
>> especially the firmware version.
>
> Interesting, this is what I get from `dmesg`:
>
> qca6174 hw2.1 target 0x05010000 chip_id 0x003405ff sub 144d:4125
> firmware ver SW_RM.1.1.1-00157-QCARMSWPZ-1 api 5 features ignore-otp,
> no-4addr-pad crc32 10bf8e08
>
> I'm guessing the firmware version 1.1.1 is the latest one for the hw
> 2.1 variant (going off of the firmware repository), but please correct
> me if I'm wrong!
>
> Looking at the repository that version was updated 8 years ago. Is
> there anything else I can try? I'm guessing newer firmware only
> works on the newer hardware revisions.

Aha! I had totally missed that you are using hw2.1. (James is using
hw3.2) Yeah, that hardware version has been problematic almost since the
beginning and there has been any firmware updates for a long time. I'm
not surprised at all that 802.11w is slow on hw2.1.

I think disabling 802.11w for QCA6174 hw2.1 is a good idea, patches
welcome.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches


  reply	other threads:[~2024-05-17  9:41 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
2024-05-15  8:04                           ` Kalle Valo
2024-05-17  8:43                             ` Eric Park
2024-05-17  9:41                               ` Kalle Valo [this message]
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=87v83cg4hf.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=ath10k@lists.infradead.org \
    --cc=me@ericswpark.com \
    /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