From owner-freebsd-bluetooth@FreeBSD.ORG  Tue Nov  2 22:05:18 2010
Return-Path: <owner-freebsd-bluetooth@FreeBSD.ORG>
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 BD3EB1065694
	for <freebsd-bluetooth@freebsd.org>;
	Tue,  2 Nov 2010 22:05:18 +0000 (UTC)
	(envelope-from plunky@rya-online.net)
Received: from mail.ukfsn.org (mail.ukfsn.org [77.75.108.10])
	by mx1.freebsd.org (Postfix) with ESMTP id 58CA48FC12
	for <freebsd-bluetooth@freebsd.org>;
	Tue,  2 Nov 2010 22:05:18 +0000 (UTC)
Received: from localhost (smtp-filter.ukfsn.org [192.168.54.205])
	by mail.ukfsn.org (Postfix) with ESMTP id 43013DEC71;
	Tue,  2 Nov 2010 21:45:06 +0000 (GMT)
Received: from mail.ukfsn.org ([192.168.54.25])
	by localhost (smtp-filter.ukfsn.org [192.168.54.205]) (amavisd-new,
	port 10024)
	with ESMTP id U3rqqp0eRdDW; Tue,  2 Nov 2010 21:45:06 +0000 (GMT)
Received: from galant.ukfsn.org (unknown [89.194.39.203])
	by mail.ukfsn.org (Postfix) with ESMTP id D414DDEC56;
	Tue,  2 Nov 2010 21:45:04 +0000 (GMT)
Received: by galant.ukfsn.org (Postfix, from userid 1000)
	id 11050260261; Tue,  2 Nov 2010 21:44:48 +0000 (GMT)
Date: Tue, 2 Nov 2010 21:44:47 +0000 (GMT)
From: Iain Hibbert <plunky@rya-online.net>
To: Maksim Yevmenkin <maksim.yevmenkin@gmail.com>
In-Reply-To: <AANLkTimRpXA2b_Pw7=fzApAjFb5FWRTPdPYvH-8pSw=m@mail.gmail.com>
Message-ID: <alpine.NEB.2.00.1011022138240.22662@galant.ukfsn.org>
References: <06b90815b84b40625e37317bc16b13ec@ringofsaturn.com>
	<AANLkTi=ObMmqB6TzH3C-N_7m9S56_x78ZczQ+c4aE+KE@mail.gmail.com>
	<8647f55a4e8dcce33036a0810564b9e0@ringofsaturn.com>
	<AANLkTimRpXA2b_Pw7=fzApAjFb5FWRTPdPYvH-8pSw=m@mail.gmail.com>
User-Agent: Alpine 2.00 (NEB 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="0-258416-1288734287=:22662"
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
	<freebsd-bluetooth.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth>, 
	<mailto:freebsd-bluetooth-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bluetooth>
List-Post: <mailto:freebsd-bluetooth@freebsd.org>
List-Help: <mailto:freebsd-bluetooth-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth>, 
	<mailto:freebsd-bluetooth-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Nov 2010 22:05:18 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--0-258416-1288734287=:22662
Content-Type: TEXT/PLAIN; charset=UTF-8
Content-Transfer-Encoding: QUOTED-PRINTABLE

On Tue, 2 Nov 2010, Maksim Yevmenkin wrote:

> > =EF=BB=BFNov  2 16:08:02 tethys root: Unknown USB device: vendor 0x0cf3=
 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 dongl=
e);

3) as this device attaches at ugen(4) already, write a userland program
   that opens the correct endpoint and writes the firmware directly

regards,
iain

(http://homepages.rya-online.net/plunky/bcmfw-1.0.tar.gz does this for the
old broadcom device on NetBSD, perhaps it would be easy to adapt..)
--0-258416-1288734287=:22662--