From owner-freebsd-stable@FreeBSD.ORG Wed Feb 15 17:34:54 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 563DB16A420 for ; Wed, 15 Feb 2006 17:34:54 +0000 (GMT) (envelope-from fcash@ocis.net) Received: from smtp.sd73.bc.ca (smtp.sd73.bc.ca [142.24.13.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id B003C43D53 for ; Wed, 15 Feb 2006 17:34:51 +0000 (GMT) (envelope-from fcash@ocis.net) Received: from localhost (localhost [127.0.0.1]) by localhost.sd73.bc.ca (Postfix) with ESMTP id 2696A8A0090 for ; Wed, 15 Feb 2006 09:37:20 -0800 (PST) Received: from smtp.sd73.bc.ca ([127.0.0.1]) by localhost (smtp.sd73.bc.ca [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 46954-02-89 for ; Wed, 15 Feb 2006 09:37:13 -0800 (PST) Received: from s10.sbo (s10.sbo [192.168.0.10]) by smtp.sd73.bc.ca (Postfix) with ESMTP id CBDB08A004C for ; Wed, 15 Feb 2006 09:37:13 -0800 (PST) From: Freddie Cash To: freebsd-stable@freebsd.org Date: Wed, 15 Feb 2006 09:34:41 -0800 User-Agent: KMail/1.9.1 References: <200602041808.03062.matt@mattsnetwork.co.uk> <20060215014608.GA9931@nowhere> <43F36564.2020904@errno.com> In-Reply-To: <43F36564.2020904@errno.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200602150934.42556.fcash@ocis.net> X-Virus-Scanned: by amavisd-new using ClamAV at sd73.bc.ca Subject: Re: dhclient in 6.0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Feb 2006 17:34:54 -0000 On Wednesday 15 February 2006 09:31 am, Sam Leffler wrote: > Craig Boston wrote: > > On Sat, Feb 04, 2006 at 10:04:16PM -0800, Kevin Oberman wrote: > I recently made another stab at overhauling wi to better integrate with > net80211. It uses some of Craig's work and some of mine. The results > were fragile. The main problem is what Craig describes: if all you > care about are Intersil parts then you can do it but if wi is to > continue supporting older cards then it's hard. As I've said before I > believe resources are better spent on improving drivers for newer > parts. OTOH if someone really and truly wants to do this I have a > number of cards I can loan. Completely naive, non-developer question: would it be possible to split the wi(4) driver into two drivers? One to support all the ancient, pre-802.11 cards, and one to support all the nice, new cards? -- Freddie Cash fcash@ocis.net