From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752496AbYIURji (ORCPT ); Sun, 21 Sep 2008 13:39:38 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751052AbYIURj1 (ORCPT ); Sun, 21 Sep 2008 13:39:27 -0400 Received: from relay.2ka.mipt.ru ([194.85.80.65]:42354 "EHLO 2ka.mipt.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750877AbYIURj0 (ORCPT ); Sun, 21 Sep 2008 13:39:26 -0400 Date: Sun, 21 Sep 2008 21:38:12 +0400 From: Evgeniy Polyakov To: Michael Buesch Cc: 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: <20080921173811.GB6306@2ka.mipt.ru> References: <20080921172316.GA6306@2ka.mipt.ru> <200809211936.00414.mb@bu3sch.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200809211936.00414.mb@bu3sch.de> User-Agent: Mutt/1.5.9i Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Sep 21, 2008 at 07:36:00PM +0200, Michael Buesch (mb@bu3sch.de) wrote: > > Intel folks, please fix this problem, I see no other way to force you to do > > this than to mark ipw2100 driver as broken, since that is what it is. > > You are pretty funny, actually. :) > > I think the bug should be fixed, but what makes _you_ think you can _force_ > anybody to do so? Maybe because I bought that adapter and it stopped working and Intel knows about this bug and does not fix it for years? -- Evgeniy Polyakov