From: Robert Marko <robert.marko@sartura.hr>
To: Jeff Johnson <quic_jjohnson@quicinc.com>
Cc: ath10k <ath10k@lists.infradead.org>,
ath11k <ath11k@lists.infradead.org>,
ath12k <ath12k@lists.infradead.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
Kalle Valo <quic_kvalo@quicinc.com>
Subject: Re: New staging repos for ath1*k firmware
Date: Thu, 7 Mar 2024 09:39:26 +0100 [thread overview]
Message-ID: <CA+HBbNFQ+25u_PK2j3vYtiCZwv+shVAVeAHKqQCwhyCopORt4Q@mail.gmail.com> (raw)
In-Reply-To: <bac97f31-4a70-4c4c-8179-4ede0b32f869@quicinc.com>
On Wed, Mar 6, 2024 at 8:23 PM Jeff Johnson <quic_jjohnson@quicinc.com> wrote:
>
> Historically, prior to being incorporated into the linux-firmware
> project, firmware for kernel.org ath1*k drivers has been first published
> to Kalle's GitHub:
> https://github.com/kvalo/ath10k-firmware
> https://github.com/kvalo/ath11k-firmware
> (ath12k firmware was pushed to the ath11k-firmware repo on a temporary
> basis in anticipation of this move)
>
> But in order to have repos with multiple maintainers, as well as to have
> a hosting platform with more control, we have moved to CodeLinaro:
> https://git.codelinaro.org/clo/ath-firmware/ath10k-firmware
> https://git.codelinaro.org/clo/ath-firmware/ath11k-firmware
> https://git.codelinaro.org/clo/ath-firmware/ath12k-firmware
>
> Note that most people should not care about this -- normally you should
> use the firmware that is in the official linux-firmware repo:
> https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/
>
> You should only need to access the staging repos if you need a previous
> version to work around an issue, or if you are testing new firmware that
> is supposed to fix a problem that you've reported.
>
> Please let Kalle & I know if you have any issues with these new repos!
Can I please ask for IPQ6018 firmware to be updated to 2.9.0.1 as well?
We have added IPQ6018 support to OpenWrt but we are forced to use the old 2.4
firmware since anything newer is crashing on IPQ6018, we had the same issue on
IPQ8074 but it was fixed with 2.9.0.1 firmware.
Even for IPQ8074, there is newer 2.9.0.1 firmware that is only
available as part of
QSDK and the community would benefit from being able to use it.
Ideally, ath11k-firmware would at least contain the same blobs as the QUIC repo:
https://github.com/quic/upstream-wifi-fw.git
Regards,
Robert
>
> /jeff
>
--
Robert Marko
Staff Embedded Linux Engineer
Sartura Ltd.
Lendavska ulica 16a
10000 Zagreb, Croatia
Email: robert.marko@sartura.hr
Web: www.sartura.hr
next prev parent reply other threads:[~2024-03-07 8:39 UTC|newest]
Thread overview: 11+ 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 [this message]
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-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
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+HBbNFQ+25u_PK2j3vYtiCZwv+shVAVeAHKqQCwhyCopORt4Q@mail.gmail.com \
--to=robert.marko@sartura.hr \
--cc=ath10k@lists.infradead.org \
--cc=ath11k@lists.infradead.org \
--cc=ath12k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_jjohnson@quicinc.com \
--cc=quic_kvalo@quicinc.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).