From mboxrd@z Thu Jan 1 00:00:00 1970 From: "John W. Linville" Subject: Re: ANNOUNCE: SFLC helps developers assess ar5k (enabling free Atheros HAL) Date: Wed, 15 Nov 2006 14:21:05 -0500 Message-ID: <20061115192054.GA10009@tuxdriver.com> References: <20061115031025.GH3451@tuxdriver.com> <200611151942.14596.mb@bu3sch.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org, madwifi-devel@lists.sourceforge.net, lwn@lwn.net Return-path: To: Michael Buesch Content-Disposition: inline In-Reply-To: <200611151942.14596.mb@bu3sch.de> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: madwifi-devel-bounces@lists.sourceforge.net Errors-To: madwifi-devel-bounces@lists.sourceforge.net List-Id: netdev.vger.kernel.org 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@tuxdriver.com ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV