From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Avery Pennarun <apenwarr@gmail.com>
Cc: ath10k <ath10k@lists.infradead.org>
Subject: Re: Support for scan while in AP mode, and offchannel while in AP mode
Date: Tue, 19 Aug 2014 08:50:50 +0300 [thread overview]
Message-ID: <8761hpc9j9.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CAHqTa-0GxKjo2ObRtoAKu6H9J6upC7JNS44MpNQpFDPXpiEKJw@mail.gmail.com> (Avery Pennarun's message of "Mon, 18 Aug 2014 22:26:42 -0400")
Avery Pennarun <apenwarr@gmail.com> writes:
> In the ath9k and several other drivers, commands like the following
> work while in AP mode:
>
> iw wlan0 scan -u ap-force passive
> and
> iw wlan0 offchannel 2452 100
>
> On ath10k (using a driver from v3.15-rc1 as of April 13th), these tell
> me the operation is not supported.
Yeah, mac80211 only supports this with sw_scan but ath10k uses hw_scan.
From ieee80211_alloc_hw():
if (!ops->hw_scan)
wiphy->features |= NL80211_FEATURE_LOW_PRIORITY_SCAN |
NL80211_FEATURE_AP_SCAN;
> Are there any plans to implement this feature? It's important in
> order to implement automatic channel change in case of changes in the
> interference environment.
No plans at the moment. Does anyone know how much work would it be to
change mac80211 to support this with hw_scan?
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2014-08-19 5:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-19 2:26 Support for scan while in AP mode, and offchannel while in AP mode Avery Pennarun
2014-08-19 5:50 ` Kalle Valo [this message]
2014-08-19 5:56 ` Avery Pennarun
2014-08-19 6:07 ` Kalle Valo
2014-08-19 6:24 ` Michal Kazior
2014-08-19 6:30 ` Kalle Valo
2014-08-19 7:01 ` Michal Kazior
2014-08-27 6:46 ` Avery Pennarun
2014-08-27 6:55 ` Michal Kazior
2014-08-27 7:41 ` Avery Pennarun
2014-08-19 15:23 ` Adrian Chadd
2014-08-19 21:46 ` Avery Pennarun
2014-08-19 21:56 ` Adrian Chadd
2014-08-19 22:01 ` Avery Pennarun
2014-08-19 6:19 ` Michal Kazior
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=8761hpc9j9.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=apenwarr@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox