Linux wireless drivers development
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: timg@tpi.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] ipw2200: Change driver default policies
Date: Tue, 14 Oct 2008 12:47:07 -0400	[thread overview]
Message-ID: <1224002827.1799.8.camel@localhost.localdomain> (raw)
In-Reply-To: <1224002103.10113.42.camel@johannes.berg>

On Tue, 2008-10-14 at 18:35 +0200, Johannes Berg wrote:
> On Tue, 2008-10-14 at 10:25 -0600, Tim Gardner wrote:
> 
> > >> 3) roaming=0 - do not automatically roam to another AP with the same SSID.
> > > 
> > > Not really sure why this should be changed?  Were there reported issues
> > > with this behavior?
> > > 
> > 
> > Its been my expereince that wireless drivers rarely make the correct
> > decision about when or where to roam. It also seems like a policy
> > decision that ought to be made elsewhere.
> > 
> > Frankly, I'm not that concerned about the roaming option. The default
> > for 'associate' was the one I _really_ wanted changed. I'll submit a v2
> > patch with just that change.
> 
> Would that also turn off the spectrum-polluting continuous scanning
> these cards do? :)

No, that would be a separate patch to disable the background scanning
behavior or at least tone it down to once every few seconds or
something.

Dan



  parent reply	other threads:[~2008-10-14 16:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-14 14:57 [PATCH] ipw2200: Change driver default policies Tim Gardner
2008-10-14 15:43 ` Dan Williams
2008-10-14 16:25   ` Tim Gardner
2008-10-14 16:35     ` Johannes Berg
2008-10-14 16:44       ` Tim Gardner
2008-10-14 16:47       ` Dan Williams [this message]
2008-10-14 16:35     ` 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=1224002827.1799.8.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=timg@tpi.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