From: Johannes Berg <johannes@sipsolutions.net>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Dan Williams <dcbw@redhat.com>,
Linux Wireless <linux-wireless@vger.kernel.org>
Subject: Re: mrv8k vs. mac80211
Date: Fri, 16 May 2008 22:22:52 +0200 [thread overview]
Message-ID: <1210969372.6381.40.camel@johannes.berg> (raw)
In-Reply-To: <20080516172535.GA9880@tuxdriver.com>
[-- Attachment #1: Type: text/plain, Size: 984 bytes --]
On Fri, 2008-05-16 at 13:25 -0400, John W. Linville wrote:
> On Tue, May 13, 2008 at 12:00:21PM -0400, Dan Williams wrote:
> > Hi,
> >
> > mrv8k has commands that should be sent before a scan is started, and
> > after a scan has finished. There aren't really pre/post scan hooks in
> > mac80211, though there certainly could be without too much trouble. The
> > other possibility is to inspect the filter flags when
> > ops->configure_filter gets called, since FIF_BCN_PRBRESP_PROMISC gets
> > flipped before and after the scan. But that seems ugly and unstable.
> >
> > Any objections to adding ops->pre_scan and ops->post_scan hooks? Or
> > should I just use the configure_filter hack... or is there a better
> > way?
>
> The pre/post hooks make sense to me...Johannes?
I don't know, sort of makes sense, but on the other hand the userspace
MLME just does it all manually anyway! What exactly do you have to do to
the hardware for scanning?
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2008-05-16 20:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-13 16:00 mrv8k vs. mac80211 Dan Williams
2008-05-16 17:25 ` John W. Linville
2008-05-16 20:22 ` Johannes Berg [this message]
2008-05-16 22:05 ` Dan Williams
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=1210969372.6381.40.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=dcbw@redhat.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).