From: Jeff Johnson <quic_jjohnson@quicinc.com>
To: Sven Eckelmann <sven@narfation.org>, <ath11k@lists.infradead.org>
Cc: ath10k <ath10k@lists.infradead.org>,
ath12k <ath12k@lists.infradead.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
Robert Marko <robert.marko@sartura.hr>,
Kalle Valo <kvalo@kernel.org>
Subject: Re: New staging repos for ath1*k firmware
Date: Wed, 11 Sep 2024 12:18:41 -0700 [thread overview]
Message-ID: <4dd46a07-4896-433f-8e03-2cea28c255c2@quicinc.com> (raw)
In-Reply-To: <2248097.72vocr9iq0@ripper>
On 9/10/2024 4:39 AM, Sven Eckelmann wrote:
...
> For the completely missing ones, I've submitted following list to QCA:
>
> * ath11k/IPQ5018_QCN6122 (that might be rather complicated due to the way how
> QCA designed this)
> * ath11k/IPQ5018_QCN6122_QCN6122 (that might be rather complicated due to the
> way how QCA designed this)
> * ath11k/IPQ9574
> * ath12k/IPQ5322
> * ath12k/IPQ5322_QCN6432_QCN6432 (sounds a little bit like the QCN6122
> situation)
I'm looking into the above. For the ath12k ones I suspect we are actually
waiting for the platform support to land in the upstream kernel, which has
some dependencies. See the current IPQ5322 RFC:
https://lore.kernel.org/all/20240814094323.3927603-1-quic_rajkbhag@quicinc.com/
> * ath12k/QCN9274
Does this help:
https://git.codelinaro.org/clo/ath-firmware/ath12k-firmware/-/commit/5d154d1a7f1059bf96b1127573e5b87f68538df8
/jeff
next prev parent reply other threads:[~2024-09-11 19:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 19:23 New staging repos for ath1*k firmware Jeff Johnson
2024-03-07 8:39 ` Robert Marko
2024-03-07 16:49 ` Kalle Valo
2024-03-09 17:58 ` Sebastian Gottschall
2024-03-13 19:32 ` Jeff Johnson
2024-03-14 7:54 ` Robert Marko
2024-03-14 22:27 ` Felix Kaechele
2024-09-10 9:00 ` Sven Eckelmann
2024-09-10 9:23 ` Kalle Valo
2024-09-10 11:39 ` Sven Eckelmann
2024-09-10 11:46 ` Robert Marko
2024-09-11 19:18 ` Jeff Johnson [this message]
2024-05-17 5:32 ` Kalle Valo
2024-06-03 20:11 ` Kalle Valo
2024-06-03 20:21 ` pgupta
2024-06-03 20:47 ` Jeff Johnson
2025-11-21 13:28 ` Paweł Owoc
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=4dd46a07-4896-433f-8e03-2cea28c255c2@quicinc.com \
--to=quic_jjohnson@quicinc.com \
--cc=ath10k@lists.infradead.org \
--cc=ath11k@lists.infradead.org \
--cc=ath12k@lists.infradead.org \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=robert.marko@sartura.hr \
--cc=sven@narfation.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