From: Jeff Johnson <quic_jjohnson@quicinc.com>
To: 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: Wed, 13 Mar 2024 12:32:22 -0700 [thread overview]
Message-ID: <e1c3ba7e-b358-42a3-a8db-f9c098132350@quicinc.com> (raw)
In-Reply-To: <3b57d932-0848-40f4-ab2d-a8d4afe11df1@dd-wrt.com>
On 3/9/2024 9:58 AM, Sebastian Gottschall wrote:
>
> Am 07.03.2024 um 17:49 schrieb Kalle Valo:
>> Robert Marko <robert.marko@sartura.hr> writes:
>>
>>> 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.
>> We are working on getting the AP chipset firmwares updated but
>> unfortunately no news yet.
> why isnt qca releasing the latest firmwares at all. i mean we all know
> that the qca networking tree contains way newer firmwares for all
> chipsets since a long time
Kalle & I are just the conduit, but I've relayed this thread to the folks
responsible for feeding us the firmware releases.
/jeff
next prev parent reply other threads:[~2024-03-13 19:32 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
2024-03-07 16:49 ` Kalle Valo
2024-03-09 17:58 ` Sebastian Gottschall
2024-03-13 19:32 ` Jeff Johnson [this message]
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=e1c3ba7e-b358-42a3-a8db-f9c098132350@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=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).