netdev - Re: Mark IPW2100 as BROKEN: Fatal interrupt. Scheduling firmware restart.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080921173811.GB6306@2ka.mipt.ru>
Date:	Sun, 21 Sep 2008 21:38:12 +0400
From:	Evgeniy Polyakov <johnpol@....mipt.ru>
To:	Michael Buesch <mb@...sch.de>
Cc:	netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
	ipw2100-devel@...ts.sourceforge.net,
	linux-wireless@...r.kernel.org, yi.zhu@...el.com,
	reinette.chatre@...el.com, jgarzik@...ox.com,
	linville@...driver.com, davem@...emloft.net
Subject: Re: Mark IPW2100 as BROKEN: Fatal interrupt. Scheduling firmware restart.

On Sun, Sep 21, 2008 at 07:36:00PM +0200, Michael Buesch (mb@...sch.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
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html