From owner-freebsd-stable@FreeBSD.ORG Mon Nov 15 18:59:00 2004 Return-Path: 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 2101D16A4CE for ; Mon, 15 Nov 2004 18:59:00 +0000 (GMT) Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2683743D1F for ; Mon, 15 Nov 2004 18:58:59 +0000 (GMT) (envelope-from michael@lyngbol.dk) Received: by freesbee.wheel.dk (Postfix, from userid 1038) id E39B4114CF; Mon, 15 Nov 2004 19:58:57 +0100 (CET) Date: Mon, 15 Nov 2004 19:58:57 +0100 From: Michael =?iso-8859-1?Q?Lyngb=F8l?= To: Sam Leffler Message-ID: <20041115185857.GE2500@freesbee.wheel.dk> Mail-Followup-To: Sam Leffler , John Hay , stable@freebsd.org References: <416DF63E.6000401@errno.com> <20041111055115.GA58987@zibbi.icomtek.csir.co.za> <20041115165342.GD2500@freesbee.wheel.dk> <200411150940.49215.sam@errno.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <200411150940.49215.sam@errno.com> User-Agent: Mutt/1.4.2.1i X-Free: live free, or die! X-Operating-System: FreeBSD/i386 5.2-CURRENT X-PGP-Fingerprint: 3CA6 3789 1455 8FC2 D499 F22A D763 1ABB 9E4A 37AE X-PGP-Public-Key: http://freesbee.wheel.dk/~lyngbol/gpgkey.pub cc: stable@freebsd.org Subject: Re: net80211+atheros changes (updated) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Nov 2004 18:59:00 -0000 On 15.11.2004 09:40:48 +0000, Sam Leffler wrote: [...] > > I'm able to use WEP which was broken before. I'll try TKIP and CCMP > > crypto support. > > > > Any chance of getting these changes committed? > > No. I have stated previously that I will not commit any of these changes to > CVS until at least one other committer agrees to help with the fallout (to > other wireless drivers). In particular I need someone to take responsibility > for the wi driver. Fair enough. Hopefully someone will step forward and help with the other wireless drivers (sorry my skills in C doesn't help much). /Michael -- Michael Lyngbøl -- michael at lyngbol dot dk Network Architect, AS3292 TDC, IP·backbone