From: Johannes Berg <johannes@sipsolutions.net>
To: "Malinen, Jouni" <jouni@qca.qualcomm.com>
Cc: Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.de>,
"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 18:09:25 +0100 [thread overview]
Message-ID: <1354122565.9345.41.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <8887AA04B7EC49479420AE48C5F94A930172CE02@NASANEXD02D.na.qualcomm.com>
On Wed, 2012-11-28 at 17:06 +0000, Malinen, Jouni wrote:
> >FWIW, right now our plan for iwlwifi is to only really support it with
> >the P2P Device wdev, but I'm not sure what implications that has in
> >terms of support for GAS/ANQP etc. We might have to revisit that.
>
> GAS/ANQP is pre-association if that makes any difference. Anyway, quite a
> few new things will start depending on off channel Action frames and
> everything I'm working on this area will most likely be using r-o-c..
Yes, pre-association might make a difference. I think it's entirely
reasonable to implement it all using ROC, I just don't know whether or
not we can support it right now out of the box.
> >Maybe we should start advertising where it's supported so wpa_s/hostapd
> >can disable/enable features appropriately?
>
> Yeah, sounds reasonable. I guess you could also reject the r-o-c command,
> but it is cleaner if this can be determined beforehand.
We do that today. Actually, in the current driver we do allow it but
it's rather messy so I might remove the ability once we have P2P Device
support, not sure. In the future we'll have it only on P2P Device,
though making it work on unassociated interfaces should not be a big
issue.
johannes
next prev parent reply other threads:[~2012-11-28 17:09 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
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 [this message]
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=1354122565.9345.41.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ath9k-devel@lists.ath9k.org \
--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=simon.wunderlich@s2003.tu-chemnitz.de \
--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).