From owner-freebsd-mobile@FreeBSD.ORG Sat Jul 17 15:44:51 2010 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7558C1065677 for ; Sat, 17 Jul 2010 15:44:51 +0000 (UTC) (envelope-from rpaulo@freebsd.org) Received: from karen.lavabit.com (karen.lavabit.com [72.249.41.33]) by mx1.freebsd.org (Postfix) with ESMTP id 4B40D8FC13 for ; Sat, 17 Jul 2010 15:44:51 +0000 (UTC) Received: from e.earth.lavabit.com (e.earth.lavabit.com [192.168.111.14]) by karen.lavabit.com (Postfix) with ESMTP id 9230F16F482; Sat, 17 Jul 2010 10:44:50 -0500 (CDT) Received: from 10.0.10.3 (54.81.54.77.rev.vodafone.pt [77.54.81.54]) by lavabit.com with ESMTP id S9PSKIEZS1RA; Sat, 17 Jul 2010 10:44:50 -0500 Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: Rui Paulo In-Reply-To: <201007172235.55333.fluffy@freebsd.org> Date: Sat, 17 Jul 2010 16:44:47 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <20AE0461-1CF3-44B2-9E19-3C8851DAC8A4@FreeBSD.org> References: <201007172235.55333.fluffy@freebsd.org> To: Dima Panov X-Mailer: Apple Mail (2.1081) Cc: freebsd-mobile@freebsd.org Subject: Re: Atheros AR3011 Bluetooth X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Jul 2010 15:44:51 -0000 On 17 Jul 2010, at 12:35, Dima Panov wrote: > Hello folks! >=20 > Is there any enthusiast which ported driver for Atheros AR3011 = Bluetooth chipset?=20 > http://www.atheros.com/pt/AR3011.htm >=20 >=20 > [root@Fluffy] ~# usbconfig -d 0.3 dump_device_desc > ugen0.3: at usbus0, cfg=3D0 md=3DHOST = spd=3DFULL (12Mbps) pwr=3DON >=20 > bLength =3D 0x0012=20 > bDescriptorType =3D 0x0001=20 > bcdUSB =3D 0x0110=20 > bDeviceClass =3D 0x00ff=20 > bDeviceSubClass =3D 0x0000=20 > bDeviceProtocol =3D 0x0000=20 > bMaxPacketSize0 =3D 0x0040=20 > idVendor =3D 0x0cf3=20 > idProduct =3D 0x3000=20 > bcdDevice =3D 0x0200=20 > iManufacturer =3D 0x0000 > iProduct =3D 0x0000 > iSerialNumber =3D 0x0000 > bNumConfigurations =3D 0x0001 >=20 >=20 Are you sure a driver is really needed? The hardware might be in HID = mode instead of HCI. Regards, -- Rui Paulo