Date: Sun, 21 Sep 2008 21:38:12 +0400
From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: Michael Buesch <mb@bu3sch.de>
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> (sfid-20080921_193930_540795_7309BF56)
References: <20080921172316.GA6306@2ka.mipt.ru> <200809211936.00414.mb@bu3sch.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <200809211936.00414.mb@bu3sch.de>
Sender: linux-wireless-owner@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