From: Kalle Valo <kvalo@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: ath11k@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: ath11k vs ar_qrtr?
Date: Wed, 30 Nov 2022 19:18:47 +0200 [thread overview]
Message-ID: <875yewnyx4.fsf@kernel.org> (raw)
In-Reply-To: <20221130132244.GB3055@lst.de> (Christoph Hellwig's message of "Wed, 30 Nov 2022 14:22:44 +0100")
Christoph Hellwig <hch@lst.de> writes:
> On Wed, Nov 30, 2022 at 03:12:32PM +0200, Kalle Valo wrote:
>> Heh, I'm learning something new here. But I wonder why nobody else has
>> seen this?
>
> Good question. How common is the ath11k hardware, especially on latptop
> where it is required for installation given that only installers tend
> to split up driver is non-standard ways.
I'm not sure about exact numbers, but not very common. I have seen
something like 4-5 different laptop models with either QCA6390 or
WCN6855 (both ath11k PCI devices). The PCI support was added to ath11k
in v5.10 (released Dec 2020) so maybe installers haven't caught up yet?
Just guessing though.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2022-11-30 17:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221130122807.GA31720@lst.de>
[not found] ` <87o7so4nr2.fsf@kernel.org>
[not found] ` <20221130125236.GA865@lst.de>
2022-11-30 13:12 ` ath11k vs ar_qrtr? Kalle Valo
2022-11-30 13:22 ` Christoph Hellwig
2022-11-30 17:18 ` Kalle Valo [this message]
2022-11-30 13:30 ` failed to insert STA entry for the AP (error -2) Christoph Hellwig
2022-12-02 18:46 ` Kalle Valo
2022-12-03 15:52 ` Christoph Hellwig
2022-12-07 12:49 ` Kalle Valo
2022-12-07 13:40 ` Christoph Hellwig
2022-12-07 14:24 ` Cyril Brulebois
2022-12-08 18:44 ` 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=875yewnyx4.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=hch@lst.de \
--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).