From: Kalle Valo <kvalo@kernel.org>
To: Sven Eckelmann <sven@narfation.org>
Cc: 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: Mon, 26 Feb 2024 17:53:54 +0200 [thread overview]
Message-ID: <87ttlvjk6l.fsf@kernel.org> (raw)
In-Reply-To: <2668032.usQuhbGJ8B@ripper> (Sven Eckelmann's message of "Mon, 26 Feb 2024 16:38:02 +0100")
+ ath11k, jeff
Sven Eckelmann <sven@narfation.org> writes:
> On Monday, 26 February 2024 15:50:44 CET Felix Fietkau wrote:
> [...]
>>> The Qualcomm bulletin[1] says "Patches are being actively
>> > shared with OEMs".
>> >
>> > Were these bugfixes made available for OpenWRT? Is there an established
>> > procedure for such cases, where closed-source firmware gets bugfixes?
> [...]
>> > [1]
>> > https://docs.qualcomm.com/product/publicresources/securitybulletin/
> december-2023-bulletin.html
>>
>> The fixes were not shared with OpenWrt. Qualcomm does not care about
>> OpenWrt support for their platforms.
>
> I've asked (using their qualcomm-cdmatech-support portal) for an official
> release of their WiFi firmware with all gathered bugfixes via
> linux-firmware.git. I got statements that the ath10k firmware is no longer
> supported + ath11k firmware is not developed further. But for some of them it
> is possible to request a release of the firmwares via Kalle's repositories.
> But also that Kalle's repositories are now replaced. Which seems to be
> confirmed by Kalle's statement [1] regarding the firmware-N.bin files on
> ath12k@lists.infradead.org .
>
> The new positions for firmware files were not revealed but I found a couple of
> places [2,3,4,5] in my search.
Yeah, the ath1?k-firmware.git repos are being moved to
git.codelinaro.org and we will send an announcement once everything is
ready.
> And to the request to get the latest versions released via linux-firmware.git
> (or maybe even only in Kalle's repositories), I got (some weeks ago) the
> answer "Let me check with our team.".
>
> It is rather hard to make statements about Qualcomm - simply because it is
> not just a single person and I have no idea about the internal structures. But
> it doesn't seem to be the highest priority (for the "internal team"?) to make
> fixes available for everyone. I still hope that it is just delayed due to some
> unfortunate circumstances. But this is just the current state.
Thanks for letting me know, I was not aware any of this. Me and Jeff
will investigate and get back to you.
For others, here's a link to the thread in openwrt-devel:
https://lists.openwrt.org/pipermail/openwrt-devel/2024-February/042341.html
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next parent reply other threads:[~2024-02-26 15:54 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 ` Kalle Valo [this message]
2024-04-29 13:14 ` Question to recent Qualcomm CVEs Kalle Valo
2024-04-29 13:36 ` Sven Eckelmann
2024-04-29 14:50 ` Robert Marko
2024-04-30 8:47 ` Kalle Valo
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=87ttlvjk6l.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=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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).