From: "Lindner, Frank" <Frank.Lindner@ghmt.de>
To: "ath11k@lists.infradead.org" <ath11k@lists.infradead.org>
Subject: WCN6856 monitor mode
Date: Mon, 22 Apr 2024 10:25:44 +0000 [thread overview]
Message-ID: <FRYP281MB0160DB4CC65BD0BF23BE491AEB122@FRYP281MB0160.DEUP281.PROD.OUTLOOK.COM> (raw)
Hi developers,
is WCN6856 chip able to do monitor mode? Any idea how to get this working in full monitor mode?
And if not, which tri-band (2.4/5/6 GHz) chip is supported in monitor-mode?
System is Intel-Desktop with EMWICON WMX7203-F miniPCI-e module (which reports as WCN6856).
Ethtool reports:
driver: ath11k_pci
version: 6.9.0-rc1+
kernel is build from ath-next tree
iw phy phyX info reports:
Supported interface modes:
* managed
* AP
* P2P-client
* P2P-GO
* P2P-device
Modinfo ath11k_pci:
filename: /lib/modules/6.9.0-rc1+/kernel/drivers/net/wireless/ath/ath11k/ath11k_pci.ko
firmware: ath11k/WCN6855/hw2.1/*
firmware: ath11k/WCN6855/hw2.0/*
firmware: ath11k/QCN9074/hw1.0/*
firmware: ath11k/QCA6390/hw2.0/*
license: Dual BSD/GPL
description: Driver support for Qualcomm Technologies PCIe 802.11ax WLAN devices
srcversion: E0CFCB86B94B50F73C20A56
alias: pci:v000017CBd00001104sv*sd*bc*sc*i*
alias: pci:v000017CBd00001103sv*sd*bc*sc*i*
alias: pci:v000017CBd00001101sv*sd*bc*sc*i*
depends: ath11k,mhi
retpoline: Y
intree: Y
name: ath11k_pci
vermagic: 6.9.0-rc1+ SMP preempt mod_unload modversions
sig_id: PKCS#7
signer: Build time autogenerated kernel key
sig_key: 3B:9A:DE:F8:A6:42:7A:C0:6C:34:9F:EB:8D:46:E8:5C:5D:E5:4B:B5
sig_hashalgo: sha512
signature: AD:15:24:6A:50:6A:90:99:80:7A:06:8C:D5:7B:A3:4E:CC:91:94:DF:
0C:79:E0:94:2F:62:E2:B0:36:99:23:F7:E6:75:48:3D:BC:38:89:65:
3E:D0:12:0A:24:CB:90:20:6E:5F:69:F9:BC:E1:53:F6:5C:2C:C7:45:
20:3D:CA:B2:7B:39:D4:C8:72:6A:5C:17:42:56:63:4C:B3:E8:11:3C:
89:0C:83:1F:66:53:17:AD:E8:B6:57:B4:26:0F:46:BA:9B:31:ED:7B:
A6:DF:8D:DD:4B:6D:D4:14:FD:3A:33:EA:D6:54:AE:60:21:09:D1:61:
08:B1:36:3D:BA:3F:AF:7A:51:B9:AC:69:19:06:28:94:F8:C2:E3:6D:
DC:30:A9:BA:B9:E7:26:38:E1:0C:A3:34:22:DE:65:A1:E8:C4:99:30:
CF:E1:61:0D:76:79:1F:5E:06:C2:18:88:A3:EC:B5:67:0A:C7:D6:29:
0C:F5:02:6E:B3:A6:8F:8B:B0:F0:3A:F4:6F:D3:A9:96:ED:D9:BB:47:
5D:A0:43:77:97:F7:EC:A6:A5:9E:26:38:28:AF:D8:C8:20:62:2C:96:
E5:4E:CC:EB:42:5C:14:75:B7:E2:78:B4:3A:45:1B:C1:FC:BE:D9:E4:
77:E3:EF:04:43:79:39:BE:12:97:C1:14:49:ED:1B:BC:4C:AD:B0:F0:
5E:6A:8F:02:E1:68:B2:23:1D:C5:A5:89:C4:26:0A:09:D1:2C:74:E2:
F8:D7:0D:93:2A:E8:7B:FE:A7:DB:10:FD:74:83:0E:83:A4:B9:E8:9B:
EB:C5:90:75:0A:DE:7B:4A:B0:E9:A9:03:1C:1E:10:48:B2:21:99:48:
D5:61:B0:B5:79:50:45:B4:4D:E7:56:38:7D:09:DC:9A:0A:C3:70:1A:
0A:B6:20:25:92:BD:F0:57:AE:D7:0C:A0:F6:D4:20:C7:5D:D2:C6:67:
D0:74:AF:EC:4B:E0:14:9A:49:F9:9F:50:7A:A5:B0:9D:B2:DB:D7:12:
9F:30:86:F0:49:1B:17:C9:D8:E7:79:3A:2A:EB:0E:C7:22:CA:7F:39:
87:BB:55:7F:DF:7D:32:C7:F6:31:57:EF:08:0E:7F:1E:E2:54:5A:FF:
40:6E:AE:99:8B:83:49:C8:61:44:72:83:93:32:64:A1:54:58:15:E6:
71:65:4B:67:D4:EA:78:7E:13:86:37:F3:6F:63:25:2B:30:36:A3:94:
D5:7E:91:E2:52:7E:DD:7C:F7:23:D6:31:6A:D3:CE:05:5F:E5:97:B4:
48:C3:D4:77:85:7E:0E:6F:C4:DB:F4:16:47:F3:AE:43:75:F8:CA:25:
C8:C3:6D:97:C4:23:15:B8:6A:6A:0B:44
TIA
BR
Franky
Vorstand: Dirk Wilhelm (V), Wulf Jannsen
Aufsichtsrat: Ron Scheepers (V)
Handelsregister: HRB Saarbrücken Nr. 13201
Ust.ID Nr.: DE 153807627
next reply other threads:[~2024-04-22 10:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-22 10:25 Lindner, Frank [this message]
2024-04-22 10:35 ` WCN6856 monitor mode 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=FRYP281MB0160DB4CC65BD0BF23BE491AEB122@FRYP281MB0160.DEUP281.PROD.OUTLOOK.COM \
--to=frank.lindner@ghmt.de \
--cc=ath11k@lists.infradead.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).