From mboxrd@z Thu Jan 1 00:00:00 1970 From: James Ketrenos Subject: Re: ipw2100: firmware problem Date: Wed, 08 Jun 2005 12:10:37 -0500 Message-ID: <42A7268D.9020402@linux.intel.com> References: <20050608142310.GA2339@elf.ucw.cz> <200506081744.20687.vda@ilport.com.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Pavel Machek , Jeff Garzik , Netdev list , kernel list , "James P. Ketrenos" Return-path: To: Denis Vlasenko In-Reply-To: <200506081744.20687.vda@ilport.com.ua> Sender: netdev-bounce@oss.sgi.com Errors-to: netdev-bounce@oss.sgi.com List-Id: netdev.vger.kernel.org Denis Vlasenko wrote: >My position is that wifi drivers must start up in an "OFF" mode. >Do not send anything. Do not join APs or start IBSS. >Thus, no need to load fw in early boot. > > This should be an option for the user if that is the desired behavior. We support that with the ipw2100 and ipw2200 projects via module parameters to disable the radio during module load. Having a standard module parameter for wireless drivers would be nice. My approach is to make the driver so it supports as many usage models as possible, leaving policy to other components of the system. If the user wants it to scan and associate immediately, that should be supported. Likewise if they want the module to be loaded w/ the radio off, they can do that as well. Since most (if not all) laptops support an RF kill switch, I tend to defer to the physical switch as the user's point of control and set the driver defaults to try and use the radio if it is enabled. James