From: "Jouni Malinen" <jkm@devicescape.com>
To: Daniel Drake <dsd@gentoo.org>
Cc: jt@hpl.hp.com, softmac-dev@sipsolutions.net, netdev@vger.kernel.org
Subject: Re: SIOCGIWSCAN wireless event behaviour
Date: Thu, 20 Apr 2006 09:39:07 -0700 [thread overview]
Message-ID: <20060420163907.GD1321@instant802.com> (raw)
In-Reply-To: <4447979F.4050603@gentoo.org>
On Thu, Apr 20, 2006 at 03:15:59PM +0100, Daniel Drake wrote:
> I think the 'extra' SIOCGIWSCAN event may be confusing wpa_supplicant
> (but have not confirmed that yet).
No, they don't. madwifi-ng is already doing this with background
scanning and as was pointed out, there can be multiple programs asking
for scans, so user space must be prepared for multiple events anyway.
--
Jouni Malinen PGP id EFC895FA
prev parent reply other threads:[~2006-04-20 16:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-20 14:15 SIOCGIWSCAN wireless event behaviour Daniel Drake
2006-04-20 14:37 ` Dan Williams
2006-04-20 16:43 ` Jean Tourrilhes
2006-04-20 17:26 ` Jouni Malinen
2006-04-21 1:42 ` Daniel Drake
2006-04-20 16:39 ` Jouni Malinen [this message]
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=20060420163907.GD1321@instant802.com \
--to=jkm@devicescape.com \
--cc=dsd@gentoo.org \
--cc=jt@hpl.hp.com \
--cc=netdev@vger.kernel.org \
--cc=softmac-dev@sipsolutions.net \
/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).