From: Kalle Valo <kvalo@kernel.org>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: Baochen Qiang <quic_bqiang@quicinc.com>,
James Prestwood <prestwoj@gmail.com>,
linux-wireless@vger.kernel.org, ath10k@lists.infradead.org,
LKML <linux-kernel@vger.kernel.org>,
Hans de Goede <hdegoede@redhat.com>,
Kai-Heng Feng <kai.heng.feng@canonical.com>,
Hui Wang <hui.wang@canonical.com>
Subject: Re: invalid vht params rate 1920 100kbps nss 2 mcs 9
Date: Wed, 26 Jun 2024 15:34:34 +0300 [thread overview]
Message-ID: <874j9fj31h.fsf@kernel.org> (raw)
In-Reply-To: <d19d520c-547b-46c1-b59e-748c2cccaf53@molgen.mpg.de> (Paul Menzel's message of "Wed, 26 Jun 2024 13:48:01 +0200")
Paul Menzel <pmenzel@molgen.mpg.de> writes:
>> All firmware releases are available here:
>> https://git.codelinaro.org/clo/ath-firmware/ath10k-firmware/-/tree/main/QCA6174/hw3.0/4.4.1?ref_type=heads
>> And more info here:
>> https://wireless.wiki.kernel.org/en/users/drivers/ath10k/firmware
>
> Thank you. It looks like the latest firmware version is 309, and
> Debian sid/unstable still ships version 288 in *firmware-atheros*
> 20230625-2 [1].
>
> Unfortunately, there does not seem to be a change-log for version 309
> (or any version for that matter). I am going to manually copy it
> anyway, but it’d be nice, if I knew what to expect. ;-)
Yeah, unfortunately there are no changelogs available for firmware
releases but I do understand the need for those. There has been
discussions to create them but no success yet.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2024-06-26 12:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-16 13:10 invalid vht params rate 1920 100kbps nss 2 mcs 9 Paul Menzel
2024-06-17 15:09 ` James Prestwood
2024-06-17 15:27 ` Kalle Valo
2024-06-17 15:40 ` James Prestwood
2024-06-18 10:33 ` Kalle Valo
2024-06-18 10:48 ` Baochen Qiang
2024-06-26 8:53 ` Baochen Qiang
2024-06-26 9:12 ` Paul Menzel
2024-06-26 10:16 ` Kalle Valo
2024-06-26 11:48 ` Paul Menzel
2024-06-26 12:34 ` Kalle Valo [this message]
2024-07-05 2:47 ` Baochen Qiang
2024-07-05 6:55 ` Paul Menzel
2024-07-05 10:51 ` Baochen Qiang
2024-07-05 11:52 ` Paul Menzel
2024-07-08 1:53 ` Baochen Qiang
2024-07-08 10:36 ` Kalle Valo
2024-07-08 10:33 ` Kalle Valo
2024-07-09 1:33 ` Baochen Qiang
2024-06-27 17:42 ` James Prestwood
2024-06-27 18:25 ` Kalle Valo
2024-06-28 1:25 ` Baochen Qiang
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=874j9fj31h.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath10k@lists.infradead.org \
--cc=hdegoede@redhat.com \
--cc=hui.wang@canonical.com \
--cc=kai.heng.feng@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
--cc=prestwoj@gmail.com \
--cc=quic_bqiang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.