From: Kalle Valo <kvalo@kernel.org>
To: Robert Marko <robimarko@gmail.com>
Cc: Sven Eckelmann <sven@narfation.org>,
Tanjeff Moos <Tanjeff.Moos@westermo.com>,
openwrt-devel@lists.openwrt.org, Felix Fietkau <nbd@nbd.name>,
ath11k@lists.infradead.org,
Jeff Johnson <quic_jjohnson@quicinc.com>
Subject: Re: Question to recent Qualcomm CVEs
Date: Tue, 30 Apr 2024 11:47:57 +0300 [thread overview]
Message-ID: <87plu7p77m.fsf@kernel.org> (raw)
In-Reply-To: <CAOX2RU4+j0GG+RxKDOF2qFWFBOZEo1+nLZt8FwNqJ30Qo1jjLg@mail.gmail.com> (Robert Marko's message of "Mon, 29 Apr 2024 16:50:07 +0200")
Robert Marko <robimarko@gmail.com> writes:
> On Mon, 29 Apr 2024 at 15:37, Sven Eckelmann <sven@narfation.org> wrote:
>>
>> On Monday, 29 April 2024 15:14:18 CEST Kalle Valo wrote:
>> > It's quite strange that they updated 2.5.0.1 branch first but my
>> > understanding that there should be updates for the newer 2.7.0.1 branch
>> > as well (2.7.0.1 branch is also in linux-firmware).
>>
>> Yes, I also told them in the support ticket that this is from an older branch
>> than what is currently shipped in linux-firmware.git. But they told me
>> that they are working on newer versions (whatever that means) - but they
>> wanted to handle first the update to ATH.11.4 (2.5.0.x) and then
>> step-by-step release it for newer firmware branches. It seem like that would be
>> up to 2.9.0.x - no idea why there is no (public) 2.10.x/2.11.x for the AP
>> SoCs.
>
> I would like to point out that IPQ6018 doesn't even have anything
> newer than 2.5.0.1 available publicly.
But I do see WLAN.HK.2.7.0.1-01744-QCAHKSWPL_SILICONZ-1 for IPQ6018:
https://git.codelinaro.org/clo/ath-firmware/ath11k-firmware/-/tree/main/IPQ6018/hw1.0/2.7.0.1/WLAN.HK.2.7.0.1-01744-QCAHKSWPL_SILICONZ-1?ref_type=heads
And that release seems to be also in linux-firmware:
File: ath11k/IPQ6018/hw1.0/q6_fw.mdt
Version: WLAN.HK.2.7.0.1-01744-QCAHKSWPL_SILICONZ-1
Am I missing something? Or did you mean IPQ5018 which only has a release
from 2.6.0.1 branch?
https://git.codelinaro.org/clo/ath-firmware/ath11k-firmware/-/tree/main/IPQ5018/hw1.0?ref_type=heads
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2024-04-30 8:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <48174971-4b30-4046-9710-2acb16990e07@westermo.com>
[not found] ` <5e5c35eb-336b-4e92-b506-506e9fbeef7d@nbd.name>
[not found] ` <2668032.usQuhbGJ8B@ripper>
2024-02-26 15:53 ` Question to recent Qualcomm CVEs Kalle Valo
2024-04-29 13:14 ` Kalle Valo
2024-04-29 13:36 ` Sven Eckelmann
2024-04-29 14:50 ` Robert Marko
2024-04-30 8:47 ` Kalle Valo [this message]
2024-04-30 8:56 ` Robert Marko
2024-04-30 13:02 ` Kalle Valo
2024-04-30 13:05 ` Robert Marko
2024-04-30 13:11 ` Christian Marangi (Ansuel)
2024-05-02 7:25 ` Sven Eckelmann
2024-05-03 7:42 ` Sven Eckelmann
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=87plu7p77m.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=Tanjeff.Moos@westermo.com \
--cc=ath11k@lists.infradead.org \
--cc=nbd@nbd.name \
--cc=openwrt-devel@lists.openwrt.org \
--cc=quic_jjohnson@quicinc.com \
--cc=robimarko@gmail.com \
--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