From: Johannes Berg <johannes@sipsolutions.net>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [RFC 1/3] nl/cfg80211: add chan_time for scan request
Date: Fri, 02 Aug 2013 15:01:10 +0200 [thread overview]
Message-ID: <1375448470.18144.10.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <CA+BoTQ=XNeYL1KLGQ4gRCZ03a9XsAWde4O7_T-dqKndLLKeX_g@mail.gmail.com> (sfid-20130802_135231_798451_6ACEA72F)
> > That's what I'm worried about - the implicit semantic change here.
>
> I think I understand your point now.
>
> I'm thinking of using series of passive scans for ACS now, so perhaps
> the whole chan_time stuff is unnecessary. What are your thoughts about
> it?
Well, still then you're relying on the fact that passive channels scans
will stick to each channel for ~110ms or so. This is true today, but
it's not really specified.
I don't think that using the scan command would be a big deal, but maybe
this 'measurement' behaviour should be explicitly enabled? Maybe other
devices even have to do something special to collect the data.
johannes
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2013-08-02 13:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 8:39 [RFC 0/3] introduce chan_time parameter to scan request Michal Kazior
2013-07-29 8:39 ` [RFC 1/3] nl/cfg80211: add chan_time for " Michal Kazior
2013-08-01 7:40 ` Johannes Berg
2013-08-01 9:14 ` Michal Kazior
2013-08-02 11:25 ` Johannes Berg
2013-08-02 11:52 ` Michal Kazior
2013-08-02 13:01 ` Johannes Berg [this message]
[not found] ` <CACA4iOrZSARKFVFx1E2QPyH=xZzQp+VoyPu_tuFWgBR3tQwOmw@mail.gmail.com>
2013-08-02 12:56 ` Sunil Dutt
2013-07-29 8:39 ` [RFC 2/3] mac80211: add support for scan chan_time parameter Michal Kazior
2013-07-29 8:39 ` [RFC 3/3] ath10k: respect chan_time parameter in scan request Michal Kazior
2013-08-01 7:36 ` [RFC 0/3] introduce chan_time parameter to " Johannes Berg
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=1375448470.18144.10.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=michal.kazior@tieto.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