From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Kalle Valo <kvalo@kernel.org>
Cc: "ath11k@lists.infradead.org" <ath11k@lists.infradead.org>
Subject: Re: WCN6855 issues with latest linux-firmware
Date: Fri, 3 Jun 2022 11:40:20 +0300 [thread overview]
Message-ID: <f77c78c4-2dee-3798-4a8a-c42abc0e1c6f@linaro.org> (raw)
In-Reply-To: <87zgium9dw.fsf@kernel.org>
Hi Kalle,
On 03/06/2022 11:36, Kalle Valo wrote:
> Dmitry Baryshkov <dmitry.baryshkov@linaro.org> writes:
>
>> I have tested the latest firmware from linux-firmware and it still
>> fails to send the bdf file request:
>>
>> [ 3.740702] ath11k_pci 0000:01:00.0: chip_id 0x2 chip_family 0xb
>> board_id 0xa7 soc_id 0x400c0210
>> [ 3.752952] ath11k_pci 0000:01:00.0: fw_version 0x11090c35
>> fw_build_timestamp 2022-04-18 20:23 fw_build_id
>> QC_IMAGE_VERSION_STRING=WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.9
>> [ 3.760674] ath11k_pci 0000:01:00.0: failed to fetch board data for
>> bus=pci,vendor=17cb,device=1103,subsystem-vendor=17cb,subsystem-device=0108,qmi-chip-id=2,qmi-board-id=167
>> from ath11k/WCN6855/hw2.1/board-2.bin
>> [....]
>> [ 13.843957] ath11k_pci 0000:01:00.0: failed to wait board file
>> download request: -110
>
> Yeah, I have a bunch of missing board files but I haven't been able to
> start searching for them yet. This will take time, sorry.
I might be mistaken, but for me it looks like the problem is not in the
missing board file. I have added local board.bin.
The problem with the WLAN.HSP.1.1 firmware is that it does not request
the board data file on these boards (as pointed by the last line in the
log: 'failed to wait board file download request'). The WLAN.HSP.2.0
firmware loads the board file correctly. The old, unsupported
WLAN.HSP.1.1 firmware (from ChromeOS repo) also loads the bdf correctly.
--
With best wishes
Dmitry
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
next prev parent reply other threads:[~2022-06-03 8:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-12 14:31 WCN6855 issues with latest linux-firmware Dmitry Baryshkov
2022-05-12 18:23 ` Kalle Valo
2022-05-12 19:48 ` Dmitry Baryshkov
2022-05-16 13:01 ` Kalle Valo
2022-05-16 16:05 ` Dmitry Baryshkov
2022-05-16 16:15 ` Kalle Valo
2022-05-16 16:28 ` Dmitry Baryshkov
2022-05-12 21:08 ` Dmitry Baryshkov
2022-05-14 13:44 ` Dmitry Baryshkov
2022-06-01 12:40 ` Dmitry Baryshkov
2022-06-03 8:36 ` Kalle Valo
2022-06-03 8:40 ` Dmitry Baryshkov [this message]
2022-06-03 9:06 ` Kalle Valo
2022-06-03 9:20 ` Dmitry Baryshkov
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=f77c78c4-2dee-3798-4a8a-c42abc0e1c6f@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=ath11k@lists.infradead.org \
--cc=kvalo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox