From: Stefan Feirer <e0926020@student.tuwien.ac.at>
To: ath10k@lists.infradead.org
Subject: Support of 802.11k
Date: Thu, 2 Jun 2016 09:27:05 +0200 [thread overview]
Message-ID: <574FDFC9.1070801@student.tuwien.ac.at> (raw)
Hello,
I'm currently working on my master thesis at vienna university of
technology.
Topic of my work is building a prototype to measure wifi roaming
performance with 802.11k (Radio Resouce Management) and 802.11r protocol
amendments.
My hardware setup uses the PCIe Wifi Card Compex WLE600VX with QCA9882
Chipset and ath10k_pci kernel module.
Operating System is Ubuntu 15.10 with Kernel Version 4.2.
With my setup 802.11r is working well with wpa_supplicant but I'm not
able to get 802.11k working.
As I already mentioned I'm using the ath10k kernel module with firmware
version 10.2.4.45.
I suppose 802.11k (RRM) is not working because it is not supported by
the firmware.
The reason of my guess is the following:
When I looked through the ath10k source code for RRM support I found out
that in the file wmi.c there are the structs
- wmi_cmd_map
- wmi_10x_cmd_map
- wmi_10_2_4_cmd_map
In the last two the function bcn_tmpl_cmdid and prb_tmpl_cmdid both are
not supported (and I use firmware version 10.2.4) and these use the
struct wmi_bcn_prb_info (wmi.h) which includes the rrm info.
This leads me to two questions:
- Am I right, that the firmware does not support 802.11k or should
802.11k be supported by the QCA9882 Chipset and the atheros firmware and
kernel modules?
- Are there any atheros wifi modules which were successfully tested with
802.11k?
Hopefully someone can help me with this!
Thanks
Stefan Feirer
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
reply other threads:[~2016-06-02 7:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=574FDFC9.1070801@student.tuwien.ac.at \
--to=e0926020@student.tuwien.ac.at \
--cc=ath10k@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 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.