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: Mon, 02 Nov 2020 20:51:55 +0200 [thread overview]
Message-ID: <87wnz3twvo.fsf@codeaurora.org> (raw)
In-Reply-To: <c9fb5fa6-297e-a595-7670-c9105641bc83@doubly.so> (Devin Bayer's message of "Thu, 22 Oct 2020 17:14:54 +0200")
Devin Bayer <dev@doubly.so> writes:
> I have recently purchased some QCA6391 cards and I am going to try to
> get them working with Linux.
>
> I've seen the instructions for QCA6390 and I'm wondering if they will
> also apply to QCA6391, or if it's possible to get it working without
> major work.
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.
--
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
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@codeaurora.org>
To: Devin Bayer <dev@doubly.so>
Cc: ath11k@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: ath11k with QCA6391
Date: Mon, 02 Nov 2020 20:51:55 +0200 [thread overview]
Message-ID: <87wnz3twvo.fsf@codeaurora.org> (raw)
In-Reply-To: <c9fb5fa6-297e-a595-7670-c9105641bc83@doubly.so> (Devin Bayer's message of "Thu, 22 Oct 2020 17:14:54 +0200")
Devin Bayer <dev@doubly.so> writes:
> I have recently purchased some QCA6391 cards and I am going to try to
> get them working with Linux.
>
> I've seen the instructions for QCA6390 and I'm wondering if they will
> also apply to QCA6391, or if it's possible to get it working without
> major work.
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.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2020-11-02 18:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 15:14 ath11k with QCA6391 Devin Bayer
2020-10-22 15:14 ` Devin Bayer
2020-11-02 18:51 ` Kalle Valo [this message]
2020-11-02 18:51 ` Kalle Valo
2020-11-03 10:53 ` Devin Bayer
2020-11-03 10:53 ` Devin Bayer
2020-11-03 13:56 ` Kalle Valo
2020-11-03 13:56 ` Kalle Valo
2020-11-25 13:22 ` Devin Bayer
2020-11-25 13:22 ` Devin Bayer
2020-11-26 10:04 ` Kalle Valo
2020-11-26 10:04 ` 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=87wnz3twvo.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 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.