From: Kalle Valo <kvalo@kernel.org>
To: GreyXor <greyxor@protonmail.com>
Cc: "ath12k@lists.infradead.org" <ath12k@lists.infradead.org>
Subject: Re: Difference between WCN7850 and WCN7851 ?
Date: Fri, 19 Jan 2024 16:55:15 +0200 [thread overview]
Message-ID: <87zfx1e5kc.fsf@kernel.org> (raw)
In-Reply-To: <874jf9frn9.fsf@kernel.org> (Kalle Valo's message of "Fri, 19 Jan 2024 14:12:58 +0200")
Kalle Valo <kvalo@kernel.org> writes:
> GreyXor <greyxor@protonmail.com> writes:
>
>> Hi, I'm interested in acquiring a WiFi 7 card for my laptop, and I
>> came across the Qualcomm QCNCM865, which is Qualcomm's WiFi 7 card.
>> Upon checking Wi-Cat, I noticed that it features a WCN7851 chipset.
>> However, when examining the ath12k/linux source, I couldn't find any
>> mention of the WCN7851; only the WCN7850 was referenced. What
>> implications does this have? Can I still obtain a WCN7851, or would it
>> be advisable to opt for a card with a WCN7850 chipset, given its
>> greater number of updates and references in the kernel?
>
> I don't know what changes WCN7851 has compared to WCN7850 but in general
> these changes are transparently handled by the firmware and the host
> driver just sees it as WCN7850. But I hope someone who is familiar with
> WCN7851 can confirm this.
Another thing I want to point out: usually board files are a major
problem so before buying anything I recommend checking that there's a
board file available for ath12k.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2024-01-19 14:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 11:36 Difference between WCN7850 and WCN7851 ? GreyXor
2024-01-19 12:12 ` Kalle Valo
2024-01-19 14:55 ` 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=87zfx1e5kc.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath12k@lists.infradead.org \
--cc=greyxor@protonmail.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 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.