From: sandeep suresh <sandeep.suresh@yahoo.co.in>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] 802.11k, 802.11v and 802.11r support in QCA9592-AR1B
Date: Fri, 6 Jan 2017 08:15:02 +0000 (UTC) [thread overview]
Message-ID: <587211005.1320200.1483690502965@mail.yahoo.com> (raw)
In-Reply-To: 587211005.1320200.1483690502965.ref@mail.yahoo.com
? Dear Experts,We are using? QCA9592-AR1B ( WPEA-252NI ) in one of our products and it supports 802.11bgn. There is a requirement to support the following standards:-802.11k802.11v and802.11r.Do we have the driver patches to support these standards? Please let me know how to go about this.Thanks & regardsSandeep Suresh.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20170106/e627ab18/attachment.htm
next parent reply other threads:[~2017-01-06 8:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <587211005.1320200.1483690502965.ref@mail.yahoo.com>
2017-01-06 8:15 ` sandeep suresh [this message]
2017-01-06 8:45 ` [ath9k-devel] 802.11k, 802.11v and 802.11r support in QCA9592-AR1B Sven Eckelmann
2017-01-06 9:00 ` sandeep suresh
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=587211005.1320200.1483690502965@mail.yahoo.com \
--to=sandeep.suresh@yahoo.co.in \
--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;
as well as URLs for NNTP newsgroup(s).