| 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
| ||
|
Message-ID: <20061115192054.GA10009@tuxdriver.com> Date: Wed, 15 Nov 2006 14:21:05 -0500 From: "John W. Linville" <linville@...driver.com> To: Michael Buesch <mb@...sch.de> Cc: madwifi-devel@...ts.sourceforge.net, lwn@....net, mcgrof@...il.com, david.kimdon@...icescape.com, linux-kernel@...r.kernel.org, netdev@...r.kernel.org Subject: Re: ANNOUNCE: SFLC helps developers assess ar5k (enabling free Atheros HAL) On Wed, Nov 15, 2006 at 07:42:14PM +0100, Michael Buesch wrote: > Now that it seems to be ok to use these openbsd sources, should I port > them to my driver framework? > I looked over the ar5k code and, well, I don't like it. ;) > I don't really like having a HAL. I'd rather prefer a "real" driver > without that HAL obfuscation. I don't think anyone likes the HAL-based architecture. I don't think we will accept a HAL-based driver into the upstream kernel. The point is that the ar5k is now safe to be used as a reference and source of information (and code, as appropriate) without copyright FUD. Distilling that information into a proper Linux driver is work that remains to be done. John -- John W. Linville linville@...driver.com - 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/
Powered by blists - more mailing lists