From: Kalle Valo <kvalo@codeaurora.org>
To: Devin Bayer <dev@doubly.so>
Cc: linux-wireless@vger.kernel.org, ath11k@lists.infradead.org
Subject: Re: ath11k with QCA6391
Date: Thu, 26 Nov 2020 12:04:45 +0200 [thread overview]
Message-ID: <87a6v4ph6q.fsf@codeaurora.org> (raw)
In-Reply-To: <48f37c07-ca63-7ba9-1518-a31681777b15@doubly.so> (Devin Bayer's message of "Wed, 25 Nov 2020 14:22:19 +0100")
Devin Bayer <dev@doubly.so> writes:
> On 03/11/2020 14.56, Kalle Valo wrote:
>> Devin Bayer <dev@doubly.so> writes:
>>
>>> On 02/11/2020 19.51, Kalle Valo wrote:
>>>>
>>>> To my knowledge, from ath11k point of view, QCA6391 should look the same
>>>> as QCA6390 but most likely the board file for QCA6391 is different.
>>>>
>>> [snip]
>>>
>>> They are different than those from your repo, but maybe I can use
>>> bdwlan01.e04 as the board file.
>>
>> Yes, that's what I would also suggest to test first: take the firmware
>> from ath11k-firmware.git and the board file from the vendor.
>
> I would like to report that with your latest qca6390-bringup branch my QCA6391
> card is working well with just the one MSI vector. I'm using the board file for
> 6390 from the linux-firmware repo.
>
> Thanks for the fixes :)
Great, thanks for the report. It's always helpful to know what is
working or not working on the field.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2020-11-26 10:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 15:14 ath11k with QCA6391 Devin Bayer
2020-11-02 18:51 ` Kalle Valo
2020-11-03 10:53 ` Devin Bayer
2020-11-03 13:56 ` Kalle Valo
2020-11-25 13:22 ` Devin Bayer
2020-11-26 10:04 ` 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=87a6v4ph6q.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=dev@doubly.so \
--cc=linux-wireless@vger.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;
as well as URLs for NNTP newsgroup(s).