From owner-freebsd-bluetooth@FreeBSD.ORG Tue Nov 2 22:35:23 2010 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1E012106564A for ; Tue, 2 Nov 2010 22:35:23 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id C7AFE8FC12 for ; Tue, 2 Nov 2010 22:35:22 +0000 (UTC) Received: by gwj16 with SMTP id 16so291753gwj.13 for ; Tue, 02 Nov 2010 15:35:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=Xp1xhfwyqHRdveh9N++iB2bGqBNc1KqaAq/t1EP6B4Q=; b=ZbBHwfMPkuWkNCd4NalCfBAn+FB5dUHutsWTxEbfYU8q7PeYIxAxuhjocCU7NP+gvd 9JaLf2bQOZaL70hNllEoYhi19wZfvtEYPbXNDVP2GS7WkYPRgxm1/H+RxRlfPpoFlam9 81mCCmsEaQ3EZpToBhYGnqM4soBBms34XiJIQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=hCIw/p3gxOml70l/5NAjqFvHFczY7n4qSZ+1f/dp4XYS3YB+0uPJ7xgKXF9EHH/M4G YXqfO+HVo6Kt22Lof0Ry3bFmdVld837gzTheySggtCP8wEV/no8o2CPFVReMhN2+4HYa kfuvPbrvGG7gsifIu1ZOtduzH30XV8HR/XYBo= MIME-Version: 1.0 Received: by 10.42.117.3 with SMTP id r3mr5677864icq.143.1288737321699; Tue, 02 Nov 2010 15:35:21 -0700 (PDT) Received: by 10.231.191.206 with HTTP; Tue, 2 Nov 2010 15:35:21 -0700 (PDT) In-Reply-To: References: <06b90815b84b40625e37317bc16b13ec@ringofsaturn.com> <8647f55a4e8dcce33036a0810564b9e0@ringofsaturn.com> Date: Tue, 2 Nov 2010 15:35:21 -0700 Message-ID: From: Maksim Yevmenkin To: Iain Hibbert Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-bluetooth@freebsd.org Subject: Re: Troubleshooting a USB Bluetooth Dongle X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Nov 2010 22:35:23 -0000 On Tue, Nov 2, 2010 at 2:44 PM, Iain Hibbert wrote: > On Tue, 2 Nov 2010, Maksim Yevmenkin wrote: > >> > =EF=BB=BFNov 2 16:08:02 tethys root: Unknown USB device: vendor 0x0cf= 3 product >> > 0x3000 bus uhub8 >> > Nov 2 16:08:02 tethys kernel: ugen3.3: at usbus3 >> > >> > Which doesn't give me much. Doing a config dump: >> >> i disagree :) it gives you vendor/device id pair which is >> 0x0cf3/0x3000. in other words, your adapter is based on atheros ar3011 >> chip and will require a special (new) driver that would download >> firmware. ubtbcmfw(4) will not work, because its for broadcom chip. i >> only mentioned this because it would be similar, but not the same :) >> >> [...] >> >> > So, any suggestions on where to go next? >> >> 1) need to write a special ubtathfw(4) driver; >> >> 2) obtain firmware (i assume it would be on a cd that came with the dong= le); > > 3) as this device attaches at ugen(4) already, write a userland program > that opens the correct endpoint and writes the firmware directly yes, i guess we could do that too :) linux driver does not seem to do anything fancy. just sends control request (firmware download), followed by a bunch of bulk requests (4k chunks of firmware). > (http://homepages.rya-online.net/plunky/bcmfw-1.0.tar.gz does this for th= e > old broadcom device on NetBSD, perhaps it would be easy to adapt..) yep thanks, max