From: Kalle Valo <kvalo@kernel.org>
To: Federico Pietro Briata <federico@briata.org>
Cc: Felix Fietkau <nbd@nbd.name>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
ath11k@lists.infradead.org
Subject: Re: help with Qualcomm QCA6696
Date: Thu, 23 Mar 2023 07:31:00 +0200 [thread overview]
Message-ID: <87h6ucdoff.fsf@kernel.org> (raw)
In-Reply-To: <CA+KKcbm9qy2yAjVZptTEQa7Z3UALcVbD2GbeHNrYufM6cfvZuw@mail.gmail.com> (Federico Pietro Briata's message of "Thu, 23 Mar 2023 01:39:43 +0100")
+ ath11k list
Federico Pietro Briata <federico@briata.org> writes:
> I would like to use the wifi chipset QCA6696 to create a mesh network,
> best in ibss or 802.11s mode. I got from quectel a wifi driver but it
> seems to support just AP and STA, but from my understanding I shall be
> able to test at least WiFi SON or EasyMesh. Do you know if the support
> for this chip it's avaiable with the community driver?
I don't know what hardware ids QCA6696 has but in theory ath11k supports
that family (QCA6390) of devices, though some changes might be needed.
But ath11k won't help you as it only support station and AP interface
modes with QCA6390 family.
BTW please don't send HTML emails, our lists drop those.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2023-03-23 5:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 9:05 [PATCH] Added Netgear AXE3000 (A8000) usb_device_id to mt7921u_device_table[] Reese Russell
2023-03-17 19:49 ` Nick Morrow
2023-03-18 7:06 ` Kalle Valo
2023-03-22 18:01 ` wifi: mt76: mt7921: add Netgear AXE3000 (A8000) support Kalle Valo
[not found] ` <CA+KKcbm9qy2yAjVZptTEQa7Z3UALcVbD2GbeHNrYufM6cfvZuw@mail.gmail.com>
2023-03-23 5:31 ` 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=87h6ucdoff.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=federico@briata.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@nbd.name \
/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).