Return-path: Received: from casper.infradead.org ([85.118.1.10]:39905 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751460AbYIUTVD (ORCPT ); Sun, 21 Sep 2008 15:21:03 -0400 Date: Sun, 21 Sep 2008 12:20:48 -0700 From: Arjan van de Ven To: Wei Weng Cc: Evgeniy Polyakov , netdev@vger.kernel.org, linux-kernel@vger.kernel.org, ipw2100-devel@lists.sourceforge.net, linux-wireless@vger.kernel.org, yi.zhu@intel.com, reinette.chatre@intel.com, jgarzik@pobox.com, linville@tuxdriver.com, davem@davemloft.net Subject: Re: Mark IPW2100 as BROKEN: Fatal interrupt. Scheduling firmware restart. Message-ID: <20080921122048.2bd52541@infradead.org> (sfid-20080921_212109_904338_73B79F86) In-Reply-To: <48D697F5.9050802@acedsl.com> References: <20080921172316.GA6306@2ka.mipt.ru> <20080921110422.1d010b96@infradead.org> <20080921182835.GA11473@2ka.mipt.ru> <20080921113513.16677c4e@infradead.org> <48D697F5.9050802@acedsl.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-wireless-owner@vger.kernel.org List-ID: On Sun, 21 Sep 2008 14:52:37 -0400 Wei Weng wrote: > > again.. so how about you detect this condition and do, in the driver > > code, the equivalent of rmmod/insmod to the hardware. I'm sure > > people who have the hardware would appreciate that type of patch a > > lot more than the one you sent out. > > > > I guess it is your way of "middle finger" to all the IPW2100 > customers who try to use it on a Linux machine. if suggesting a workaround is giving the middle finger in your mind, then I don't think it's worth my time to discuss this further with you. -- Arjan van de Ven Intel Open Source Technology Centre For development, discussion and tips for power savings, visit http://www.lesswatts.org