public inbox for ath12k@lists.infradead.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: ath11k@lists.infradead.org
Cc: Jeff Johnson <quic_jjohnson@quicinc.com>,
	ath11k@lists.infradead.org, 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: Tue, 10 Sep 2024 13:39:36 +0200	[thread overview]
Message-ID: <2248097.72vocr9iq0@ripper> (raw)
In-Reply-To: <87h6ang8v3.fsf@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 1155 bytes --]

On Tuesday, 10 September 2024 11:23:44 CEST Kalle Valo wrote:
> As there are so many different branches I have lost track, do you have a
> list of missing firmware updates? We could try to push for updates on
> our own end as well.

Afaik, ath10k is missing various security updates - but I don't know the 
firmware version which has these security updates.

ath11k is missing the 2.9.0.1 release - which seems to be still required to 
get various APs working correctly (without a crash). Maybe Robert Marko has 
the newest firmware version (not the file - the version) somewhere.

Afaik, there are even newer ath11k versions - for example for IPQ9574 (which 
is completely missing at the moment in the repositories).

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)
* ath12k/QCN9274

Kind regards,
	Sven

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2024-09-10 11:39 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 [this message]
2024-09-10 11:46         ` Robert Marko
2024-09-11 19:18         ` Jeff Johnson
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=2248097.72vocr9iq0@ripper \
    --to=sven@narfation.org \
    --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=quic_jjohnson@quicinc.com \
    --cc=robert.marko@sartura.hr \
    /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