From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261304AbVFIDgX (ORCPT ); Wed, 8 Jun 2005 23:36:23 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261594AbVFIDgX (ORCPT ); Wed, 8 Jun 2005 23:36:23 -0400 Received: from fmr14.intel.com ([192.55.52.68]:33929 "EHLO fmsfmr002.fm.intel.com") by vger.kernel.org with ESMTP id S261304AbVFIDgV (ORCPT ); Wed, 8 Jun 2005 23:36:21 -0400 Subject: Re: ipw2100: firmware problem From: Zhu Yi To: Pavel Machek Cc: James Ketrenos , Jeff Garzik , Netdev list , kernel list , "James P. Ketrenos" In-Reply-To: <20050608223437.GB2614@elf.ucw.cz> References: <20050608142310.GA2339@elf.ucw.cz> <42A723D3.3060001@linux.intel.com> <20050608212707.GA2535@elf.ucw.cz> <42A76719.2060700@linux.intel.com> <20050608223437.GB2614@elf.ucw.cz> Content-Type: text/plain Organization: Intel Corp. Date: Thu, 09 Jun 2005 11:33:10 +0800 Message-Id: <1118287990.10234.114.camel@debian.sh.intel.com> Mime-Version: 1.0 X-Mailer: Evolution 2.2.2 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Hi Pavel, On Thu, 2005-06-09 at 00:34 +0200, Pavel Machek wrote: > Actually it would still transmit when user did not want it to. I > believe that staying "quiet" is right thing, long-term. And it could > solve firmware-loading problems, short-term... If ipw2100 is built into kernel, you can disable it by kernel parameter ipw2100.disable=1. Then you can enable it with: $ echo 0 > /sys/bus/pci/drivers/ipw2100/*/rf_kill > How long does association with AP take? Anyway it should be easy to > tell driver to associate ASAP, just after the insmod... Are you suggesting by default it is disabled for built into kernel but enabled as a module? Thanks, -yi