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:	Tue, 5 Dec 2006 15:39:06 +0100 (CET)
From:	"Michael Renzmann" <madwifi@...pam.otaku42.de>
To:	"Luis R. Rodriguez" <mcgrof@...il.com>
Cc:	"Stephen Hemminger" <shemminger@...l.org>,
	"David Kimdon" <david.kimdon@...icescape.com>,
	netdev@...r.kernel.org, madwifi-devel@...ts.sourceforge.net,
	"Nick Kossifidis" <mickflemm@...il.com>,
	"Michael Buesch" <mb@...sch.de>
Subject: Re: [Madwifi-devel] ar5k and Atheros AR5005G

Hi all.

> To make things easier for development I'd like to suggest a few madwif
> ibranches created:
>
> * madwifi-1152-openhal: based on madwifi-1152, patched with my patch,
> added openhal, old hal removed. Working free solution. Should exist
> just as a reference and to allow users to checkout a working free
> alternative in the mean time.
>
> * madwifi-dadwifi-openal: based on the latest dadwifi with the
> openhal, old hal removed. As dadwifi gets updated you can pull updates
> to this branch. As the openhal advances you can make updates to the
> openhal here.

I've set up the suggested branches, with slight changing to the proposed
names:

* http://svn.madwifi.org/branches/madwifi-old-openhal (based on r1142)
* http://svn.madwifi.org/branches/dadwifi-openhal (based on r1827)

Neither of them has received any modifications yet, they are basically
copies of the mentioned revisions. I'm currently lacking the time to
import Nick's work into the madwifi-old-openhal branch, for example - it
would be nice if someone else could work on that.

The MadWifi project happily provides any interested party access to the
resources we have at hands - including (but not limited to) r/w access to
the repository, an account for our Trac (used to manage tickets for bugs,
patches, ...), e-mail, .... Let me know if you need something in that
regard and I'll try to get it done. We'd love to support these efforts
where possible.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ