From: Sven Eckelmann <sven@narfation.org>
To: "linux-firmware@kernel.org" <linux-firmware@kernel.org>,
ath11k@lists.infradead.org, Kalle Valo <kvalo@qca.qualcomm.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PULL] ath11k firmware 20211223
Date: Fri, 18 Feb 2022 16:00:47 +0100 [thread overview]
Message-ID: <4785910.v3KmxWAaZY@ripper> (raw)
In-Reply-To: <BYAPR02MB4567669033A210A78AC397E9927E9@BYAPR02MB4567.namprd02.prod.outlook.com>
[-- Attachment #1.1: Type: text/plain, Size: 395 bytes --]
On Thursday, 23 December 2021 15:03:04 CET Kalle Valo wrote:
> ath11k/QCN9074/hw1.0/Notice.txt | 802 ++++++++++++++++++++
> ath11k/QCN9074/hw1.0/amss.bin | Bin 0 -> 11897676 bytes
> ath11k/QCN9074/hw1.0/m3.bin | Bin 0 -> 340108 bytes
This pull adds the firmware for QCN9074 but not the board-2.bin. As result,
the initialization of the ath11k PHY will fail.
Kind regards,
Sven
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 102 bytes --]
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
WARNING: multiple messages have this Message-ID (diff)
From: Sven Eckelmann <sven@narfation.org>
To: "linux-firmware@kernel.org" <linux-firmware@kernel.org>,
ath11k@lists.infradead.org, Kalle Valo <kvalo@qca.qualcomm.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PULL] ath11k firmware 20211223
Date: Fri, 18 Feb 2022 16:00:47 +0100 [thread overview]
Message-ID: <4785910.v3KmxWAaZY@ripper> (raw)
In-Reply-To: <BYAPR02MB4567669033A210A78AC397E9927E9@BYAPR02MB4567.namprd02.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 395 bytes --]
On Thursday, 23 December 2021 15:03:04 CET Kalle Valo wrote:
> ath11k/QCN9074/hw1.0/Notice.txt | 802 ++++++++++++++++++++
> ath11k/QCN9074/hw1.0/amss.bin | Bin 0 -> 11897676 bytes
> ath11k/QCN9074/hw1.0/m3.bin | Bin 0 -> 340108 bytes
This pull adds the firmware for QCN9074 but not the board-2.bin. As result,
the initialization of the ath11k PHY will fail.
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-02-18 15:25 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-23 14:03 [PULL] ath11k firmware 20211223 Kalle Valo
2021-12-23 14:03 ` Kalle Valo
2021-12-23 17:24 ` Mark Herbert
2021-12-29 13:41 ` Josh Boyer
2021-12-29 13:41 ` Josh Boyer
2022-01-10 15:19 ` Kalle Valo
2022-01-10 15:19 ` Kalle Valo
2022-02-10 10:45 ` Kalle Valo
2022-02-10 10:45 ` Kalle Valo
2022-02-18 15:55 ` Josh Boyer
2022-02-18 15:55 ` Josh Boyer
2022-03-02 17:50 ` Jouni Malinen
2022-03-02 17:50 ` Jouni Malinen
2022-03-04 13:04 ` Josh Boyer
2022-03-04 13:04 ` Josh Boyer
2022-03-04 16:14 ` Jouni Malinen
2022-03-04 16:14 ` Jouni Malinen
2022-03-23 8:06 ` Takashi Iwai
2022-03-23 8:06 ` Takashi Iwai
2022-04-13 8:26 ` Kalle Valo
2022-04-13 8:26 ` Kalle Valo
2022-04-13 8:40 ` Takashi Iwai
2022-04-13 8:40 ` Takashi Iwai
2022-02-18 15:00 ` Sven Eckelmann [this message]
2022-02-18 15:00 ` Sven Eckelmann
2022-04-13 8:28 ` Kalle Valo
2022-04-13 8:28 ` Kalle Valo
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=4785910.v3KmxWAaZY@ripper \
--to=sven@narfation.org \
--cc=ath11k@lists.infradead.org \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-firmware@kernel.org \
--cc=linux-wireless@vger.kernel.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 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.