From: James Prestwood <jprestwood@locusrobotics.com>
To: "open list:MEDIATEK MT76 WIRELESS LAN DRIVER"
<linux-wireless@vger.kernel.org>,
ath11k@lists.infradead.org
Subject: ath11k multicast action frame RX
Date: Wed, 24 Jan 2024 05:06:26 -0800 [thread overview]
Message-ID: <dcdbd757-ad6e-4fe0-a0c1-fe328431b73b@locusrobotics.com> (raw)
Hi,
I recently added support to ath10k, for the QCA6174, to receive
multicast action frames in order to support DPP. I'm trying to do this
for the ath11k QCNFA765/WCN6855. I took the same approach as ath10k
which was actually quite simple but I'm unable to see any multicast
frames coming over even when I enable RX/DATA debugging.
What I've done so far is:
- Add FIF_MCAST_ACTION to the supported filters list
- Created/started a monitor vdev from within
ath11k_mac_op_configure_filter()
ath11k_mac_monitor_vdev_create(ar);
ath11k_mac_monitor_start(ar);
- Also tried adding
ath11k_mac_config_mon_status_default(ar, true);
I can successfully create/start the monitor vdev. I see now as I'm
writing this email that my specific hardware does not support monitor
mode outright... Is this a dead end or is there hope with purely driver
changes? or is it some filtering at the firmware level preventing this?
Thanks,
James
next reply other threads:[~2024-01-24 13:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 13:06 James Prestwood [this message]
2024-01-26 19:18 ` ath11k multicast action frame RX James Prestwood
2024-01-30 7:00 ` Baochen Qiang
2024-01-30 12:47 ` James Prestwood
2024-01-30 12:54 ` James Prestwood
2024-01-31 2:01 ` Baochen Qiang
2024-01-31 12:28 ` James Prestwood
2024-02-21 3:45 ` Baochen Qiang
2024-02-21 12:24 ` James Prestwood
2024-02-22 2:26 ` Baochen Qiang
2024-02-22 15:38 ` James Prestwood
2024-02-23 1:56 ` Baochen Qiang
2024-02-23 16:13 ` James Prestwood
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=dcdbd757-ad6e-4fe0-a0c1-fe328431b73b@locusrobotics.com \
--to=jprestwood@locusrobotics.com \
--cc=ath11k@lists.infradead.org \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).