From owner-svn-src-all@FreeBSD.ORG Thu May 6 18:26:58 2010 Return-Path: Delivered-To: svn-src-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 02663106567C; Thu, 6 May 2010 18:26:58 +0000 (UTC) (envelope-from bschmidt@mx.techwires.net) Received: from mx.techwires.net (mx.techwires.net [79.140.39.242]) by mx1.freebsd.org (Postfix) with ESMTP id 6F8968FC1B; Thu, 6 May 2010 18:26:57 +0000 (UTC) Received: by mx.techwires.net (Postfix, from userid 1001) id 34FFC291A1; Thu, 6 May 2010 20:11:10 +0200 (CEST) Date: Thu, 6 May 2010 20:11:10 +0200 From: Bernhard Schmidt To: Ben Kaduk Message-ID: <20100506181110.GA6628@mx.techwires.net> References: <201005061753.o46Hr4d0046296@svn.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org Subject: Re: svn commit: r207709 - head/sys/dev/iwn X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 May 2010 18:26:58 -0000 On Thu, May 06, 2010 at 01:55:11PM -0400, Ben Kaduk wrote: > On Thu, May 6, 2010 at 1:53 PM, Bernhard Schmidt wrote: > > Author: bschmidt > > Date: Thu May 6 17:53:04 2010 > > New Revision: 207709 > > URL: http://svn.freebsd.org/changeset/base/207709 > > > > Log: > > Add a workaround for a bug in the firmware regarding the transition > > from passive to active scans. Basicly disable it by increasing the > > amount packets to be received to an amount which can't be reached > > during dwell times. > > Is this expected to fix the firmware errors that have cropped up > periodically for me? > (Sorry for the lack of useful bug reports, etc.) I'm not aware that this generated any firmware errors. For scans on certain channels (definitely those which require radar detection) the firmware scan command might return with an error code instead of the expected scan result though. Which made it pretty much impossible to connect on those channels. -- Bernhard