From: Kalle Valo <kvalo@kernel.org>
To: Sven Eckelmann <sven@narfation.org>
Cc: "linux-firmware\@kernel.org" <linux-firmware@kernel.org>,
ath11k@lists.infradead.org,
"linux-wireless\@vger.kernel.org"
<linux-wireless@vger.kernel.org>
Subject: Re: [PULL] ath11k firmware 20211223
Date: Wed, 13 Apr 2022 11:28:43 +0300 [thread overview]
Message-ID: <87czhlmlok.fsf@kernel.org> (raw)
In-Reply-To: <4785910.v3KmxWAaZY@ripper> (Sven Eckelmann's message of "Fri, 18 Feb 2022 16:00:47 +0100")
Sven Eckelmann <sven@narfation.org> writes:
> 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.
Good point, I missed that. My plan is to include both QCN9074 firmware
and board-2.bin in my next pull request.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
prev parent reply other threads:[~2022-04-13 8:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-23 14:03 [PULL] ath11k firmware 20211223 Kalle Valo
2021-12-29 13:41 ` Josh Boyer
2022-01-10 15:19 ` Kalle Valo
2022-02-10 10:45 ` Kalle Valo
2022-02-18 15:55 ` Josh Boyer
2022-03-02 17:50 ` Jouni Malinen
2022-03-04 13:04 ` Josh Boyer
2022-03-04 16:14 ` Jouni Malinen
2022-03-23 8:06 ` Takashi Iwai
2022-04-13 8:26 ` Kalle Valo
2022-04-13 8:40 ` Takashi Iwai
2022-02-18 15:00 ` Sven Eckelmann
2022-04-13 8:28 ` Kalle Valo [this message]
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=87czhlmlok.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=linux-firmware@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--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 NNTP newsgroup(s).