From: Kalle Valo <kvalo@kernel.org>
To: Hans de Goede <hans@hansg.org>
Cc: ath10k@lists.infradead.org
Subject: Re: ath10k-firmware: QCA6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 168c:3370 board file
Date: Fri, 21 Jan 2022 16:16:51 +0200 [thread overview]
Message-ID: <87ee519nsc.fsf@kernel.org> (raw)
In-Reply-To: <226790d7-75d8-bac3-9991-d73fa5b7df5b@hansg.org> (Hans de Goede's message of "Tue, 24 Aug 2021 18:44:05 +0200")
Hans de Goede <hans@hansg.org> writes:
> Here is a board-file for the QCA6174 PCI 168c:003e subsys: 168c:3370 wifi
> card found on Microsoft Surface Go devices.
>
> I'm submitting this per the docs in:
> https://wireless.wiki.kernel.org/en/users/drivers/ath10k/boardfiles
> I hope those are still up to date.
>
> Currently the kernel gives the following message when loading on this card:
> "failed to fetch board data for
> bus=pci,vendor=168c,device=003e,subsystem-vendor=168c,subsystem-device=3370
> from ath10k/QCA6174/hw3.0/board-2.bin"
>
> And then errors out with a bunch of -110 (-ETIMEOUT) errors.
>
> Replacing the fallback board.bin file with the attached .bin file fixes
> these errors and results in working wifi (I tested at both 2.4G and 5G).
>
> There are various internet forum posts which point to this board file:
> https://web.archive.org/web/20201111213909/http://www.killernetworking.com/support/K1535_Debian/board.bin
>
> But the killer 1535 wifi card uses completely different subsys-ids
> of 1a56:1535, so even though that happens to work I do not believe
> that is the correct file.
>
> So instead, inspired by this report:
> https://bugzilla.redhat.com/show_bug.cgi?id=1651779
>
> I started looking at the driverstore directory of the original windows
> install on the device I found "netathr10x.inf" there which has this line:
>
> eDesc.6320_3% = ATHR_DEV_OS63_988x_TX8.ndi,
> PCI\VEN_168C&DEV_003E&SUBSYS_3370168C&REV_32; WiFi Only SKU
>
> Note the "WiFi Only SKU" remark is there to differentiate this from
> the 168c:3371 subsys one which also has LTE (marked as "WiFi/LTE SKU")
>
> This led me to the "ATHR_DEV_OS63_988x_TX8.ndi" section of the .inf file:
>
> [ATHR_DEV_OS63_988x_TX8.ndi.NTamd64]
> ...
> CopyFiles = atheros.CopyFiles, atheros_FW_3X.CopyFiles, atheros_BD_TX8.CopyFiles
> ...
>
> And "atheros_BD_TX8.CopyFiles" is:
>
> [atheros_BD_TX8.CopyFiles]
> eeprom_ar6320_3p0_TX8_clpc.bin,,,2
>
> The "windows\system32\driverstore\netathr10x" dir has a ton of
> eeprom files (let me know if you want a copy of the whole dir)
> including the mentioned one. Where as "windows\system32\drivers"
> only has the one eeprom_ar6320_3p0_TX8_clpc.bin eeprom... file,
> further indicating that that is the one actually being used.
>
> So this is the file which I've tested with and which is attached to this email as:
> "bus=pci,vendor=168c,device=003e,subsystem-vendor=168c,subsystem-device=3370.bin"
>
> md5sum:
> bc52aa5640b27fa50f9d4d144f81e169
> bus=pci,vendor=168c,device=003e,subsystem-vendor=168c,subsystem-device=3370.bin
I assume this is the same version as you submitted directly to
linux-firmware[1], so I'm dropping this request.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=4d74f4dec175363fa24c95702dd86f477cef232c
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2022-01-21 14:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-24 16:44 ath10k-firmware: QCA6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 168c:3370 board file Hans de Goede
2022-01-21 14:16 ` Kalle Valo [this message]
2022-01-21 15:13 ` Hans de Goede
2022-01-24 9:05 ` 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=87ee519nsc.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath10k@lists.infradead.org \
--cc=hans@hansg.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