linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Tomas Winkler <tomasw@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
	Dan Williams <dcbw@redhat.com>
Subject: Re: technology preview: scan with cfg80211
Date: Fri, 19 Sep 2008 10:56:05 +0200	[thread overview]
Message-ID: <1221814565.10419.19.camel@johannes.berg> (raw)
In-Reply-To: <1ba2fa240809190103i69c66978he4762fd350ab2e5d@mail.gmail.com> (sfid-20080919_100303_802308_72777315)

[-- Attachment #1: Type: text/plain, Size: 1356 bytes --]

On Fri, 2008-09-19 at 11:03 +0300, Tomas Winkler wrote:
> On Fri, Sep 19, 2008 at 6:41 AM, Johannes Berg
> <johannes@sipsolutions.net> wrote:
> > On Fri, 2008-09-19 at 05:18 +0200, Johannes Berg wrote:
> >> This is totally incomplete:
> >>
> >> cfg80211 needs to
> >>  * actually hash on the BSSID instead of putting things into a list
> >>  * provide BSS list functions so mac80211 need not keep track
> >>  * allow a "private" area in each scan result with hw-provided size
> >>  * handle mesh properly
> >>  * provide a way for the hw to limit the number of SSIDs in a scan

> Don't understand this requirement?

Limiting the number of SSIDs? Well I don't want to have userspace
request an active scan for like 100 SSIDs, which currently _is_ possible
(mac80211 will reject anything but 1 right now though). Hence, I want to
have a "max probes" or something like that in the wiphy structure that
we can use (a) tell userspace how many we support and (b) limit the
number appropriately.

>   * provide a way to limit the number of channels in a scan (for
> faster roaming candidate search)

Hey, unfair! ;) I did leave a lot of TODOs but this wasn't one of them.
You can provide a channel list and it'll scan only those (except hw scan
right now but that'll be fixed once we pass the scan request struct
through)

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2008-09-19  8:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-19  3:18 technology preview: scan with cfg80211 Johannes Berg
2008-09-19  3:41 ` Johannes Berg
2008-09-19  8:03   ` Tomas Winkler
2008-09-19  8:56     ` Johannes Berg [this message]
2008-09-19 10:37       ` Tomas Winkler
2008-09-19 10:42         ` Johannes Berg
2008-09-19 11:45           ` Tomas Winkler
2008-09-19 11:54             ` Johannes Berg
2008-09-19 13:16 ` technology preview: scan with cfg80211 (v2) Johannes Berg
2008-09-19 14:17   ` Johannes Berg
2008-09-19 17:48     ` Luis R. Rodriguez
2008-09-19 19:18       ` 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=1221814565.10419.19.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=dcbw@redhat.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=tomasw@gmail.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).