From: Oleksij Rempel <linux@rempel-privat.de>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] 802.11k support in ath9k
Date: Fri, 11 Apr 2014 09:30:26 +0200 [thread overview]
Message-ID: <53479A12.6000706@rempel-privat.de> (raw)
In-Reply-To: <53453C3F.3090605@globaledgesoft.com>
Am 09.04.2014 14:25, schrieb Kathiravan Thirumoorthy:
> Hi Folks,
>
> I am thinking to work on 802.11k. To start up with this, I would be keen
> to know if ath9k supports RRM(802.11k) functionality?
> Looking for your valuable feedback and suggestions to start with.
> Thanks in advance.
I would suggest you to start investigation on your own. I'm not sure,
but probably you should take a look at hostapd and linux/net/wireless -
most of 802.11k work should happen on upper levels.
--
Regards,
Oleksij
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 278 bytes
Desc: OpenPGP digital signature
Url : http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20140411/6395535e/attachment.pgp
prev parent reply other threads:[~2014-04-11 7:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-09 12:25 [ath9k-devel] 802.11k support in ath9k Kathiravan Thirumoorthy
2014-04-11 7:30 ` Oleksij Rempel [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=53479A12.6000706@rempel-privat.de \
--to=linux@rempel-privat.de \
--cc=ath9k-devel@lists.ath9k.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