From: "Nicolò Sprea" <nsprea@gmail.com>
To: Kalle Valo <kvalo@kernel.org>
Cc: ath10k@lists.infradead.org
Subject: Re: Firmware 4 vs Firmware 6 for QCA6174 hw3.0
Date: Wed, 8 Jun 2022 11:16:47 +0200 [thread overview]
Message-ID: <CA+BgFQXH7FsSO6ZuGNcddm+0iyP+NEW77Tr-dtaDvOQC3ri+qg@mail.gmail.com> (raw)
In-Reply-To: <87fskfr462.fsf@kernel.org>
# Using:
driver: ath10k_pci
version: 4.15.0-38-generic
firmware-version: WLAN.RM.4.4.1-00079-QCARMSWPZ-1
# Problem:
When wpa_supplicant re-associates, I get the following issue:
ath10k_pci 0000:02:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0
and all the interfaces (including loopback) "freeze" for a few seconds.
# Solutions:
1. using firmware version WLAN.RM.2.0-00180-QCARMSWPZ-1
2. backporting driver
# My question:
What are the missing features/known bugs of WLAN.RM.2.0-00180-QCARMSWPZ-1?
On Wed, Jun 8, 2022 at 9:43 AM Kalle Valo <kvalo@kernel.org> wrote:
>
> Nicolò Sprea <nsprea@gmail.com> writes:
>
> > Thanks for the answer.
> > Is there any feature that uses only api 6?
> > If I want to downgrade to api 4, is there anything that I should pay
> > attention to?
>
> The interface number itself does not change any functionality, what
> matters are the actual firmware release versions. And of course older
> firmware releases have more bugs and less features. It would be easier
> for people to help if you describe what's the actual problem you are
> trying to solve.
>
> --
> https://patchwork.kernel.org/project/linux-wireless/list/
>
> https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2022-06-08 9:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 6:12 Firmware 4 vs Firmware 6 for QCA6174 hw3.0 Nicolò Sprea
2022-06-08 6:35 ` Kalle Valo
2022-06-08 6:43 ` Nicolò Sprea
2022-06-08 7:43 ` Kalle Valo
2022-06-08 9:16 ` Nicolò Sprea [this message]
2022-06-08 10:17 ` Kalle Valo
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=CA+BgFQXH7FsSO6ZuGNcddm+0iyP+NEW77Tr-dtaDvOQC3ri+qg@mail.gmail.com \
--to=nsprea@gmail.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 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.