From: "Tomas Winkler" <tomasw@gmail.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
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 11:03:02 +0300 [thread overview]
Message-ID: <1ba2fa240809190103i69c66978he4762fd350ab2e5d@mail.gmail.com> (raw)
In-Reply-To: <1221795715.10419.15.camel@johannes.berg>
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?
* provide a way to limit the number of channels in a scan (for
faster roaming candidate search)
>
> * provide a function to just pass in the whole beacon/probe response
> frame and pick it apart itself
> * handle aging
> * provide a wext "set scan" hook that creates a request and passes it
> off to ->scan(), provide wext "get scan" hook
> * parse the supported rates into a bitmap like mac80211 does now, based
> on the bitrate information the wiphy provides
>
>> in mac80211, we need to
>> * pass the scan request to the hardware offload
>> * handle multiple SSIDs in a scan
>> * use BSS list stuff cfg80211 needs to provide
>> * handle active/passive properly
>
> * use all those helpers I mentioned above
>
> Also, we need to think about
> * how fullmac stuff can integrate, can it provide this IE-based
> information, and if not, is it feasible to just synthesize it?
> * whether this should really be per wiphy as it is now, or somehow more
> per netdev, or not related to a netdev at all...
>
> johannes
>
next prev parent reply other threads:[~2008-09-19 8:03 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 [this message]
2008-09-19 8:56 ` Johannes Berg
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=1ba2fa240809190103i69c66978he4762fd350ab2e5d@mail.gmail.com \
--to=tomasw@gmail.com \
--cc=dcbw@redhat.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.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