netdev - Re: zd1211 ported to Devicescape stack

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: <200612021332.33255.flamingice@sourmilk.net>
Date:	Sat, 2 Dec 2006 13:32:28 -0500
From:	Michael Wu <flamingice@...rmilk.net>
To:	Ulrich Kunitz <kune@...ne-taler.de>
Cc:	Daniel Drake <dsd@...too.org>, netdev@...r.kernel.org,
	John Linville <linville@...driver.com>,
	Luis Rodriguez <mcgrof@...il.com>
Subject: Re: zd1211 ported to Devicescape stack

On Saturday 02 December 2006 12:57, Ulrich Kunitz wrote:
> I intend to track the d80211 stack, care for the forward porting
> and see also a number of things, which should be done for d80211.
>
> - 802.11a support
> - better d80211 integration (d80211_tx_status, led stuff)
> - cleanups
>
Great! I expected to handle the patch porting alone, but it's better to have 
someone used to this hardware doing this.

> This will make the d80211 driver the development branch and the
> mainline driver the maintenance branch. As already stated I intend
> care for forwardportsi of the mainline fixes, but IMHO we should
> not care to much for backports and backport compatibility.
I avoided cleanups in the patch to make any patch porting from the mainline 
driver easier, but if it's okay with you, I might make a few zd1211-d80211 
specific clean up patches.

Thanks,
-Michael Wu

Content of type "application/pgp-signature" skipped