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]

Date:	Sun, 21 Sep 2008 12:20:48 -0700
From:	Arjan van de Ven <arjan@...radead.org>
To:	Wei Weng <wweng@...dsl.com>
Cc:	Evgeniy Polyakov <johnpol@....mipt.ru>, 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, 21 Sep 2008 14:52:37 -0400
Wei Weng <wweng@...dsl.com> 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
--
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