From owner-freebsd-stable@FreeBSD.ORG Tue Apr 15 21:08:09 2003 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 586D437B401; Tue, 15 Apr 2003 21:08:09 -0700 (PDT) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 864F243F85; Tue, 15 Apr 2003 21:08:08 -0700 (PDT) (envelope-from sam@errno.com) Received: from melange (melange.errno.com [66.127.85.82]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.9) with ESMTP id h3G47npw095278 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Tue, 15 Apr 2003 21:07:49 -0700 (PDT) (envelope-from sam@errno.com) Message-ID: <0d4701c303cd$c2e5b980$52557f42@errno.com> From: "Sam Leffler" To: , , "M. Warner Losh" References: <200304142204.aa46871@banana.critchley.biz><00ac01c302e0$da5d3fe0$15b55042@vizion2000.net><20030415022050.V2937@znfgre.tberna.bet> <20030415.214600.43408988.imp@bsdimp.com> Date: Tue, 15 Apr 2003 21:07:44 -0700 Organization: Errno Consulting MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4920.2300 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4920.2300 cc: john@critchley.biz cc: freebsd-stable@freebsd.org cc: will@csociety.org Subject: Re: Annother Wireless network card annother problem 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: Wed, 16 Apr 2003 04:08:09 -0000 > In message: <20030415022050.V2937@znfgre.tberna.bet> > Doug Barton writes: > : As for 802.11a, I was told by several people in a position to know that > : it's not going to be available in FreeBSD for "a while." > > There's a talk schedueled for the end of the month to talk about the > Atheros driver.... I am doing the work. I can't promise exactly when the support will be ready but "not for a while" is incorrect. I've tried to keep a low profile to avoid lots of questions. Sam