From: Kalle Valo <kvalo@codeaurora.org>
To: Pavel Procopiuc <pavel.procopiuc@gmail.com>
Cc: ath11k@lists.infradead.org
Subject: Re: PROBLEM: unable to get QCA6390 to work
Date: Mon, 02 Nov 2020 19:42:08 +0200 [thread overview]
Message-ID: <87lffjodu7.fsf@codeaurora.org> (raw)
In-Reply-To: <fa22cf0f-3bac-add6-8c71-6f6cad5206d8@gmail.com> (Pavel Procopiuc's message of "Mon, 2 Nov 2020 11:32:02 +0100")
Pavel Procopiuc <pavel.procopiuc@gmail.com> writes:
> Hi,
>
> I'm unable to get QCA6390 to work on kernel 5.10-rc2.
>
> I have a Dell XPS 17 laptop with the QCA6390 device and I'm trying to
> get it to work using 5.10-rc2 kernel. So far I'm getting firmware
> errors in the log. For the kernel setup and firmware files I was
> following the guide from
> https://www.spinics.net/lists/linux-wireless/msg203111.html.
>
> * The current firmware repo structure is a bit different so I'm using:
> QCA6390/hw2.0/board-2.bin -> /lib/firmware/ath11k/QCA6390/hw2.0/board.bin
> QCA6390/hw2.0/1.0.1/WLAN.HST.1.0.1-01740-QCAHSTSWPLZ_V2_TO_X86-1/amss.bin
> -> /lib/firmware/ath11k/QCA6390/hw2.0/amss.bin
> QCA6390/hw2.0/1.0.1/WLAN.HST.1.0.1-01740-QCAHSTSWPLZ_V2_TO_X86-1/m3.bin
> -> /lib/firmware/ath11k/QCA6390/hw2.0/m3.bin
Can you do 'md5sum /lib/firmware/ath11k/QCA6390/hw2.0/*' and send the
output? Currently ath11k does not check the firmware files in any way
and I want to make sure they are not corrupted.
I have:
a101dc90f8e876f39383b60c9da64ec4 amss.bin
d4c912a3501a3694a3f460d13de06d28 m3.bin
4c0781f659d2b7d6bef10a2e3d457728 board-2.bin
Ah, now I noticed that you renamed board-2.bin to board.bin. But you
need to keep the file as board-2.bin, board-2.bin and board.bin are not
compatible. I need to send new instructions with the new board-2.bin
file.
--
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:[~2020-11-02 17:42 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 10:32 PROBLEM: unable to get QCA6390 to work Pavel Procopiuc
2020-11-02 17:42 ` Kalle Valo [this message]
2020-11-02 18:21 ` Pavel Procopiuc
2020-11-02 21:14 ` Pavel Procopiuc
2020-11-03 6:56 ` Kalle Valo
2020-11-03 13:12 ` Pavel Procopiuc
2020-11-04 9:32 ` Pavel Procopiuc
2020-11-03 14:23 ` Kalle Valo
2020-11-03 21:01 ` Pavel Procopiuc
2020-11-04 9:12 ` Kalle Valo
2020-11-04 22:15 ` Pavel Procopiuc
2020-11-05 9:04 ` Regression: QCA6390 fails with "mm/page_alloc: place pages to tail in __free_pages_core()" Kalle Valo
2020-11-05 9:47 ` Pavel Procopiuc
2020-11-05 10:42 ` Vlastimil Babka
2020-11-05 10:45 ` Pavel Procopiuc
2020-11-05 11:13 ` David Hildenbrand
2020-11-05 12:55 ` Pavel Procopiuc
2020-11-05 20:23 ` David Hildenbrand
2020-11-06 17:32 ` Pavel Procopiuc
2020-11-06 20:41 ` David Hildenbrand
2020-11-11 19:23 ` Kalle Valo
2020-11-11 20:41 ` Pavel Procopiuc
2020-11-12 10:48 ` David Hildenbrand
2020-11-13 8:17 ` Pavel Procopiuc
2020-11-13 11:08 ` Carl Huang
2020-11-13 11:44 ` Carl Huang
2020-11-13 12:52 ` Pavel Procopiuc
2020-11-13 13:36 ` wi nk
2020-11-13 13:56 ` David Hildenbrand
2020-11-13 15:49 ` wi nk
2020-11-03 8:42 ` PROBLEM: unable to get QCA6390 to work Carl Huang
2020-11-03 14:12 ` Pavel Procopiuc
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=87lffjodu7.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=pavel.procopiuc@gmail.com \
/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