From owner-freebsd-bluetooth@FreeBSD.ORG Sun Jun 12 07:02:39 2011 Return-Path: Delivered-To: bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 452E9106566C for ; Sun, 12 Jun 2011 07:02:39 +0000 (UTC) (envelope-from freebsd-bluetooth@herveybayaustralia.com.au) Received: from mail.unitedinsong.com.au (mail.unitedinsong.com.au [150.101.178.33]) by mx1.freebsd.org (Postfix) with ESMTP id EA2CF8FC16 for ; Sun, 12 Jun 2011 07:02:35 +0000 (UTC) Received: from laptop1.herveybayaustralia.com.au (laptop1.herveybayaustralia.com.au [192.168.0.186]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.unitedinsong.com.au (Postfix) with ESMTPS id 99C7E5C22 for ; Sun, 12 Jun 2011 16:52:22 +1000 (EST) Message-ID: <4DF46049.6080206@herveybayaustralia.com.au> Date: Sun, 12 Jun 2011 16:44:25 +1000 From: Da Rock User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.16) Gecko/20110204 Thunderbird/3.0.11 ThunderBrowse/3.3.4 MIME-Version: 1.0 To: bluetooth@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Asus bluetooth device - 0x1712 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: Sun, 12 Jun 2011 07:02:39 -0000 Trying to get this device to work on my laptop (after some time of neglect - I've had no use or time to look into it as yet), but none of the drivers seem to be working. I've even tried the atheros driver by Rusty which doesn't appear to be the same device anyway. Under usbconfig I get: on usbus5 Any ideas? Also, what is the state of bluetooth 2.x? Everything I've read has only mentioned 1.1. Cheers From owner-freebsd-bluetooth@FreeBSD.ORG Sun Jun 12 07:54:41 2011 Return-Path: Delivered-To: bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D305B106564A for ; Sun, 12 Jun 2011 07:54:41 +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 958818FC0A for ; Sun, 12 Jun 2011 07:54:41 +0000 (UTC) Received: from localhost (smtp-filter.ukfsn.org [192.168.54.205]) by mail.ukfsn.org (Postfix) with ESMTP id 7F4DDDEC1E; Sun, 12 Jun 2011 08:29:53 +0100 (BST) 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 M1hiTynlpr4t; Sun, 12 Jun 2011 08:29:53 +0100 (BST) Received: from galant.ukfsn.org (unknown [89.195.67.156]) by mail.ukfsn.org (Postfix) with ESMTP id 49597DEBF6; Sun, 12 Jun 2011 08:29:52 +0100 (BST) Received: by galant.ukfsn.org (Postfix, from userid 1000) id 72F2A2600AC; Sun, 12 Jun 2011 08:30:26 +0100 (BST) Date: Sun, 12 Jun 2011 08:30:26 +0100 (BST) From: Iain Hibbert To: Da Rock In-Reply-To: <4DF46049.6080206@herveybayaustralia.com.au> Message-ID: References: <4DF46049.6080206@herveybayaustralia.com.au> User-Agent: Alpine 2.00 (NEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: bluetooth@freebsd.org Subject: Re: Asus bluetooth device - 0x1712 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: Sun, 12 Jun 2011 07:54:41 -0000 On Sun, 12 Jun 2011, Da Rock wrote: > Trying to get this device to work on my laptop (after some time of neglect - > I've had no use or time to look into it as yet), but none of the drivers seem > to be working. I've even tried the atheros driver by Rusty which doesn't > appear to be the same device anyway. > > Under usbconfig I get: > on usbus5 > > Any ideas? class 224/1 is wireless/rf, is there a way to check the device protocol? it should be 1 (bluetooth) for the ubt driver to match.. > Also, what is the state of bluetooth 2.x? Everything I've read has only > mentioned 1.1. 4.0, 3.0 & 2.x spec are all mostly backwards compatible (there are very few deprecations) and the FreeBSD stack should continue to work on all modern devices, albeit without advanced features.. iain From owner-freebsd-bluetooth@FreeBSD.ORG Sun Jun 12 22:13:56 2011 Return-Path: Delivered-To: bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 31296106566C for ; Sun, 12 Jun 2011 22:13:56 +0000 (UTC) (envelope-from freebsd-bluetooth@herveybayaustralia.com.au) Received: from mail.unitedinsong.com.au (mail.unitedinsong.com.au [150.101.178.33]) by mx1.freebsd.org (Postfix) with ESMTP id D6B398FC23 for ; Sun, 12 Jun 2011 22:13:55 +0000 (UTC) Received: from laptop1.herveybayaustralia.com.au (laptop1.herveybayaustralia.com.au [192.168.0.186]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.unitedinsong.com.au (Postfix) with ESMTPS id E2A4F5C22; Mon, 13 Jun 2011 08:23:05 +1000 (EST) Message-ID: <4DF53A6F.9080701@herveybayaustralia.com.au> Date: Mon, 13 Jun 2011 08:15:11 +1000 From: Da Rock User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.16) Gecko/20110204 Thunderbird/3.0.11 ThunderBrowse/3.3.4 MIME-Version: 1.0 To: Iain Hibbert References: <4DF46049.6080206@herveybayaustralia.com.au> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: bluetooth@freebsd.org Subject: Re: Asus bluetooth device - 0x1712 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: Sun, 12 Jun 2011 22:13:56 -0000 On 06/12/11 17:30, Iain Hibbert wrote: > On Sun, 12 Jun 2011, Da Rock wrote: > > >> Trying to get this device to work on my laptop (after some time of neglect - >> I've had no use or time to look into it as yet), but none of the drivers seem >> to be working. I've even tried the atheros driver by Rusty which doesn't >> appear to be the same device anyway. >> >> Under usbconfig I get: >> on usbus5 >> >> Any ideas? >> > class 224/1 is wireless/rf, is there a way to check the device protocol? > it should be 1 (bluetooth) for the ubt driver to match.. > How do I find that out? Isn't it the rev number there? Or do I need to run a command to find that out? I can't physically look at the device as its built into the laptop board. > >> Also, what is the state of bluetooth 2.x? Everything I've read has only >> mentioned 1.1. >> > 4.0, 3.0& 2.x spec are all mostly backwards compatible (there are very > few deprecations) and the FreeBSD stack should continue to work on all > modern devices, albeit without advanced features.. > Ok, I get that people are busy working on other (possibly) more important things, but what is required to get the advanced features working? Where can I find out the current status of these projects and how to help? I'm currently learning about this technology (I know, late bloomer and all... :) ) and its various features- which are why I'm looking carefully at it now for my current needs. Unfortunately its the advanced features which I really need :( So if I can help advance things I will. Cheers From owner-freebsd-bluetooth@FreeBSD.ORG Mon Jun 13 06:48:11 2011 Return-Path: Delivered-To: bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 10586106564A for ; Mon, 13 Jun 2011 06:48:11 +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 A1A328FC08 for ; Mon, 13 Jun 2011 06:48:10 +0000 (UTC) Received: from localhost (smtp-filter.ukfsn.org [192.168.54.205]) by mail.ukfsn.org (Postfix) with ESMTP id 4E43CDEBFE; Mon, 13 Jun 2011 07:48:07 +0100 (BST) 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 BW15bFVWdqom; Mon, 13 Jun 2011 07:48:07 +0100 (BST) Received: from galant.ukfsn.org (unknown [89.195.67.156]) by mail.ukfsn.org (Postfix) with ESMTP id 26979DEB9D; Mon, 13 Jun 2011 07:48:05 +0100 (BST) Received: by galant.ukfsn.org (Postfix, from userid 1000) id 08F3F2600AC; Mon, 13 Jun 2011 07:48:30 +0100 (BST) Date: Mon, 13 Jun 2011 07:48:29 +0100 (BST) From: Iain Hibbert To: Da Rock In-Reply-To: <4DF53A6F.9080701@herveybayaustralia.com.au> Message-ID: References: <4DF46049.6080206@herveybayaustralia.com.au> <4DF53A6F.9080701@herveybayaustralia.com.au> User-Agent: Alpine 2.00 (NEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: bluetooth@freebsd.org Subject: Re: Asus bluetooth device - 0x1712 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: Mon, 13 Jun 2011 06:48:11 -0000 On Mon, 13 Jun 2011, Da Rock wrote: > On 06/12/11 17:30, Iain Hibbert wrote: > > On Sun, 12 Jun 2011, Da Rock wrote: > > > Trying to get this device to work on my laptop (after some time of neglect > > > - > > > I've had no use or time to look into it as yet), but none of the drivers > > > seem > > > to be working. I've even tried the atheros driver by Rusty which doesn't > > > appear to be the same device anyway. > > > > > > Under usbconfig I get: > > > on > > > usbus5 > > > > > > Any ideas? > > > > class 224/1 is wireless/rf, is there a way to check the device protocol? > > it should be 1 (bluetooth) for the ubt driver to match.. > > How do I find that out? Isn't it the rev number there? Or do I need to run a > command to find that out? I can't physically look at the device as its built > into the laptop board. No, the rev number is the USB device rev number and AFAIK has no relevance to anything.. usbconfig(8) manpage seems to be a bit sparse, you might have to check the source for tips as to what it can print out.. if the device is built in, is there some way of disabling it? (my laptop has a disable wireless switch, and also a disable bluetooth method.. mind you, both of them cause the usb device to disappear entirely) > > > Also, what is the state of bluetooth 2.x? Everything I've read has only > > > mentioned 1.1. > > > > 4.0, 3.0& 2.x spec are all mostly backwards compatible (there are very > > few deprecations) and the FreeBSD stack should continue to work on all > > modern devices, albeit without advanced features.. > > > Ok, I get that people are busy working on other (possibly) more important > things, but what is required to get the advanced features working? Where can I > find out the current status of these projects and how to help? here :) > I'm currently learning about this technology (I know, late bloomer and all... > :) ) and its various features- which are why I'm looking carefully at it now > for my current needs. Unfortunately its the advanced features which I really > need :( So if I can help advance things I will. what advanced features do you need? iain (btw I am not a FreeBSD person, I come from NetBSD but I congregate here because us BSD guys got to stick together sometimes :) From owner-freebsd-bluetooth@FreeBSD.ORG Mon Jun 13 19:51:32 2011 Return-Path: Delivered-To: bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AA20F106566C for ; Mon, 13 Jun 2011 19:51:32 +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 31E478FC0A for ; Mon, 13 Jun 2011 19:51:31 +0000 (UTC) Received: by bwz12 with SMTP id 12so5909062bwz.13 for ; Mon, 13 Jun 2011 12:51:31 -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; bh=fh3sZkhCR5QykjqBpbyPMT9GjxdihcvbMVXLALzH/kw=; b=va0wDci8ACXgwZtMJZszNdycq2/h3iY0rsMirQPdLGMTbBLWYJW+oMHJg5wAB7ipya NwHKmWvYXAeyhi6egu8/eSwlGTzv4A8BxGBKyC2yfah63XMaj2YWfU866nfJLjgomOGH pXzvf6N4tsuNqtAn09xj7xaXsBPzvX5k4KmME= 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; b=fslu/a0k2VKRukCpgdPB5HjuEMpJawXHfK6MCDiCkMpLY4UfitFs+U/EyMovSLJpmH IzeS4OsF8HfkUHVs2dJE67oNh2KWTB6X8pd4/x8bvKK8DCyk6iNuDYyBStQpnGnk0Gb1 YTHiQRblHO1nMxiQq8RES7So83KTG7ypVQ3QM= MIME-Version: 1.0 Received: by 10.204.172.66 with SMTP id k2mr2041106bkz.125.1307993272026; Mon, 13 Jun 2011 12:27:52 -0700 (PDT) Received: by 10.204.36.12 with HTTP; Mon, 13 Jun 2011 12:27:51 -0700 (PDT) In-Reply-To: References: <4DF46049.6080206@herveybayaustralia.com.au> <4DF53A6F.9080701@herveybayaustralia.com.au> Date: Mon, 13 Jun 2011 12:27:51 -0700 Message-ID: From: Maksim Yevmenkin To: Da Rock Content-Type: text/plain; charset=ISO-8859-1 Cc: bluetooth@freebsd.org Subject: Re: Asus bluetooth device - 0x1712 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: Mon, 13 Jun 2011 19:51:32 -0000 On Sun, Jun 12, 2011 at 11:48 PM, Iain Hibbert wrote: > On Mon, 13 Jun 2011, Da Rock wrote: > >> On 06/12/11 17:30, Iain Hibbert wrote: >> > On Sun, 12 Jun 2011, Da Rock wrote: >> > > Trying to get this device to work on my laptop (after some time of neglect >> > > - >> > > I've had no use or time to look into it as yet), but none of the drivers >> > > seem >> > > to be working. I've even tried the atheros driver by Rusty which doesn't >> > > appear to be the same device anyway. >> > > >> > > Under usbconfig I get: >> > > on >> > > usbus5 >> > > >> > > Any ideas? >> > >> > class 224/1 is wireless/rf, is there a way to check the device protocol? >> > it should be 1 (bluetooth) for the ubt driver to match.. >> >> How do I find that out? Isn't it the rev number there? Or do I need to run a >> command to find that out? I can't physically look at the device as its built >> into the laptop board. > > No, the rev number is the USB device rev number and AFAIK has no relevance > to anything.. > > usbconfig(8) manpage seems to be a bit sparse, you might have to check the > source for tips as to what it can print out.. > > if the device is built in, is there some way of disabling it? (my laptop > has a disable wireless switch, and also a disable bluetooth method.. mind > you, both of them cause the usb device to disappear entirely) first, question: did you load ng_ubt(4) driver? if you did and device is still not recognized, could you please dump device descriptor, i.e. use usbconfig(8) dump_device_desc command >> > > Also, what is the state of bluetooth 2.x? Everything I've read has only >> > > mentioned 1.1. >> > >> > 4.0, 3.0& 2.x spec are all mostly backwards compatible (there are very >> > few deprecations) and the FreeBSD stack should continue to work on all >> > modern devices, albeit without advanced features.. >> > >> Ok, I get that people are busy working on other (possibly) more important >> things, but what is required to get the advanced features working? Where can I >> find out the current status of these projects and how to help? > > here :) > >> I'm currently learning about this technology (I know, late bloomer and all... >> :) ) and its various features- which are why I'm looking carefully at it now >> for my current needs. Unfortunately its the advanced features which I really >> need :( So if I can help advance things I will. > > what advanced features do you need? thanks, Iain :) max From owner-freebsd-bluetooth@FreeBSD.ORG Tue Jun 14 06:53:58 2011 Return-Path: Delivered-To: bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0412B106566C for ; Tue, 14 Jun 2011 06:53:58 +0000 (UTC) (envelope-from freebsd-bluetooth@herveybayaustralia.com.au) Received: from mail.unitedinsong.com.au (mail.unitedinsong.com.au [150.101.178.33]) by mx1.freebsd.org (Postfix) with ESMTP id 7D5B78FC12 for ; Tue, 14 Jun 2011 06:53:57 +0000 (UTC) Received: from laptop1.herveybayaustralia.com.au (laptop1.herveybayaustralia.com.au [192.168.0.186]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.unitedinsong.com.au (Postfix) with ESMTPS id 3AFB15C24; Tue, 14 Jun 2011 17:03:07 +1000 (EST) Message-ID: <4DF705C9.7020606@herveybayaustralia.com.au> Date: Tue, 14 Jun 2011 16:55:05 +1000 From: Da Rock User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.16) Gecko/20110204 Thunderbird/3.0.11 ThunderBrowse/3.3.4 MIME-Version: 1.0 To: Maksim Yevmenkin References: <4DF46049.6080206@herveybayaustralia.com.au> <4DF53A6F.9080701@herveybayaustralia.com.au> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: bluetooth@freebsd.org Subject: Re: Asus bluetooth device - 0x1712 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, 14 Jun 2011 06:53:58 -0000 On 06/14/11 05:27, Maksim Yevmenkin wrote: > On Sun, Jun 12, 2011 at 11:48 PM, Iain Hibbert wrote: > >> On Mon, 13 Jun 2011, Da Rock wrote: >> >> >>> On 06/12/11 17:30, Iain Hibbert wrote: >>> >>>> On Sun, 12 Jun 2011, Da Rock wrote: >>>> >>>>> Trying to get this device to work on my laptop (after some time of neglect >>>>> - >>>>> I've had no use or time to look into it as yet), but none of the drivers >>>>> seem >>>>> to be working. I've even tried the atheros driver by Rusty which doesn't >>>>> appear to be the same device anyway. >>>>> >>>>> Under usbconfig I get: >>>>> on >>>>> usbus5 >>>>> >>>>> Any ideas? >>>>> >>>> class 224/1 is wireless/rf, is there a way to check the device protocol? >>>> it should be 1 (bluetooth) for the ubt driver to match.. >>>> >>> How do I find that out? Isn't it the rev number there? Or do I need to run a >>> command to find that out? I can't physically look at the device as its built >>> into the laptop board. >>> >> No, the rev number is the USB device rev number and AFAIK has no relevance >> to anything.. >> >> usbconfig(8) manpage seems to be a bit sparse, you might have to check the >> source for tips as to what it can print out.. >> >> if the device is built in, is there some way of disabling it? (my laptop >> has a disable wireless switch, and also a disable bluetooth method.. mind >> you, both of them cause the usb device to disappear entirely) >> No. Its builtin and the only switch is for the wifi. > first, question: did you load ng_ubt(4) driver? > Naturally. Its in the handbook, and you never discount the handbook :) > if you did and device is still not recognized, could you please dump > device descriptor, i.e. use usbconfig(8) dump_device_desc command > ugen5.2: at usbus5, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x00e0 bDeviceSubClass = 0x0001 bDeviceProtocol = 0x0001 bMaxPacketSize0 = 0x0040 idVendor = 0x0b05 idProduct = 0x1712 bcdDevice = 0x1915 iManufacturer = 0x0000 iProduct = 0x0000 iSerialNumber = 0x0003 <0194E8-5B-0002> bNumConfigurations = 0x0001 > >>>>> Also, what is the state of bluetooth 2.x? Everything I've read has only >>>>> mentioned 1.1. >>>>> >>>> 4.0, 3.0& 2.x spec are all mostly backwards compatible (there are very >>>> few deprecations) and the FreeBSD stack should continue to work on all >>>> modern devices, albeit without advanced features.. >>>> >>>> >>> Ok, I get that people are busy working on other (possibly) more important >>> things, but what is required to get the advanced features working? Where can I >>> find out the current status of these projects and how to help? >>> >> here :) >> Good to know. I've been following the list for a while, just not actively. I thought there might be project pages or something to read... >> >>> I'm currently learning about this technology (I know, late bloomer and all... >>> :) ) and its various features- which are why I'm looking carefully at it now >>> for my current needs. Unfortunately its the advanced features which I really >>> need :( So if I can help advance things I will. >>> >> what advanced features do you need? >> I'm a little new to jargon, but the features are stereo audio, better bitrates, remote control, phone control, etc (HSP, EDR, AV-something or rather I think at least). Basically all the cool media stuff available now that wasn't around with 1.x. Thats what has grabbed my interest now anyway, file transfer, dun... meh- I can do that with wifi. > thanks, Iain :) > Iain, as to your previous post I thought I had recognized your name on the list of other BSD flavours... :) > max > Thanks Max. What now? Can I add the product ID to the ng_ubt driver and it just work? If so, any chance you could clarify the right way to do that- I'm still a little green with coding for BSD :) (and once I have done that and it works I'll swing it by you to check it out and commit even if you don't mind). Cheers From owner-freebsd-bluetooth@FreeBSD.ORG Tue Jun 14 20:17:37 2011 Return-Path: Delivered-To: bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 93002106566C for ; Tue, 14 Jun 2011 20:17:37 +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 2A3C48FC0A for ; Tue, 14 Jun 2011 20:17:36 +0000 (UTC) Received: from localhost (smtp-filter.ukfsn.org [192.168.54.205]) by mail.ukfsn.org (Postfix) with ESMTP id CF47BDEC43; Tue, 14 Jun 2011 21:17:33 +0100 (BST) 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 RWkd7Gz2qKWl; Tue, 14 Jun 2011 21:17:33 +0100 (BST) Received: from galant.ukfsn.org (unknown [89.242.155.49]) by mail.ukfsn.org (Postfix) with ESMTP id 821ECDEBBD; Tue, 14 Jun 2011 21:17:33 +0100 (BST) Received: by galant.ukfsn.org (Postfix, from userid 1000) id 683432600AE; Tue, 14 Jun 2011 21:17:33 +0100 (BST) Date: Tue, 14 Jun 2011 21:17:33 +0100 (BST) From: Iain Hibbert To: Da Rock In-Reply-To: <4DF705C9.7020606@herveybayaustralia.com.au> Message-ID: References: <4DF46049.6080206@herveybayaustralia.com.au> <4DF53A6F.9080701@herveybayaustralia.com.au> <4DF705C9.7020606@herveybayaustralia.com.au> User-Agent: Alpine 2.00 (NEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: bluetooth@freebsd.org Subject: Re: Asus bluetooth device - 0x1712 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, 14 Jun 2011 20:17:37 -0000 On Tue, 14 Jun 2011, Da Rock wrote: > > first, question: did you load ng_ubt(4) driver? > > > Naturally. Its in the handbook, and you never discount the handbook :) > > if you did and device is still not recognized, could you please dump > > device descriptor, i.e. use usbconfig(8) dump_device_desc command > > > ugen5.2: at usbus5, cfg=0 md=HOST spd=FULL > (12Mbps) pwr=ON > > bDeviceClass = 0x00e0 > bDeviceSubClass = 0x0001 > bDeviceProtocol = 0x0001 seems like the ng_ubt driver should attach to this directly.. > > > > I'm currently learning about this technology (I know, late bloomer > > > > and all... :) ) and its various features- which are why I'm > > > > looking carefully at it now for my current needs. Unfortunately > > > > its the advanced features which I really need :( So if I can help > > > > advance things I will. > > > > > > > what advanced features do you need? > > > > I'm a little new to jargon, but the features are stereo audio, better > bitrates, remote control, phone control, etc (HSP, EDR, AV-something or rather > I think at least). Basically all the cool media stuff available now that > wasn't around with 1.x. Thats what has grabbed my interest now anyway, file > transfer, dun... meh- I can do that with wifi. better bitrates should be supported natively (not sure about the 3.0 HS speeds, perhaps that requires extra work?) and the parts that would not be supported from the top of my head would be "Secure Simple Pairing" and reliable L2CAP channels, most of the rest is just operating over normal L2CAP/RFCOMM sockets anyway.. the Advanced Audio I have wanted to do for some time as an audio daemon but never got around to starting (not sure actually, how complex it will be - for FreeBSD it would require something like the NetBSD pad(4) driver to be added also).. the Heaset will actually use SCO sockets for audio, which I think FreeBSD does support and there is some code in NetBSD that handles it (via a special kernel audio device, but it should be converted to use pad(4)). Similarly for Handsfree (there is a bthfp program that I wrote, basically a proof-of-concept rather than being greatly useful) not sure how the AV?TP profiles/protocols work, I don't think they are all that complex, it might be that they can represent as a HID profile or if it needs to be tied somewhat into a media player software. It does sound interesting, but I rarely use media from my computer and have never found a need.. I was actually looking at a Bluetooth capable printer (HP 470) on ebay the other day, because I'm sick of using a BJ10 and I hate wires, though the price seemed a little out of my range.. btw all the specifications are available from www.bluetooth.com :) iain From owner-freebsd-bluetooth@FreeBSD.ORG Tue Jun 14 23:38:27 2011 Return-Path: Delivered-To: bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BF928106564A for ; Tue, 14 Jun 2011 23:38:27 +0000 (UTC) (envelope-from freebsd-bluetooth@herveybayaustralia.com.au) Received: from mail.unitedinsong.com.au (mail.unitedinsong.com.au [150.101.178.33]) by mx1.freebsd.org (Postfix) with ESMTP id 2FA9F8FC13 for ; Tue, 14 Jun 2011 23:38:26 +0000 (UTC) Received: from laptop1.herveybayaustralia.com.au (laptop1.herveybayaustralia.com.au [192.168.0.186]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.unitedinsong.com.au (Postfix) with ESMTPS id 303F15C22; Wed, 15 Jun 2011 09:47:38 +1000 (EST) Message-ID: <4DF7F13C.6090208@herveybayaustralia.com.au> Date: Wed, 15 Jun 2011 09:39:40 +1000 From: Da Rock User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.16) Gecko/20110204 Thunderbird/3.0.11 ThunderBrowse/3.3.4 MIME-Version: 1.0 To: Iain Hibbert References: <4DF46049.6080206@herveybayaustralia.com.au> <4DF53A6F.9080701@herveybayaustralia.com.au> <4DF705C9.7020606@herveybayaustralia.com.au> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: bluetooth@freebsd.org Subject: Re: Asus bluetooth device - 0x1712 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, 14 Jun 2011 23:38:27 -0000 On 06/15/11 06:17, Iain Hibbert wrote: > On Tue, 14 Jun 2011, Da Rock wrote: > > >>> first, question: did you load ng_ubt(4) driver? >>> >>> >> Naturally. Its in the handbook, and you never discount the handbook :) >> >>> if you did and device is still not recognized, could you please dump >>> device descriptor, i.e. use usbconfig(8) dump_device_desc command >>> >>> >> ugen5.2: at usbus5, cfg=0 md=HOST spd=FULL >> (12Mbps) pwr=ON >> >> bDeviceClass = 0x00e0 >> bDeviceSubClass = 0x0001 >> bDeviceProtocol = 0x0001 >> > seems like the ng_ubt driver should attach to this directly.. > Probably would if it recognised the product then. What is the correct way to do this then? I know about usbdevs, and the awk script to run, but does anything then need to be added to the driver to pick it up, or should that be all thats needed? > >>>>> I'm currently learning about this technology (I know, late bloomer >>>>> and all... :) ) and its various features- which are why I'm >>>>> looking carefully at it now for my current needs. Unfortunately >>>>> its the advanced features which I really need :( So if I can help >>>>> advance things I will. >>>>> >>>>> >>>> what advanced features do you need? >>>> >>>> >> I'm a little new to jargon, but the features are stereo audio, better >> bitrates, remote control, phone control, etc (HSP, EDR, AV-something or rather >> I think at least). Basically all the cool media stuff available now that >> wasn't around with 1.x. Thats what has grabbed my interest now anyway, file >> transfer, dun... meh- I can do that with wifi. >> > better bitrates should be supported natively (not sure about the 3.0 HS > speeds, perhaps that requires extra work?) and the parts that would not be > supported from the top of my head would be "Secure Simple Pairing" and > reliable L2CAP channels, most of the rest is just operating over > normal L2CAP/RFCOMM sockets anyway.. > > the Advanced Audio I have wanted to do for some time as an audio daemon > but never got around to starting (not sure actually, how complex it will > be - for FreeBSD it would require something like the NetBSD pad(4) driver > to be added also).. the Heaset will actually use SCO sockets for audio, > which I think FreeBSD does support and there is some code in NetBSD that > handles it (via a special kernel audio device, but it should be converted > to use pad(4)). Similarly for Handsfree (there is a bthfp program that I > wrote, basically a proof-of-concept rather than being greatly useful) > > not sure how the AV?TP profiles/protocols work, I don't think they are all > that complex, it might be that they can represent as a HID profile or if > it needs to be tied somewhat into a media player software. It does sound > interesting, but I rarely use media from my computer and have never found > a need.. > I'll have a look at all that then, the media control is a HID profile btw(found that by accident looking into a IR remote and HID keyboard oddly enough). > I was actually looking at a Bluetooth capable printer (HP 470) on ebay the > other day, because I'm sick of using a BJ10 and I hate wires, though the > price seemed a little out of my range.. > > btw all the specifications are available from www.bluetooth.com :) > Thanks Iain, I'll check it out :) > iain > From owner-freebsd-bluetooth@FreeBSD.ORG Tue Jun 14 23:47:25 2011 Return-Path: Delivered-To: bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 774AC1065675 for ; Tue, 14 Jun 2011 23:47:25 +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 F18998FC15 for ; Tue, 14 Jun 2011 23:47:24 +0000 (UTC) Received: by bwz12 with SMTP id 12so84462bwz.13 for ; Tue, 14 Jun 2011 16:47:23 -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=OPX2lxMgHJXXYc/lTK2KBSCCKFBCjJ88d8d8evgLoyc=; b=Al2kzEXo+00sO2ni1/mFuVqvzfHi8jwcn1FLQMJLGnCoc+V8ALdhIiu1Y3r9O3azgk sSIkJYWgVboa9zn2GEXj+DmhY0heKOXM2RPZgknYVb4zPiT/XWPBAI1PFD38VlIfN2O+ xxQT/WQu5vRxic5svad2b8zVH3sOx+iuXrGFM= 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=mIpt1CzM/+tMjqJ8pM8+tGUPWxntg0liwzqzzi0gSXguNXQCnYxGn+Ze+62SIiy1Qf uQsSyJ08kj7ZATn+HoEKeNF1V3zQbQc78R7Zi/COT1AFSgqLDNo2P/HY/aKew2hpp+Bm wtfO2U0/CbFYLjVKG2fz/eIAsOlQ3kqgIsc0s= MIME-Version: 1.0 Received: by 10.204.172.66 with SMTP id k2mr2596803bkz.125.1308095243663; Tue, 14 Jun 2011 16:47:23 -0700 (PDT) Received: by 10.204.36.12 with HTTP; Tue, 14 Jun 2011 16:47:23 -0700 (PDT) In-Reply-To: <4DF7F13C.6090208@herveybayaustralia.com.au> References: <4DF46049.6080206@herveybayaustralia.com.au> <4DF53A6F.9080701@herveybayaustralia.com.au> <4DF705C9.7020606@herveybayaustralia.com.au> <4DF7F13C.6090208@herveybayaustralia.com.au> Date: Tue, 14 Jun 2011 16:47:23 -0700 Message-ID: From: Maksim Yevmenkin To: Da Rock Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: bluetooth@freebsd.org Subject: Re: Asus bluetooth device - 0x1712 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, 14 Jun 2011 23:47:25 -0000 On Tue, Jun 14, 2011 at 4:39 PM, Da Rock wrote: > On 06/15/11 06:17, Iain Hibbert wrote: >> >> On Tue, 14 Jun 2011, Da Rock wrote: >> >> >>>> >>>> first, question: did you load ng_ubt(4) driver? >>>> >>>> >>> >>> Naturally. Its in the handbook, and you never discount the handbook :) >>> >>>> >>>> if you did =A0and device is still not recognized, could you please dum= p >>>> device descriptor, i.e. use usbconfig(8) dump_device_desc command >>>> >>>> >>> >>> ugen5.2: =A0at usbus5, cfg=3D0 md=3DHOST = spd=3DFULL >>> (12Mbps) pwr=3DON >>> >>> =A0 bDeviceClass =3D 0x00e0 >>> =A0 bDeviceSubClass =3D 0x0001 >>> =A0 bDeviceProtocol =3D 0x0001 >>> >> >> seems like the ng_ubt driver should attach to this directly.. >> > > Probably would if it recognised the product then. What is the correct way= to > do this then? I know about usbdevs, and the awk script to run, but does > anything then need to be added to the driver to pick it up, or should tha= t > be all thats needed? it does not look at the product. it looks at interface class, subclass and protocol. are you sure you are loading ng_ubt(4) from loader.conf? are there any error messages from ng_ubt(4) in /var/log/messages? >> >> >>>>>> >>>>>> I'm currently learning about this technology (I know, late bloomer >>>>>> and all... :) ) and its various features- which are why I'm >>>>>> looking carefully at it now for my current needs. Unfortunately >>>>>> its the advanced features which I really need :( So if I can help >>>>>> advance things I will. >>>>>> >>>>>> >>>>> >>>>> what advanced features do you need? >>>>> >>>>> >>> >>> I'm a little new to jargon, but the features are stereo audio, better >>> bitrates, remote control, phone control, etc (HSP, EDR, AV-something or >>> rather >>> I think at least). Basically all the cool media stuff available now tha= t >>> wasn't around with 1.x. Thats what has grabbed my interest now anyway, >>> file >>> transfer, dun... meh- I can do that with wifi. >>> >> >> better bitrates should be supported natively (not sure about the 3.0 HS >> speeds, perhaps that requires extra work?) and the parts that would not = be >> supported from the top of my head would be "Secure Simple Pairing" and >> reliable L2CAP channels, most of the rest is just operating over >> normal L2CAP/RFCOMM sockets anyway.. >> >> the Advanced Audio I have wanted to do for some time as an audio daemon >> but never got around to starting (not sure actually, how complex it will >> be - for FreeBSD it would require something like the NetBSD pad(4) drive= r >> to be added also).. the Heaset will actually use SCO sockets for audio, >> which I think FreeBSD does support and there is some code in NetBSD that >> handles it (via a special kernel audio device, but it should be converte= d >> to use pad(4)). Similarly for Handsfree (there is a bthfp program that I >> wrote, basically a proof-of-concept rather than being greatly useful) >> >> not sure how the AV?TP profiles/protocols work, I don't think they are a= ll >> that complex, it might be that they can represent as a HID profile or if >> it needs to be tied somewhat into a media player software. It does sound >> interesting, but I rarely use media from my computer and have never foun= d >> a need.. >> > > I'll have a look at all that then, the media control is a HID profile > btw(found that by accident looking into a IR remote and HID keyboard oddl= y > enough). >> >> I was actually looking at a Bluetooth capable printer (HP 470) on ebay t= he >> other day, because I'm sick of using a BJ10 and I hate wires, though the >> price seemed a little out of my range.. >> >> btw all the specifications are available from www.bluetooth.com :) >> > > Thanks Iain, I'll check it out :) >> >> iain >> > > _______________________________________________ > freebsd-bluetooth@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth > To unsubscribe, send any mail to "freebsd-bluetooth-unsubscribe@freebsd.o= rg" > From owner-freebsd-bluetooth@FreeBSD.ORG Wed Jun 15 05:27:30 2011 Return-Path: Delivered-To: bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C628A106564A for ; Wed, 15 Jun 2011 05:27:30 +0000 (UTC) (envelope-from freebsd-bluetooth@herveybayaustralia.com.au) Received: from mail.unitedinsong.com.au (mail.unitedinsong.com.au [150.101.178.33]) by mx1.freebsd.org (Postfix) with ESMTP id 4A34B8FC0C for ; Wed, 15 Jun 2011 05:27:29 +0000 (UTC) Received: from laptop1.herveybayaustralia.com.au (laptop1.herveybayaustralia.com.au [192.168.0.186]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.unitedinsong.com.au (Postfix) with ESMTPS id 24A9C5C22; Wed, 15 Jun 2011 15:36:41 +1000 (EST) Message-ID: <4DF8430C.3010104@herveybayaustralia.com.au> Date: Wed, 15 Jun 2011 15:28:44 +1000 From: Da Rock User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.16) Gecko/20110204 Thunderbird/3.0.11 ThunderBrowse/3.3.4 MIME-Version: 1.0 To: Maksim Yevmenkin References: <4DF46049.6080206@herveybayaustralia.com.au> <4DF53A6F.9080701@herveybayaustralia.com.au> <4DF705C9.7020606@herveybayaustralia.com.au> <4DF7F13C.6090208@herveybayaustralia.com.au> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: bluetooth@freebsd.org Subject: Re: Asus bluetooth device - 0x1712 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, 15 Jun 2011 05:27:30 -0000 On 06/15/11 09:47, Maksim Yevmenkin wrote: > On Tue, Jun 14, 2011 at 4:39 PM, Da Rock > wrote: > >> On 06/15/11 06:17, Iain Hibbert wrote: >> >>> On Tue, 14 Jun 2011, Da Rock wrote: >>> >>> >>> >>>>> first, question: did you load ng_ubt(4) driver? >>>>> >>>>> >>>>> >>>> Naturally. Its in the handbook, and you never discount the handbook :) >>>> >>>> >>>>> if you did and device is still not recognized, could you please dump >>>>> device descriptor, i.e. use usbconfig(8) dump_device_desc command >>>>> >>>>> >>>>> >>>> ugen5.2: at usbus5, cfg=0 md=HOST spd=FULL >>>> (12Mbps) pwr=ON >>>> >>>> bDeviceClass = 0x00e0 >>>> bDeviceSubClass = 0x0001 >>>> bDeviceProtocol = 0x0001 >>>> >>>> >>> seems like the ng_ubt driver should attach to this directly.. >>> >>> >> Probably would if it recognised the product then. What is the correct way to >> do this then? I know about usbdevs, and the awk script to run, but does >> anything then need to be added to the driver to pick it up, or should that >> be all thats needed? >> > it does not look at the product. it looks at interface class, subclass > and protocol. are you sure you are loading ng_ubt(4) from loader.conf? > are there any error messages from ng_ubt(4) in /var/log/messages? > devd.conf problem then? I haven't got it in loader.conf, but I did kldload- dmesg output (although the last 2 lines disappear when unloaded/loaded: ubt0: on usbus5 WARNING: attempt to domain_add(bluetooth) after domainfinalize() WARNING: attempt to domain_add(netgraph) after domainfinalize() But ls dev shows no devices, and I can't start bluetooth services: /etc/rc.d/bluetooth: ERROR: Unable to setup Bluetooth stack for device ubt0 If it should work, then what am I doing wrong? > >>> >>> >>>>>>> I'm currently learning about this technology (I know, late bloomer >>>>>>> and all... :) ) and its various features- which are why I'm >>>>>>> looking carefully at it now for my current needs. Unfortunately >>>>>>> its the advanced features which I really need :( So if I can help >>>>>>> advance things I will. >>>>>>> >>>>>>> >>>>>>> >>>>>> what advanced features do you need? >>>>>> >>>>>> >>>>>> >>>> I'm a little new to jargon, but the features are stereo audio, better >>>> bitrates, remote control, phone control, etc (HSP, EDR, AV-something or >>>> rather >>>> I think at least). Basically all the cool media stuff available now that >>>> wasn't around with 1.x. Thats what has grabbed my interest now anyway, >>>> file >>>> transfer, dun... meh- I can do that with wifi. >>>> >>>> >>> better bitrates should be supported natively (not sure about the 3.0 HS >>> speeds, perhaps that requires extra work?) and the parts that would not be >>> supported from the top of my head would be "Secure Simple Pairing" and >>> reliable L2CAP channels, most of the rest is just operating over >>> normal L2CAP/RFCOMM sockets anyway.. >>> >>> the Advanced Audio I have wanted to do for some time as an audio daemon >>> but never got around to starting (not sure actually, how complex it will >>> be - for FreeBSD it would require something like the NetBSD pad(4) driver >>> to be added also).. the Heaset will actually use SCO sockets for audio, >>> which I think FreeBSD does support and there is some code in NetBSD that >>> handles it (via a special kernel audio device, but it should be converted >>> to use pad(4)). Similarly for Handsfree (there is a bthfp program that I >>> wrote, basically a proof-of-concept rather than being greatly useful) >>> >>> not sure how the AV?TP profiles/protocols work, I don't think they are all >>> that complex, it might be that they can represent as a HID profile or if >>> it needs to be tied somewhat into a media player software. It does sound >>> interesting, but I rarely use media from my computer and have never found >>> a need.. >>> >>> >> I'll have a look at all that then, the media control is a HID profile >> btw(found that by accident looking into a IR remote and HID keyboard oddly >> enough). >> >>> I was actually looking at a Bluetooth capable printer (HP 470) on ebay the >>> other day, because I'm sick of using a BJ10 and I hate wires, though the >>> price seemed a little out of my range.. >>> >>> btw all the specifications are available from www.bluetooth.com :) >>> >>> >> Thanks Iain, I'll check it out :) >> >>> iain >>> >>> >> _______________________________________________ >> freebsd-bluetooth@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth >> To unsubscribe, send any mail to "freebsd-bluetooth-unsubscribe@freebsd.org" >> >> From owner-freebsd-bluetooth@FreeBSD.ORG Thu Jun 16 17:22:17 2011 Return-Path: Delivered-To: bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A4FB0106566C for ; Thu, 16 Jun 2011 17:22:17 +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 2B27A8FC13 for ; Thu, 16 Jun 2011 17:22:16 +0000 (UTC) Received: by bwz12 with SMTP id 12so2165351bwz.13 for ; Thu, 16 Jun 2011 10:22:15 -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; bh=fPaI13HuuSjEI25U/kbDQxkL3Jg8b0dn+yT2BdDHSR4=; b=q1/Z3swYQNlMsOFZPtdTAJie3RyVKJNYkFf5hqwEleA5ya1eggZZyXdzFiUTKtpcD4 iC+FYpYLNir0HNhEe/H7IOhA2AMJkfivfYRR+PbB3pH0iAS7UCOCie0YkjqK+BHI0vQX NUNX0hOkuHLVJ8JLGFXfhSkZtKXP4YsQm/+lY= 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; b=gRFXDyQLGVh/cNdcpHKKDI6RejmZzOBcKN1hTQSk4HP/JvOCnuxAluUlEGfnZksrZz OP79wOXZngsk+DcxzFGylnJLrO38d79p2DgJTt3MvPP9E/5ANE8g4j7jifUdSYoqco+f JWSZ1qjDeNqZWrc7MQPHIkIN2uPElvE51kcYE= MIME-Version: 1.0 Received: by 10.205.82.199 with SMTP id ad7mr827810bkc.152.1308244935801; Thu, 16 Jun 2011 10:22:15 -0700 (PDT) Received: by 10.204.36.12 with HTTP; Thu, 16 Jun 2011 10:22:15 -0700 (PDT) In-Reply-To: <4DF8430C.3010104@herveybayaustralia.com.au> References: <4DF46049.6080206@herveybayaustralia.com.au> <4DF53A6F.9080701@herveybayaustralia.com.au> <4DF705C9.7020606@herveybayaustralia.com.au> <4DF7F13C.6090208@herveybayaustralia.com.au> <4DF8430C.3010104@herveybayaustralia.com.au> Date: Thu, 16 Jun 2011 10:22:15 -0700 Message-ID: From: Maksim Yevmenkin To: Da Rock Content-Type: text/plain; charset=ISO-8859-1 Cc: bluetooth@freebsd.org Subject: Re: Asus bluetooth device - 0x1712 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: Thu, 16 Jun 2011 17:22:17 -0000 [...] >>> Probably would if it recognised the product then. What is the correct way >>> to >>> do this then? I know about usbdevs, and the awk script to run, but does >>> anything then need to be added to the driver to pick it up, or should >>> that >>> be all thats needed? >> >> it does not look at the product. it looks at interface class, subclass >> and protocol. are you sure you are loading ng_ubt(4) from loader.conf? >> are there any error messages from ng_ubt(4) in /var/log/messages? > > devd.conf problem then? I haven't got it in loader.conf, but I did kldload- > dmesg output (although the last 2 lines disappear when unloaded/loaded: > > ubt0: on > usbus5 > WARNING: attempt to domain_add(bluetooth) after domainfinalize() > WARNING: attempt to domain_add(netgraph) after domainfinalize() if you get ubt0 line then device was recognized and attached. those two WARNING messages are harmless > But ls dev shows no devices, and I can't start bluetooth services: ng_ubt(4) does NOT create device nodes in /dev. this question pops up very often. handbook should really be updated to mention this. > /etc/rc.d/bluetooth: ERROR: Unable to setup Bluetooth stack for device ubt0 > > If it should work, then what am I doing wrong? devd(8) will start/stop stack for you automatically. please check devd.conf (look at ubt secion). there is no need to start stack by hand any more. the error is because you are trying to start the stack when its already been started. again, handbook should be updated to reflect that. max From owner-freebsd-bluetooth@FreeBSD.ORG Thu Jun 16 21:49:28 2011 Return-Path: Delivered-To: bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0346B106564A for ; Thu, 16 Jun 2011 21:49:28 +0000 (UTC) (envelope-from freebsd-bluetooth@herveybayaustralia.com.au) Received: from mail.unitedinsong.com.au (mail.unitedinsong.com.au [150.101.178.33]) by mx1.freebsd.org (Postfix) with ESMTP id 9D2708FC16 for ; Thu, 16 Jun 2011 21:49:27 +0000 (UTC) Received: from laptop1.herveybayaustralia.com.au (laptop1.herveybayaustralia.com.au [192.168.0.186]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.unitedinsong.com.au (Postfix) with ESMTPS id 72A4D5C24; Fri, 17 Jun 2011 07:58:38 +1000 (EST) Message-ID: <4DFA7AB4.3010405@herveybayaustralia.com.au> Date: Fri, 17 Jun 2011 07:50:44 +1000 From: Da Rock User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.16) Gecko/20110204 Thunderbird/3.0.11 ThunderBrowse/3.3.4 MIME-Version: 1.0 To: Maksim Yevmenkin References: <4DF46049.6080206@herveybayaustralia.com.au> <4DF53A6F.9080701@herveybayaustralia.com.au> <4DF705C9.7020606@herveybayaustralia.com.au> <4DF7F13C.6090208@herveybayaustralia.com.au> <4DF8430C.3010104@herveybayaustralia.com.au> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: bluetooth@freebsd.org Subject: Re: Asus bluetooth device - 0x1712 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: Thu, 16 Jun 2011 21:49:28 -0000 On 06/17/11 03:22, Maksim Yevmenkin wrote: > [...] > > >>>> Probably would if it recognised the product then. What is the correct way >>>> to >>>> do this then? I know about usbdevs, and the awk script to run, but does >>>> anything then need to be added to the driver to pick it up, or should >>>> that >>>> be all thats needed? >>>> >>> it does not look at the product. it looks at interface class, subclass >>> and protocol. are you sure you are loading ng_ubt(4) from loader.conf? >>> are there any error messages from ng_ubt(4) in /var/log/messages? >>> >> devd.conf problem then? I haven't got it in loader.conf, but I did kldload- >> dmesg output (although the last 2 lines disappear when unloaded/loaded: >> >> ubt0: on >> usbus5 >> WARNING: attempt to domain_add(bluetooth) after domainfinalize() >> WARNING: attempt to domain_add(netgraph) after domainfinalize() >> > if you get ubt0 line then device was recognized and attached. > > those two WARNING messages are harmless > > >> But ls dev shows no devices, and I can't start bluetooth services: >> > ng_ubt(4) does NOT create device nodes in /dev. this question pops up > very often. handbook should really be updated to mention this. > > >> /etc/rc.d/bluetooth: ERROR: Unable to setup Bluetooth stack for device ubt0 >> >> If it should work, then what am I doing wrong? >> > devd(8) will start/stop stack for you automatically. please check > devd.conf (look at ubt secion). there is no need to start stack by > hand any more. the error is because you are trying to start the stack > when its already been started. again, handbook should be updated to > reflect that. > > max > Thanks Max. Sounds like there is updating required in the handbook- but how do I test whether its actually working or not? Those are the tests to show it works. Perhaps some more decisive tests should be included? From owner-freebsd-bluetooth@FreeBSD.ORG Thu Jun 16 22:11:10 2011 Return-Path: Delivered-To: bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 206B5106564A for ; Thu, 16 Jun 2011 22:11:10 +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 90F448FC15 for ; Thu, 16 Jun 2011 22:11:09 +0000 (UTC) Received: by bwz12 with SMTP id 12so2426362bwz.13 for ; Thu, 16 Jun 2011 15:11:08 -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=EgkZGmIM3jUbxTm7hfJyxcDPbqz/qERT8OGhdwp677Y=; b=u3fmX0ftmCPmlk6cFycZr1hoJudQmP2TA6e1BcQKE9n65gl62kCIYiycusriJkETCa x6R3vII5Ow8pT1S5zuOHRYMv2GdswMR+y3V01ac5r7om6xpr0gaUlB3oQ3395Pp9HXsW 2BIcoscT+aEsCczqN7Qg9CSJgYSFxYMhRsD5U= 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=M8h0gke+0x+faUHM9C1iCinOgLYHssW733vThQkr4uWN2Cb4XrBtlHMArpQJOtgVon B8TBPfqYgq1NsSSsTIElHzOA69n5Fz5HUkCt5hJtTxkTKoPDraW5l8aoMwR3JcfibCWW a9AKQYpBMiZ9LHOHaUrySU1Tib1FOWGUbyR8c= MIME-Version: 1.0 Received: by 10.204.19.18 with SMTP id y18mr1024883bka.179.1308262267978; Thu, 16 Jun 2011 15:11:07 -0700 (PDT) Received: by 10.204.36.12 with HTTP; Thu, 16 Jun 2011 15:11:07 -0700 (PDT) In-Reply-To: <4DFA7AB4.3010405@herveybayaustralia.com.au> References: <4DF46049.6080206@herveybayaustralia.com.au> <4DF53A6F.9080701@herveybayaustralia.com.au> <4DF705C9.7020606@herveybayaustralia.com.au> <4DF7F13C.6090208@herveybayaustralia.com.au> <4DF8430C.3010104@herveybayaustralia.com.au> <4DFA7AB4.3010405@herveybayaustralia.com.au> Date: Thu, 16 Jun 2011 15:11:07 -0700 Message-ID: From: Maksim Yevmenkin To: Da Rock Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: bluetooth@freebsd.org Subject: Re: Asus bluetooth device - 0x1712 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: Thu, 16 Jun 2011 22:11:10 -0000 On Thu, Jun 16, 2011 at 2:50 PM, Da Rock wrote: > On 06/17/11 03:22, Maksim Yevmenkin wrote: >> >> [...] >> >> >>>>> >>>>> Probably would if it recognised the product then. What is the correct >>>>> way >>>>> to >>>>> do this then? I know about usbdevs, and the awk script to run, but do= es >>>>> anything then need to be added to the driver to pick it up, or should >>>>> that >>>>> be all thats needed? >>>>> >>>> >>>> it does not look at the product. it looks at interface class, subclass >>>> and protocol. are you sure you are loading ng_ubt(4) from loader.conf? >>>> are there any error messages from ng_ubt(4) in /var/log/messages? >>>> >>> >>> devd.conf problem then? I haven't got it in loader.conf, but I did >>> kldload- >>> dmesg output (although the last 2 lines disappear when unloaded/loaded: >>> >>> ubt0: >>> =A0on >>> usbus5 >>> WARNING: attempt to domain_add(bluetooth) after domainfinalize() >>> WARNING: attempt to domain_add(netgraph) after domainfinalize() >>> >> >> if you get ubt0 line then device was recognized and attached. >> >> those two WARNING messages are harmless >> >> >>> >>> But ls dev shows no devices, and I can't start bluetooth services: >>> >> >> ng_ubt(4) does NOT create device nodes in /dev. this question pops up >> very often. handbook should really be updated to mention this. >> >> >>> >>> /etc/rc.d/bluetooth: ERROR: Unable to setup Bluetooth stack for device >>> ubt0 >>> >>> If it should work, then what am I doing wrong? >>> >> >> devd(8) will start/stop stack for you automatically. please check >> devd.conf (look at ubt secion). there is no need to start stack by >> hand any more. the error is because you are trying to start the stack >> when its already been started. again, handbook should be updated to >> reflect that. > > Thanks Max. Sounds like there is updating required in the handbook- but h= ow > do I test whether its actually working or not? Those are the tests to sho= w > it works. Perhaps some more decisive tests should be included? well, you could use hccontrol(8) and try to issue a couple of diagnostic commands, i.e. read_bd_addr, read_local_name, etc. to see if your device responds to those. obexapp from ports (comms/obexapp) is often used to transfer files to/from mobile phones/pdas. rfcomm_pppd(8) and rfcomm_sppd(1) in combination with ppp(8) are often used to create data link, i.e. use mobile phone data connection to connect to the internet. btpand(8) can be used to build ethernet-over-bluetooth lan. bthidd(8) can be used to connect your bluetooth keyboard/mouse to your freebsd pc etc. etc. bluetooth audio is lacking, i might get around to implementing a2dp profile and possibly avrcp profile but no promises. in other word, try to use it and if something does not work - ask and/or implement it :) thanks, max