From owner-freebsd-bluetooth@FreeBSD.ORG Wed Jun 22 16:17:46 2011 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 61B811065672 for ; Wed, 22 Jun 2011 16:17:46 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id E12218FC0A for ; Wed, 22 Jun 2011 16:17:40 +0000 (UTC) Received: by bwz12 with SMTP id 12so1307419bwz.13 for ; Wed, 22 Jun 2011 09:17:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=u2Vj3TD5gQoQbQKx1hR1dAzdyVojrjBZZOclCrdQ+Hk=; b=HLwMDszFCNo6Qc3P8gepcBRVrNYks+tW3t1xbUVphBfgPbm35qaJXB+3eB/ZO3/DOD CijZ9fEmzV1H96ifj+59hGXK0zZxN6S6lAbNYffsT7N+YZBGsdqmg337wy1B8jjiS7bb gTCG0XsZ8M1HeLV13Uyss74xQMTpMgfwkn8aQ= 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=eCHxucs7T6gNn5IX1JKINvEwOLINa40dgVrUATM/m/A9Y6xez/8Qq7rc0h5vwY/G+g tSEl3dyWe9VfdorzXFVe1qcfYZX0qUY1hCTUGAWkfmyf32ov45QTE9Zx1qVqitaKXemU V0oq0yuMNKrQnlQO+dbPVxd8C4Qz6Hj+q6Rak= MIME-Version: 1.0 Received: by 10.204.84.24 with SMTP id h24mr28850bkl.185.1308759459103; Wed, 22 Jun 2011 09:17:39 -0700 (PDT) Received: by 10.204.38.10 with HTTP; Wed, 22 Jun 2011 09:17:39 -0700 (PDT) In-Reply-To: References: Date: Wed, 22 Jun 2011 09:17:39 -0700 Message-ID: From: Maksim Yevmenkin To: Brandon Gooch Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-bluetooth@freebsd.org" Subject: Re: Broadcom BCM2046B1 in HCI mode? 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: Wed, 22 Jun 2011 16:17:46 -0000 On Tuesday, June 21, 2011, Brandon Gooch wrot= e: > I have one of these in my notebook: > > uhub4: on usbus0 > > This is a bluetooth device in HID mode, but I'd like to switch it to > HCI mode. I found the following in rc.conf(5): > > =A0 =A0 ubthidhci_enable > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 (bool) If set to ``YES'', change the USB= Bluetooth controller > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 from HID mode to HCI mode. =A0You also n= eed to specify the > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 location of USB Bluetooth controller wit= h the > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 ubthidhci_busnum and ubthidhci_addr vari= ables. > > =A0 =A0 ubthidhci_busnum > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Bus number where the USB Bluetooth contr= oller is located. > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Check the output of usbconfig(8) on your= system to find this > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 information. > > =A0 =A0 ubthidhci_addr > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Bus address of the USB Bluetooth control= ler. =A0Check the out- > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 put of usbconfig(8) on your system to fi= nd this information. > > So I added the appropriate directives to /etc/rc.conf, to no avail: > > ubthidhci_enable=3D"YES" > ubthidhci_busnum=3D"0" > ubthidhci_addr=3D"5" > > This basically calls usbconfig(8) at system start-up in the following way= : > > /usr/sbin/usbconfig -u 0 -a 5 do_request 0x40 0 0 0 0 > /dev/null 2>&1 > > Running this command manually, I see this output: > > REQUEST =3D > > ...which I've read as potentially being OK, as the operation still may > have successfully completed -- it hasn't :( > > So, has anyone had any luck using this rc.conf(5) directive, or does > anyone on this list have a modified usbconfig(8) command that may help > me coax HCI from this device? Switching device between hid and hci modes is s something that is device / manufacturer specific. It could be that this particular device need different request or something like that. I would suggest to look at linux tool called hid2hci. It has support for different devices from different manufacturers. Thanks, Max