From owner-freebsd-current@FreeBSD.ORG Thu Jun 21 18:43:26 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 228DD1065686; Thu, 21 Jun 2012 18:43:26 +0000 (UTC) (envelope-from samira.nox@gmail.com) Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 781FB8FC1B; Thu, 21 Jun 2012 18:43:25 +0000 (UTC) Received: by wgbds11 with SMTP id ds11so925681wgb.31 for ; Thu, 21 Jun 2012 11:43:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:to:cc:subject:references:date:mime-version :content-transfer-encoding:from:organization:message-id:in-reply-to :user-agent; bh=QWteNVHU4HvfJcBvelYCyj1k+Ir9gvCk9cfV1yjLMeo=; b=DnADYORckL/Tq825RhlQ8NiBNDGVEnEjfvECq+2AEIkhL2dYZySfAR+RMw0rwOP/xg bnme8jodidf6D06OjrE5oQJMUNW6pC1Hrj2XPjDcZUBpbmORgum74kBkxnV1xcIbH38Z mmZohiOCu8zSZPA+Jqj9UHbXfK9aFH8VdL/oS1xBkH3VuoxpVF7PZ2dN1OATHfmwKGGl iEl700XBw0VH5+BwJ8I06/f30OiOR7bMO0xxU8yvBdROOnSoJJghj/3YdPEDxYi4NE9H ptsh3Idra7DBxgHQXCD5kEk2PyKGmPySXdJbMS8D0p2rWe6zBN8M/9C/VnbC6VvsN2np L3KA== Received: by 10.180.101.103 with SMTP id ff7mr22444988wib.6.1340304204446; Thu, 21 Jun 2012 11:43:24 -0700 (PDT) Received: from noxon (141-119.0-85.cust.bluewin.ch. [85.0.119.141]) by mx.google.com with ESMTPS id fo7sm47254075wib.9.2012.06.21.11.43.23 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 21 Jun 2012 11:43:23 -0700 (PDT) Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: "Adrian Chadd" References: Date: Thu, 21 Jun 2012 20:43:22 +0200 MIME-Version: 1.0 Content-Transfer-Encoding: Quoted-Printable From: sam Organization: - Message-ID: In-Reply-To: User-Agent: Opera Mail/12.01 (FreeBSD) Cc: "freebsd-current@freebsd.org" Subject: Re: Wireless: AzureWave 2100 supported? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jun 2012 18:43:26 -0000 Hi That's a shame. But I look forward to test it, if you get the time, to = work on it. mfg sam Am 20.06.2012, 23:09 Uhr, schrieb Adrian Chadd : > Hi, > > > On 20 June 2012 14:02, sam wrote: > >> or if you prefer pciconf: >> none12@pci0:8:0:0: class=3D0x028000 card=3D0x21001a3b chip=3D0x0= 037168c >> rev=3D0x01 hdr=3D0x00 >> vendor =3D 'Atheros Communications Inc.' >> class =3D network > > 0x168c is Atheros. > > 0x0037 looks like some kind of AR93xx derivative. There's currently no= > support in ath(4) and ath_hal(4) for the AR93xx or later chips. > > I have some rough plans to start supporting that when I get some time > but I'm very short on time right now and I'm mostly trying to focus on= > testing and tidying up the existing driver code before I bring over > AR93xx support. > > Sorry, I can't give you any further help than that. > > > Adrian -- = Erstellt mit Operas revolution=C3=A4rem E-Mail-Modul: http://www.opera.c= om/mail/