From: Felix Kaechele <felix@kaechele.ca>
To: Jeff Johnson <quic_jjohnson@quicinc.com>,
Sebastian Gottschall <s.gottschall@dd-wrt.com>,
Kalle Valo <kvalo@kernel.org>,
Robert Marko <robert.marko@sartura.hr>
Cc: ath10k <ath10k@lists.infradead.org>,
ath11k <ath11k@lists.infradead.org>,
ath12k <ath12k@lists.infradead.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: New staging repos for ath1*k firmware
Date: Thu, 14 Mar 2024 18:27:25 -0400 [thread overview]
Message-ID: <96597f1d-5072-4915-be5a-e685dc85614a@kaechele.ca> (raw)
In-Reply-To: <e1c3ba7e-b358-42a3-a8db-f9c098132350@quicinc.com>
Hi Jeff,
On 2024-03-13 15:32, Jeff Johnson wrote:
> Kalle & I are just the conduit, but I've relayed this thread to the folks
> responsible for feeding us the firmware releases.
Thank you for providing that service to the community. It's much
appreciated.
Is there a chance you could ask the team for the most recent firmware
for QCA9379 hw1.0 SDIO (Naples)? Branch name would be WLAN.NPL.
There are currently no public releases of this firmware outside of
what's included in the vendor blobs from some Android devices.
I'm still doing some testing on the patch I sent to support this card on
February 28 to this list and I'd like to see if some of the issues I'm
seeing might be a firmware issue.
Thanks!
Regards,
Felix
next prev parent reply other threads:[~2024-03-14 22:27 UTC|newest]
Thread overview: 8+ 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 [this message]
2024-05-17 5:32 ` 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=96597f1d-5072-4915-be5a-e685dc85614a@kaechele.ca \
--to=felix@kaechele.ca \
--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 \
--cc=s.gottschall@dd-wrt.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).