linux-kernel - Re: ipw3945 status

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 for Android: free password hash cracker in your pocket

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

Message-ID: <44CC993B.6070309@l4x.org>
Date:	Sun, 30 Jul 2006 13:34:19 +0200
From:	Jan Dittmer <jdi@....org>
To:	Matthew Garrett <mjg59@...f.ucam.org>
CC:	Pavel Machek <pavel@...e.cz>, Jirka Lenost Benc <jbenc@...e.cz>,
	kernel list <linux-kernel@...r.kernel.org>,
	ipw2100-admin@...ux.intel.com
Subject: Re: ipw3945 status

Matthew Garrett schrieb:
> On Sun, Jul 30, 2006 at 12:40:42PM +0200, Pavel Machek wrote:
> 
> 
>>I'm unfortunate enough to have x60 with ipw card. Card works okay, but
>>driver is 16K LoC and needs binary daemon (ugh). Plus, it lives as an
>>external module...
> 
> 
> I have a mostly working replacement for the binary daemon, but it causes 
> the firmware to crash at the point where it triggers an association. If 
> anyone's keen on trying to figure out what's up, I'll clean up the code 
> and stick it somewhere.

Why not get rid of the daemon like bsd did [0]? Otherwise in
5 years you'll have 42 daemons running which communicate with
the firmware of various devices, each having a different inter-
face.

Jan

[0] http://kerneltrap.org/node/6650


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/