From: Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.de>
To: "Malinen, Jouni" <jouni@qca.qualcomm.com>
Cc: Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.de>,
Johannes Berg <johannes@sipsolutions.net>,
"mathias.kretschmer@fokus.fraunhofer.de"
<mathias.kretschmer@fokus.fraunhofer.de>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linville@tuxdriver.com" <linville@tuxdriver.com>,
Simon Wunderlich <siwu@hrz.tu-chemnitz.de>,
"Rodriguez, Luis" <rodrigue@qca.qualcomm.com>,
"ath9k-devel@lists.ath9k.org" <ath9k-devel@lists.ath9k.org>,
"Giori, Kathy" <kgiori@qca.qualcomm.com>,
"zefir.kurtisi@neratec.com" <zefir.kurtisi@neratec.com>
Subject: Re: [ath9k-devel] [RFC 1/3] nl80211: add spec scan flag
Date: Wed, 28 Nov 2012 17:12:19 +0100 [thread overview]
Message-ID: <20121128161219.GA6642@pandem0nium> (raw)
In-Reply-To: <8887AA04B7EC49479420AE48C5F94A930172CD48@NASANEXD02D.na.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 1813 bytes --]
Hey Jouni,
On Wed, Nov 28, 2012 at 03:29:36PM +0000, Malinen, Jouni wrote:
>
>
> On 11/28/12 7:19 AM, "Simon Wunderlich"
> <simon.wunderlich@s2003.tu-chemnitz.de> wrote:
>
> >The main reason why I wanted to use this function is that it can be used
> >while operation, that is sending power save, forbidding payload tx, etc.
>
> Have you looked at the remain-on-channel commands?
>
TBH, today was the first time I've had a more close look. :)
> >It seems there is no way to trigger a scan from within ath9k/debugfs,
> >right?
>
> I don't think there is nor that there should be.. Do you really need scan
> operating for this? I would use remain-on-channel commands from a user
> space app to go through the channels you want to analyze.
>
Hmm, that would be possible as well ... Using the scan function is very
convenient as I don't have to think about cycling, channel lists, etc.
But putting more control to userspace is also possible, if we can ask the
driver to just have a "quick spectral peek" on another channel.
Anyway, you'd suggest to use the NL80211 remain on channel command for that?
Or add a new "spectral scan" nl80211 command to do a spectral scan on this
(or multiple) channels, and use the various functions from mac80211/offchannel.c?
BTW, is there any limitation to remain on channel commands, like will they
work on AP ifaces, Ad-Hoc ifaces, MultiSSID in general, etc?
> >I could also cycle channels within ath9k, but the main problem I see is
> >that
> >I can't turn off TX/go into power save mode from the driver, or would you
> >see
> >anything feasible?
>
> Remain-on-channel should take care of that, but yes, that would not be
> triggered from ath9k, but from user space.
That sounds good. :)
Thanks for the hint!
Simon
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-11-28 16:12 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-27 19:01 [RFC 0/3] Add spectral scan support for Atheros AR92xx/AR93xx Simon Wunderlich
2012-11-27 19:01 ` [RFC 1/3] nl80211: add spec scan flag Simon Wunderlich
2012-11-28 12:35 ` Johannes Berg
2012-11-28 12:43 ` Johannes Berg
2012-11-28 15:19 ` Simon Wunderlich
2012-11-28 15:29 ` [ath9k-devel] " Malinen, Jouni
2012-11-28 16:12 ` Simon Wunderlich [this message]
2012-11-28 16:49 ` Malinen, Jouni
2012-11-28 16:57 ` Johannes Berg
2012-11-28 17:06 ` Malinen, Jouni
2012-11-28 17:09 ` Johannes Berg
2012-11-28 16:26 ` Johannes Berg
2012-11-28 19:39 ` Simon Wunderlich
2012-11-27 19:01 ` [RFC 2/3] mac80211: add spectral_scan function, hook it up in scanning Simon Wunderlich
2012-11-27 19:01 ` [RFC 3/3] ath9k: add spectral scan feature Simon Wunderlich
2012-12-01 4:00 ` Adrian Chadd
2012-12-05 10:40 ` Simon Wunderlich
2012-12-05 11:38 ` Felix Fietkau
2012-12-05 12:05 ` Adrian Chadd
2012-12-17 20:08 ` Adrian Chadd
2012-11-27 19:01 ` [RFC] iw: add spectral scan attribute to scan function Simon Wunderlich
2012-11-27 19:16 ` [RFC 0/3] Add spectral scan support for Atheros AR92xx/AR93xx Martin Schleier
2012-11-27 19:49 ` Simon Wunderlich
2012-11-27 20:32 ` Simon Wunderlich
2012-11-27 21:01 ` Jonathan Bither
2012-11-28 10:37 ` Simon Wunderlich
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=20121128161219.GA6642@pandem0nium \
--to=simon.wunderlich@s2003.tu-chemnitz.de \
--cc=ath9k-devel@lists.ath9k.org \
--cc=johannes@sipsolutions.net \
--cc=jouni@qca.qualcomm.com \
--cc=kgiori@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mathias.kretschmer@fokus.fraunhofer.de \
--cc=rodrigue@qca.qualcomm.com \
--cc=siwu@hrz.tu-chemnitz.de \
--cc=zefir.kurtisi@neratec.com \
/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).