From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Greear <greearb@candelatech.com>
Cc: Jouni Malinen <j@w1.fi>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: RFC: mac80211/ath9k: allow scanning single channel if other VIF is associated.
Date: Wed, 15 Sep 2010 17:37:13 +0200 [thread overview]
Message-ID: <1284565033.7705.5.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <4C90E708.5050109@candelatech.com>
On Wed, 2010-09-15 at 08:32 -0700, Ben Greear wrote:
> >> Right, but as soon as one finished, the next would start, and at least in .31,
> >> that caused the first to un-associate, giving never-ending loop of interfaces
> >> scanning and trying to associate.
> >
> > There should be a grace period maybe?
>
> I don't think that really fixes anything, except make the race between
> full scan and attempting for the first interface to associate harder to
> hit (and that is only useful if the scan-one logic is enabled anyway).
I think you just need to update ... newer kernels shouldn't be allowing
a scan while trying to associate, I think.
johannes
next prev parent reply other threads:[~2010-09-15 15:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-13 23:14 RFC: mac80211/ath9k: allow scanning single channel if other VIF is associated Ben Greear
2010-09-15 3:03 ` Jouni Malinen
2010-09-15 5:30 ` Ben Greear
2010-09-15 5:46 ` Dan Williams
2010-09-15 5:48 ` Dan Williams
2010-09-15 5:49 ` Ben Greear
2010-09-15 10:16 ` Johannes Berg
2010-09-15 14:21 ` Ben Greear
2010-09-15 14:24 ` Johannes Berg
2010-09-15 15:32 ` Ben Greear
2010-09-15 15:37 ` Johannes Berg [this message]
2010-09-15 16:12 ` Ben Greear
2010-09-15 20:31 ` Jouni Malinen
2010-09-15 21:04 ` Luis R. Rodriguez
2010-09-16 0:11 ` Ben Greear
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=1284565033.7705.5.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=greearb@candelatech.com \
--cc=j@w1.fi \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.