From: Kalle Valo <kvalo@kernel.org>
To: Brett Mastbergen <brett.mastbergen@protectli.com>
Cc: Wonsup Yoon <pusnow@kaist.ac.kr>, ath10k@lists.infradead.org
Subject: Re: Questions about QCA6174 firmwares
Date: Wed, 05 Apr 2023 16:37:01 +0300 [thread overview]
Message-ID: <878rf6a1s2.fsf@kernel.org> (raw)
In-Reply-To: <20220815195952.GA7798@lycia.zebraskunk.int> (Brett Mastbergen's message of "Mon, 15 Aug 2022 15:59:52 -0400")
(sorry for the delay, this got piled up with other email and I missed it)
Brett Mastbergen <brett.mastbergen@protectli.com> writes:
> On Wed, Aug 10, 2022 at 10:56:38AM +0900, Wonsup Yoon wrote:
>> Hi,
>>
>> If you don't mind, I'd like ask a few questions regarding QCA6174 firmwares.
>>
>> 1. I've notice that QCA6174 hw3.0 4.4.1 firmwares have 4 versions
>> (none, c1, c2, c3). Are there any differences? Which one is newest
>> or correct?
IIRC c1, c2 and c3 have different features but I can't recall what they
are. The recommendation is to use the mainline branch 4.4.1 from [1] and
that's the branch which I update to linux-firmware as well.
>> 2. My QCA6174 seems to have a compatibility issue with a recent
>> firmware. I've tested theses firmware versions, but only the oldest
>> one works.
>>
>
> I have observed the same firmware crashes with those versions with my
> QCA6174 module (JWW6051). Would love to know if
> RM.4.4.1.c2-00057-QCARMSWP-1 is the correct version to use, or if
> there is another newer version that I should be using.
It looks like these crashes only certain devices, can you provide more
info on what devices exactly they happen? The more information the
better.
And apparently older firmware works but newer crashes? It would help to
solve the problem if finding out from [1] what's the latest release
which still works and the earliest release which is broken.
Kalle
[1] https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0/4.4.1
--
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:[~2023-04-05 13:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-10 1:56 Questions about QCA6174 firmwares Wonsup Yoon
2022-08-15 19:59 ` Brett Mastbergen
2022-08-16 5:41 ` Wonsup Yoon
2022-08-16 18:55 ` Brett Mastbergen
2023-04-05 13:37 ` Kalle Valo [this message]
2023-04-05 13:45 ` 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=878rf6a1s2.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath10k@lists.infradead.org \
--cc=brett.mastbergen@protectli.com \
--cc=pusnow@kaist.ac.kr \
/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.