From: Kalle Valo <kvalo@kernel.org>
To: Sven Eckelmann <sven@narfation.org>
Cc: ath11k@lists.infradead.org
Subject: Re: ath11k: QCN9074: Incompatible board-2.bin for 6GHz
Date: Wed, 13 Apr 2022 10:06:27 +0300 [thread overview]
Message-ID: <87sfqhmpho.fsf@kernel.org> (raw)
In-Reply-To: <2947430.zJFXT1rtDI@sven-l14> (Sven Eckelmann's message of "Tue, 21 Dec 2021 23:58:42 +0100")
Sven Eckelmann <sven@narfation.org> writes:
> On Tuesday, 21 December 2021 15:52:03 CET Kalle Valo wrote:
>> I have told the firmware team numerious times that the board file should
>> be backwards compatible as it creates problems for upstream. And I do
>> try to keep everything in ath11k-firmware (and in linux-firmware)
>> backwards compatible, but if they are not please do let me know.
>
> Please check the first message to find such a problem. Ok, it was not about
> board files being really backward compatible - it actually is about the
> firmware not being backward compatible and not working with the board-2.bin/
> BDFs in the same repository.
>
> So if I get
> https://github.com/kvalo/ath11k-firmware/commit/ae4f4f64ed14097dc24a8d686fa60e932cba4868/QCN9074/hw1.0/testing/2.4.0.1.r1/WLAN.HK.2.4.0.1.r1-00019-QCAHKSWPL_SILICONZ-1/board-2.bin
> (extract board_id 162 as board.bin - because nobody seems to initialize the
> board_id in the OTP)
>
> and use it with
>
> https://github.com/kvalo/ath11k-firmware/tree/master/QCN9074/hw1.0/2.5.0.1/WLAN.HK.2.5.0.1-01100-QCAHKSWPL_SILICONZ-1
>
> then it causes the initialization error described in the first mail. And the
> firmware used here is the only non-testing firmware available for QCN9074. And
> the board-2.bin is the only available one from your repository for QCN9074.
Ah, I forgot to mention that everything under "testing" directory is
work-in-progress, and might break backwards compatibility. To keep
things simple I now removed all backwards incompatible files from my
ath11k-firmware. Also now there's a proper board-2.bin for QCN9074,
hopefully that works better. Do let me know if you have any issues.
--
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
next prev parent reply other threads:[~2022-04-13 7:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-26 10:52 ath11k: QCN9074: Incompatible board-2.bin for 6GHz Sven Eckelmann
2021-11-26 14:54 ` John Crispin
2021-11-26 15:55 ` Mark Herbert
2021-11-29 17:19 ` Sven Eckelmann
2021-12-21 14:52 ` Kalle Valo
2021-12-21 22:58 ` Sven Eckelmann
2022-04-13 7:06 ` Kalle Valo [this message]
2022-04-13 7:26 ` Sven Eckelmann
2022-04-13 8:01 ` 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=87sfqhmpho.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath11k@lists.infradead.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 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.