netdev - Re: [Madwifi-devel] ar5k and Atheros AR5005G

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:	Wed, 29 Nov 2006 16:58:46 +0100 (CET)
From:	"Michael Renzmann" <madwifi@...pam.otaku42.de>
To:	"Michael Buesch" <mb@...sch.de>
Cc:	"David Kimdon" <david.kimdon@...icescape.com>,
	"Nick Kossifidis" <mickflemm@...il.com>,
	"Daniel Drake" <ddrake@...ntes3d.com>, netdev@...r.kernel.org,
	madwifi-devel@...ts.sourceforge.net
Subject: Re: [Madwifi-devel] ar5k and Atheros AR5005G

Hi.

> On Wednesday 29 November 2006 16:24, David Kimdon wrote:
>> There is absolutely no reason why dadwifi can't be merged into the
>> mainline once the hal issue is resolved.
> Last time we talked about that stuff, it was decided that
> we don't want a HAL... See archives.

IIRC Pavel already explained that getting rid of the HAL per se should be
no problem - it could easily be dissolved into the driver, if that is one
of the requirements to be fulfilled before the driver (MadWifi or DadWifi)
is considered for mainline inclusion. As soon as there is source available
to dissolve, at least.

>From what I understood the "... once the hal issue is resolved" part of
David's mail refered to exactly that question.

Bye, Mike



-
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