From owner-freebsd-bluetooth@FreeBSD.ORG Mon Nov 1 11:06:53 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 6919E106566B for ; Mon, 1 Nov 2010 11:06:53 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 3BC9E8FC32 for ; Mon, 1 Nov 2010 11:06:53 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id oA1B6rlI019111 for ; Mon, 1 Nov 2010 11:06:53 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id oA1B6qKZ019109 for freebsd-bluetooth@FreeBSD.org; Mon, 1 Nov 2010 11:06:52 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 1 Nov 2010 11:06:52 GMT Message-Id: <201011011106.oA1B6qKZ019109@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-bluetooth@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-bluetooth@FreeBSD.org 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, 01 Nov 2010 11:06:53 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- p kern/140590 bluetooth [bluetooth] ng_ubt(4) ng_l2cap_process_cmd_rej warning 1 problem total. From owner-freebsd-bluetooth@FreeBSD.ORG Tue Nov 2 20:25:29 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 8419D106564A for ; Tue, 2 Nov 2010 20:25:29 +0000 (UTC) (envelope-from rnejdl@ringofsaturn.com) Received: from tethys.ringofsaturn.com (tethys.ringofsaturn.com [71.252.219.43]) by mx1.freebsd.org (Postfix) with ESMTP id 348AC8FC17 for ; Tue, 2 Nov 2010 20:25:28 +0000 (UTC) Received: from ASSP.nospam (tethys [71.252.219.43]) (authenticated bits=0) by tethys.ringofsaturn.com (8.14.4/8.14.4) with ESMTP id oA2Ju3Pg073397 for ; Tue, 2 Nov 2010 14:56:03 -0500 (CDT) (envelope-from rnejdl@ringofsaturn.com) Received: from mail.ringofsaturn.com ([71.252.219.43] helo=mail.ringofsaturn.com) with IPv4:25 by ASSP.nospam; 2 Nov 2010 14:56:02 -0500 MIME-Version: 1.0 Date: Tue, 02 Nov 2010 14:56:02 -0500 From: Rusty Nejdl To: Message-ID: <06b90815b84b40625e37317bc16b13ec@ringofsaturn.com> X-Sender: rnejdl@ringofsaturn.com User-Agent: RoundCube Webmail/0.5-trunk X-Assp-Version: 1.7.5.7(1.0.07) on ASSP.nospam X-Assp-Intended-For-IP: 71.252.219.43 X-Assp-Passing: authenticated X-Assp-ID: ASSP.nospam 27763-00768 X-Assp-Envelope-From: rnejdl@ringofsaturn.com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Troubleshooting a USB Bluetooth Dongle X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rnejdl@ringofsaturn.com 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 20:25:29 -0000 I am trying to find a working bluetooth dongle or get the one I have working. I purchased a ASUS USB-BT211 [1] which is cheap but is not picked up by FreeBSD. All of the bluetooth devices mentioned on the website are not manufactured any more and I was hoping to be able to utilize something more recent. So, if anyone can recommend a recent device like the above or how I can assist in troubleshooting the device I purchased, I would appreciate any feedback. Sincerely, Rusty Nejdl Links: ------ [1] http://www.newegg.com/Product/Product.aspx?Item=N82E16833320057 From owner-freebsd-bluetooth@FreeBSD.ORG Tue Nov 2 20:36:58 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 D4969106564A for ; Tue, 2 Nov 2010 20:36:58 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 9B1998FC15 for ; Tue, 2 Nov 2010 20:36:58 +0000 (UTC) Received: by iwn39 with SMTP id 39so8878379iwn.13 for ; Tue, 02 Nov 2010 13:36:58 -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=+qirEHLw8XCXxRg/olB/6Q908xJWCNVUNHV543RYNq8=; b=GBBr+aSBcpXiOFzx0HjxKE0MZbucTVn+25cXXrhfe6VRmUzwFXpXV0K7nX3uLHy2dN LqsIS4G4kBYhot0ns2f4NhDgtBy9NX1TafmkVpdRTd2Dci0uUTJxgLGOlO3WpWWtNVRS qHf10Bj4hE63lbP9mR3q4y/HNs2WLQW2B0DRU= 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=DEE/pnBjLOML1swDndR0GZKmB+rhiJWucNkXHreiaj0g5cSmqnhyH9cm9JIk5PMf0n gGtTWLBdpUbqFgmXYxOV8H1UUzChezk4b6WH9N2UANwtYnBe3GEM5dsiKrnaLmXyfHbR jvIuuPaIbTzA47WvmR35O1SdSN7xChatTSqmk= MIME-Version: 1.0 Received: by 10.231.31.1 with SMTP id w1mr7194752ibc.162.1288730216982; Tue, 02 Nov 2010 13:36:56 -0700 (PDT) Received: by 10.231.191.206 with HTTP; Tue, 2 Nov 2010 13:36:56 -0700 (PDT) In-Reply-To: <06b90815b84b40625e37317bc16b13ec@ringofsaturn.com> References: <06b90815b84b40625e37317bc16b13ec@ringofsaturn.com> Date: Tue, 2 Nov 2010 13:36:56 -0700 Message-ID: From: Maksim Yevmenkin To: rnejdl@ringofsaturn.com 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 20:36:58 -0000 Hello, > I am trying to find a working bluetooth dongle or get the one I have > working. I purchased a =EF=BB=BFASUS USB-BT211 [1] which is cheap but is = not > picked up by FreeBSD. All of the bluetooth devices mentioned on the > website are not manufactured any more and I was hoping to be able to > utilize something more recent. So, if anyone can recommend a recent > device like the above or how I can assist in troubleshooting the device > I purchased, I would appreciate any feedback. i assume that you have kldload(8)ed ng_ubt(4) driver, correct? if you did, and it still does not work, then could you please dump usb descriptor for the device? quick google search suggests that at least some of those adapters are based on atheros ar3011 chip (vendor/device id 0x0cf3/0x3000) , and require firmware download. basically, very similar to a certain broadcom chip, for which we have ubtbcmfw(4) driver. thanks, max > > Sincerely, > > Rusty > Nejdl > > Links: > ------ > [1] > http://www.newegg.com/Product/Product.aspx?Item=3DN82E16833320057 > _______________________________________________ > 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 Tue Nov 2 21:18:40 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 C4CFE1065672 for ; Tue, 2 Nov 2010 21:18:40 +0000 (UTC) (envelope-from rnejdl@ringofsaturn.com) Received: from tethys.ringofsaturn.com (tethys.ringofsaturn.com [71.252.219.43]) by mx1.freebsd.org (Postfix) with ESMTP id 7133A8FC14 for ; Tue, 2 Nov 2010 21:18:40 +0000 (UTC) Received: from ASSP.nospam (tethys [71.252.219.43]) (authenticated bits=0) by tethys.ringofsaturn.com (8.14.4/8.14.4) with ESMTP id oA2LIdVR090917; Tue, 2 Nov 2010 16:18:39 -0500 (CDT) (envelope-from rnejdl@ringofsaturn.com) Received: from mail.ringofsaturn.com ([71.252.219.43] helo=mail.ringofsaturn.com) with IPv4:25 by ASSP.nospam; 2 Nov 2010 16:18:38 -0500 MIME-Version: 1.0 Date: Tue, 02 Nov 2010 16:18:38 -0500 From: Rusty Nejdl To: Maksim Yevmenkin In-Reply-To: References: <06b90815b84b40625e37317bc16b13ec@ringofsaturn.com> Message-ID: <8647f55a4e8dcce33036a0810564b9e0@ringofsaturn.com> X-Sender: rnejdl@ringofsaturn.com User-Agent: RoundCube Webmail/0.5-trunk X-Assp-Version: 1.7.5.7(1.0.07) on ASSP.nospam X-Assp-Intended-For-IP: 71.252.219.43 X-Assp-Passing: authenticated X-Assp-ID: ASSP.nospam 32719-05907 X-Assp-Envelope-From: rnejdl@ringofsaturn.com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 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 Reply-To: rnejdl@ringofsaturn.com 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 21:18:40 -0000 On Tue, 2 Nov 2010 13:36:56 -0700, Maksim Yevmenkin wrote: > Hello, > >> I am trying to find a working bluetooth dongle or get the one I have working. I purchased a ASUS USB-BT211 [1] which is cheap but is not picked up by FreeBSD. All of the bluetooth devices mentioned on the website are not manufactured any more and I was hoping to be able to utilize something more recent. So, if anyone can recommend a recent device like the above or how I can assist in troubleshooting the device I purchased, I would appreciate any feedback. > i assume that you have kldload(8)ed ng_ubt(4) driver, correct? if you did, and it still does not work, then could you please dump usb descriptor for the device? quick google search suggests that at least some of those adapters are based on atheros ar3011 chip (vendor/device id 0x0cf3/0x3000) , and require firmware download. basically, very similar to a certain broadcom chip, for which we have ubtbcmfw(4) driver. thanks, max Maksim, Thanks for the response. Indeed, I have this in /boot/loader.conf: # --- Generated by sysinstall --- kern.cam.scsi_delay="1000" autoboot_delay="3" ahci_load="YES" linux_load="YES" ipfw_load="YES" ipdivert_load="YES" accf_http_load="YES" accf_data_load="YES" atapicam_load="YES" mvs_load="YES" vboxdrv_load="YES" nvidia_load="YES" ng_ubt_load="YES" ichsmb_load="YES" coretemp_load="YES" I manually loaded ubtbcmfw and then plugged my device in and I get: Nov 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: [tethys]:/home/rnejdl> usbconfig ugen0.1: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen1.1: at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen2.1: at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen3.1: at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen4.1: at usbus4, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen5.1: at usbus5, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen6.1: at usbus6, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen7.1: at usbus7, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen3.2: at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen4.2: at usbus4, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen5.2: at usbus5, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen5.3: at usbus5, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen3.3: at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON [tethys]:/home/rnejdl> usbconfig -u 3 -a 3 dump_curr_config_desc ugen3.3: at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x0019 bNumInterfaces = 0x0001 bConfigurationValue = 0x0001 iConfiguration = 0x0000 bmAttributes = 0x0080 bMaxPower = 0x0032 Interface 0 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0000 bAlternateSetting = 0x0000 bNumEndpoints = 0x0001 bInterfaceClass = 0x00ff bInterfaceSubClass = 0x0000 bInterfaceProtocol = 0x0000 iInterface = 0x0000 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0002 bmAttributes = 0x0002 wMaxPacketSize = 0x0040 bInterval = 0x0000 bRefresh = 0x0000 bSynchAddress = 0x0000 So, any suggestions on where to go next? Rusty Nejdl From owner-freebsd-bluetooth@FreeBSD.ORG Tue Nov 2 21:29:08 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 3394C1065674 for ; Tue, 2 Nov 2010 21:29:08 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id E002F8FC14 for ; Tue, 2 Nov 2010 21:29:07 +0000 (UTC) Received: by ywh2 with SMTP id 2so4166591ywh.13 for ; Tue, 02 Nov 2010 14:29:07 -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=G0DqBsMKEti22axjWwgNDvCx+3NAMN2yBb70BfVet9Y=; b=q1tsc34j6DILNrqCOQ5f6smNSqiyHNGDRyDPP2YkcHYTLJ7wSdwnne0ROnG6zlQDlF fdLeuCYaIBXieUpTzCWsIz4R0QOOT4fX95bsuMzbsTOyP0jn7vmj+qZsg32sq0LHVsnq rP+QBPA8/EZEZJq2ujC2t/Nu1rMCugg106qbw= 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=RW1Ul5YrcyoT0KBJN3yT0RVt0zSwqd24h4LZi4REkhYdE6CizmoV5EtjlgSYEeZ3JA NWxWyoMWksIx5jpLMRNb/Fm0GXrLcSCD30RZZ1fdiJALVz6UIyobaLNisPfGkP+tsCVV 7FtzVbhD68QGnfzA8OCAqDOtMph8slHWEs5kg= MIME-Version: 1.0 Received: by 10.42.117.3 with SMTP id r3mr5631958icq.143.1288733346897; Tue, 02 Nov 2010 14:29:06 -0700 (PDT) Received: by 10.231.191.206 with HTTP; Tue, 2 Nov 2010 14:29:06 -0700 (PDT) In-Reply-To: <8647f55a4e8dcce33036a0810564b9e0@ringofsaturn.com> References: <06b90815b84b40625e37317bc16b13ec@ringofsaturn.com> <8647f55a4e8dcce33036a0810564b9e0@ringofsaturn.com> Date: Tue, 2 Nov 2010 14:29:06 -0700 Message-ID: From: Maksim Yevmenkin To: rnejdl@ringofsaturn.com 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 21:29:08 -0000 On Tue, Nov 2, 2010 at 2:18 PM, Rusty Nejdl wrote= : >>> On Tue, 2 Nov 2010 13:36:56 -0700, Maksim Yevmenkin wrote: >>> >>> Hello, >>> >>> I am trying to find a working bluetooth dongle or get the one I have >>> working. I purchased a =EF=BB=BFASUS USB-BT211 [1] which is cheap but i= s not >>> picked up by FreeBSD. All of the bluetooth devices mentioned on the >>> website are not manufactured any more and I was hoping to be able to >>> utilize something more recent. So, if anyone can recommend a recent >>> device like the above or how I can assist in troubleshooting the device >>> I purchased, I would appreciate any feedback. >> >> i assume that you have kldload(8)ed ng_ubt(4) driver, correct? >> >> if you did, and it still does not work, then could you please dump usb >> descriptor for the device? quick google search suggests that at least >> some of those adapters are based on atheros ar3011 chip (vendor/device >> id 0x0cf3/0x3000) , and require firmware download. basically, very >> similar to a certain broadcom chip, for which we have ubtbcmfw(4) >> driver. [...] thanks for the information > =EF=BB=BFNov 2 16:08:02 tethys root: Unknown USB device: vendor 0x0cf3 p= roduct > 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 dongle)= ; the good thing is that linux 2.6.33.7 kernel already has firmware driver, so, it makes it easier to port. i can probably take a stab at it, but, without device, you would have to test it (and likely to crash your machine several times :) are you up for it? thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Tue Nov 2 21:54:33 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 85F2B1065782 for ; Tue, 2 Nov 2010 21:54:33 +0000 (UTC) (envelope-from rnejdl@ringofsaturn.com) Received: from tethys.ringofsaturn.com (tethys.ringofsaturn.com [71.252.219.43]) by mx1.freebsd.org (Postfix) with ESMTP id 31A4B8FC14 for ; Tue, 2 Nov 2010 21:54:32 +0000 (UTC) Received: from ASSP.nospam (tethys [71.252.219.43]) (authenticated bits=0) by tethys.ringofsaturn.com (8.14.4/8.14.4) with ESMTP id oA2LsWKJ092832; Tue, 2 Nov 2010 16:54:32 -0500 (CDT) (envelope-from rnejdl@ringofsaturn.com) Received: from mail.ringofsaturn.com ([71.252.219.43] helo=mail.ringofsaturn.com) with IPv4:25 by ASSP.nospam; 2 Nov 2010 16:54:31 -0500 MIME-Version: 1.0 Date: Tue, 02 Nov 2010 16:54:31 -0500 From: Rusty Nejdl To: Maksim Yevmenkin In-Reply-To: References: <06b90815b84b40625e37317bc16b13ec@ringofsaturn.com> <8647f55a4e8dcce33036a0810564b9e0@ringofsaturn.com> Message-ID: X-Sender: rnejdl@ringofsaturn.com User-Agent: RoundCube Webmail/0.5-trunk X-Assp-Version: 1.7.5.7(1.0.07) on ASSP.nospam X-Assp-Intended-For-IP: 71.252.219.43 X-Assp-Passing: authenticated X-Assp-ID: ASSP.nospam 34872-08105 X-Assp-Envelope-From: rnejdl@ringofsaturn.com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 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 Reply-To: rnejdl@ringofsaturn.com 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 21:54:33 -0000 On Tue, 2 Nov 2010 14:29:06 -0700, Maksim Yevmenkin wrote: > On Tue, Nov 2, 2010 at 2:18 PM, Rusty Nejdl wrote: >>>> On Tue, 2 Nov 2010 13:36:56 -0700, Maksim Yevmenkin wrote: Hello, I am trying to find a working bluetooth dongle or get the one I have working. I purchased a ASUS USB-BT211 [1] which is cheap but is not picked up by FreeBSD. All of the bluetooth devices mentioned on the website are not manufactured any more and I was hoping to be able to utilize something more recent. So, if anyone can recommend a recent device like the above or how I can assist in troubleshooting the device I purchased, I would appreciate any feedback. >>> i assume that you have kldload(8)ed ng_ubt(4) driver, correct? if you did, and it still does not work, then could you please dump usb descriptor for the device? quick google search suggests that at least some of those adapters are based on atheros ar3011 chip (vendor/device id 0x0cf3/0x3000) , and require firmware download. basically, very similar to a certain broadcom chip, for which we have ubtbcmfw(4) driver. > [...] thanks for the information > >> Nov 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 dongle); the good thing is that linux 2.6.33.7 kernel already has fir > >> uld have to test it (and likely to crash > several times :) are you up for it? thanks, max Max, Well, I have 3 different options: 1) Sure, I would be happy to test. 2) I am also testing out USB Pass through into VirtualBox and so can do some sandbox testing there. 3) I would be happy to order one and have it sent your way if you would like. Just let me know your address. Thanks! Rusty Nejdl Links: ------ [1] mailto:rnejdl@ringofsaturn.com From owner-freebsd-bluetooth@FreeBSD.ORG Tue Nov 2 22:05:18 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 BD3EB1065694 for ; 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 ; 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 To: Maksim Yevmenkin In-Reply-To: Message-ID: References: <06b90815b84b40625e37317bc16b13ec@ringofsaturn.com> <8647f55a4e8dcce33036a0810564b9e0@ringofsaturn.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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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-- From owner-freebsd-bluetooth@FreeBSD.ORG Tue Nov 2 22:26:31 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 A61E8106564A for ; Tue, 2 Nov 2010 22:26:31 +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 42F7B8FC15 for ; Tue, 2 Nov 2010 22:26:30 +0000 (UTC) Received: from localhost (smtp-filter.ukfsn.org [192.168.54.205]) by mail.ukfsn.org (Postfix) with ESMTP id 9D259DEC82 for ; Tue, 2 Nov 2010 22:26:29 +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 ReblGOhof+Bm for ; Tue, 2 Nov 2010 22:26:29 +0000 (GMT) Received: from galant.ukfsn.org (unknown [89.194.39.203]) by mail.ukfsn.org (Postfix) with ESMTP id 75DDADEC7F for ; Tue, 2 Nov 2010 22:26:28 +0000 (GMT) Received: by galant.ukfsn.org (Postfix, from userid 1000) id CFE50260261; Tue, 2 Nov 2010 22:26:08 +0000 (GMT) Date: Tue, 2 Nov 2010 22:26:08 +0000 (GMT) From: Iain Hibbert To: freebsd-bluetooth@freebsd.org Message-ID: User-Agent: Alpine 2.00 (NEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-707870261-1288736768=:10122" Subject: obexapp alloc server channel 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:26:31 -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-707870261-1288736768=:10122 Content-Type: TEXT/PLAIN; charset=US-ASCII Hi, one more thing for obexapp, I think FreeBSD has the thing of RFCOMM where you can bind() to channel 0 and use getsockname() after listen() in order to find the allocated channel? It was discussed on the list some time ago anyway, and I did implement it on NetBSD (using RFCOMM_CHANNEL_ANY == 0) The patch attached implements this functionality in obexapp, allowing -C to be optional in server mode. regards, iain btw I implemented similar for L2CAP except that binding to L2CAP_PSM_ANY gets you one of the dynamic PSM (1001->) after listen() call --0-707870261-1288736768=:10122 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=any.diff Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename=any.diff LS0tIG1haW4uYy5vcmlnCTIwMTAtMTAtMjIgMDc6Mjk6MDYuMDAwMDAwMDAw ICswMTAwDQorKysgbWFpbi5jCTIwMTAtMTEtMDIgMjI6MDU6MDguMDAwMDAw MDAwICswMDAwDQpAQCAtMjY2LDcgKzI2Niw3IEBADQogCQl9DQogCX0NCiAN Ci0JaWYgKGNvbnRleHQuY2hhbm5lbCA8PSAwIHx8IGNvbnRleHQuY2hhbm5l bCA+IDMwKQ0KKwlpZiAoKGNvbnRleHQuY2hhbm5lbCA9PSAwICYmICFjb250 ZXh0LnNlcnZlcikgfHwgY29udGV4dC5jaGFubmVsID4gMzApDQogCQllcnJ4 KDEsICJJbnZhbGlkIFJGQ09NTSBjaGFubmVsICVkIiwNCiAJCQljb250ZXh0 LmNoYW5uZWwpOw0KIA0KLS0tIHRyYW5zcG9ydC5jLm9yaWcJMjAxMC0xMC0y MiAwNzoyOTowNi4wMDAwMDAwMDAgKzAxMDANCisrKyB0cmFuc3BvcnQuYwky MDEwLTExLTAyIDIyOjExOjE5LjAwMDAwMDAwMCArMDAwMA0KQEAgLTIwMiw2 ICsyMDIsMTYgQEANCiAJCXJldHVybiAoLTEpOw0KIAl9DQogDQorCWlmIChj b250ZXh0LT5jaGFubmVsID09IDApIHsNCisJCWFkZHJsZW4gPSBzaXplb2Yo YWRkcik7DQorCQlpZiAoZ2V0c29ja25hbWUocywgKHN0cnVjdCBzb2NrYWRk ciAqKSAmYWRkciwgJmFkZHJsZW4pIDwgMCkgew0KKwkJCWxvZ19lcnIoIiVz KCk6IENvdWxkIG5vdCBnZXQgc29ja2V0IGFkZHJlc3MuICVzICglZCkiLA0K KwkJCQlfX2Z1bmNfXywgIHN0cmVycm9yKGVycm5vKSwgZXJybm8pOw0KKwkJ CXJldHVybiAoLTEpOw0KKwkJfQ0KKwkJY29udGV4dC0+Y2hhbm5lbCA9IGFk ZHIucmZjb21tX2NoYW5uZWw7DQorCX0NCisNCiAJbWVtc2V0KCZvcHVzaCwg MCwgc2l6ZW9mKG9wdXNoKSk7DQogCW9wdXNoLnNlcnZlcl9jaGFubmVsID0g Y29udGV4dC0+Y2hhbm5lbDsNCiAJb3B1c2guc3VwcG9ydGVkX2Zvcm1hdHNf c2l6ZSA9IDc7DQotLS0gb2JleGFwcC4xLm9yaWcJMjAwOS0wOC0yMCAyMjo1 NzoxOC4wMDAwMDAwMDAgKzAxMDANCisrKyBvYmV4YXBwLjEJMjAxMC0xMS0w MiAyMjoyMTozNi4wMDAwMDAwMDAgKzAwMDANCkBAIC01NCw3ICs1NCw3IEBA DQogLkZsIHMNCiAuT3AgRmwgZERGT1NSaA0KIC5PcCBGbCBBIEFyIEJEX0FE RFINCi0uRmwgQyBBciBjaGFubmVsDQorLk9wIEZsIEMgQXIgY2hhbm5lbA0K IC5PcCBGbCBtIEFyIE1UVQ0KIC5PcCBGbCByIEFyIHBhdGgNCiAuT3AgRmwg dSBBciB1c2VyDQpAQCAtMTE3LDggKzExNyw5IEBAIFRoZSBwYXRoIGNvbXBv bmVudCBvZiB0aGUgY29uc3RydWN0ZWQgcmUNCiAuUHANCiBJbiB0aGUgc2Vy dmVyIG1vZGUNCiAuTm0NCi1saXN0ZW5zIGZvciBpbmNvbW1pbmcgY29ubmVj dGlvbnMsIG9uIHRoZSBzcGVjaWZpZWQgQkRfQUREUiBhbmQgY2hhbm5lbCwg ZnJvbQ0KLXJlbW90ZSBjbGllbnRzLg0KK2xpc3RlbnMgZm9yIGluY29tbWlu ZyBjb25uZWN0aW9ucywgb24gdGhlIHNwZWNpZmllZCBCRF9BRERSIGFuZCBj aGFubmVsDQord2hlbiBnaXZlbiwgZnJvbSByZW1vdGUgY2xpZW50cy4NCitJ ZiBubyBjaGFubmVsIGlzIGdpdmVuLCB0aGUgZmlyc3QgdW51c2VkIFJGQ09N TSBjaGFubmVsIHdpbGwgYmUgYWxsb2NhdGVkLg0KIE9uY2UgbmV3IGNvbm5l Y3Rpb24gaXMgYWNjZXB0ZWQNCiAuTm0NCiBmb3JrcyBhbmQgc3RhcnQgbmV3 IE9CRVggc2VydmVyIGZvciB0aGUgY2xpZW50Lg0KQEAgLTE0NSw3ICsxNDYs NyBAQCBJZiBub3Qgc3BlY2lmaWVkLCBCREFERFJfQU5ZIHdpbGwgYmUgdXNl DQogSW4gdGhlIGNsaWVudCBtb2RlIHRoaXMgcmVxdWlyZWQgb3B0aW9uIHNw ZWNpZmllcyB0aGUgcmVtb3RlIEJEX0FERFIgb2YgdGhlDQogT0JFWCBzZXJ2 ZXIuDQogLkl0IEZsIEMgQXIgY2hhbm5lbA0KLUluIGJvdGggY2xpZW50IGFu ZCBzZXJ2ZXIgbW9kZXMgdGhpcyByZXF1aXJlZCBvcHRpb24gc3BlY2lmaWVz IFJGQ09NTSBjaGFubmVsDQorSW4gYm90aCBjbGllbnQgYW5kIHNlcnZlciBt b2RlcyB0aGlzIG9wdGlvbiBzcGVjaWZpZXMgUkZDT01NIGNoYW5uZWwNCiB0 byBjb25uZWN0IHRvIG9yIGxpc3RlbiBvbi4NCiBJbiB0aGUgc2VydmVyIG1v ZGUgUkZDT01NIGNoYW5uZWwgc2hvdWxkIGJlIG51bWJlciBiZXR3ZWVuIDEg YW5kIDMwLg0KIEluIHRoZSBjbGllbnQgbW9kZSBSRkNPTU0gY2hhbm5lbCBj b3VsZCBiZSBlaXRoZXIgbnVtYmVyIGJldHdlZW4gMSBhbmQgMzAgb3INCg== --0-707870261-1288736768=:10122-- 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 From owner-freebsd-bluetooth@FreeBSD.ORG Wed Nov 3 10:28:25 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 A20C31065672 for ; Wed, 3 Nov 2010 10:28:25 +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 675CB8FC1B for ; Wed, 3 Nov 2010 10:28:25 +0000 (UTC) Received: from localhost (smtp-filter.ukfsn.org [192.168.54.205]) by mail.ukfsn.org (Postfix) with ESMTP id C31A1DEC72 for ; Wed, 3 Nov 2010 10:28:23 +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 SGMDMtSjCr5x for ; Wed, 3 Nov 2010 10:28:23 +0000 (GMT) Received: from galant.ukfsn.org (unknown [89.194.39.203]) by mail.ukfsn.org (Postfix) with ESMTP id 473F6DEC71 for ; Wed, 3 Nov 2010 10:28:23 +0000 (GMT) Received: by galant.ukfsn.org (Postfix, from userid 1000) id 05DAA260261; Wed, 3 Nov 2010 10:27:58 +0000 (GMT) Date: Wed, 3 Nov 2010 10:27:57 +0000 (GMT) From: Iain Hibbert To: freebsd-bluetooth@freebsd.org Message-ID: User-Agent: Alpine 2.00 (NEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: obexapp should not use libbsdxml 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, 03 Nov 2010 10:28:25 -0000 Hi, according to the libbsdxml manpage, http://www.freebsd.org/cgi/man.cgi?query=libbsdxml&apropos=0&sektion=0&manpath=FreeBSD+8.1-RELEASE&format=html it should not really be used by external programs.. using expat directly (as per patch below) will cut down on a patch that is required on NetBSD + expat dependency would need to be added in ports/comms/obexapp (I guess that translating expat to builtin bsdxml could feature automatically in ports framework using ln -s) iain --- Makefile.orig 2010-01-08 18:31:22.000000000 +0000 +++ Makefile 2010-11-03 10:11:34.000000000 +0000 @@ -16,9 +16,9 @@ CFLAGS+= -I/usr/local/include \ -I/usr/local/include/openobex -DPADD= ${LIBBLUETOOTH} ${LIBSDP} ${LIBBSDXML} ${LIBREADLINE} +DPADD= ${LIBBLUETOOTH} ${LIBSDP} ${LIBREADLINE} LDADD= -L/usr/lib -L/usr/local/lib \ - -lbluetooth -lsdp -lopenobex -lbsdxml -lreadline -liconv + -lbluetooth -lsdp -lopenobex -lexpat -lreadline -liconv .include --- util.c.orig 2010-10-22 07:29:06.000000000 +0100 +++ util.c 2010-01-08 19:51:02.000000000 +0000 @@ -30,9 +30,9 @@ */ #include -#include #include #include +#include #include #include #include From owner-freebsd-bluetooth@FreeBSD.ORG Wed Nov 3 18:21:07 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 CC1911065674 for ; Wed, 3 Nov 2010 18:21:07 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 9347A8FC18 for ; Wed, 3 Nov 2010 18:21:07 +0000 (UTC) Received: by iwn39 with SMTP id 39so1004008iwn.13 for ; Wed, 03 Nov 2010 11:21:06 -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; bh=+yDItfYV6Dv4GlA82qHlolulk4qX8xOMclvM8WqdkQs=; b=E0ObzeK7rFlE8eiG0/aWnntKHKo3en+EW0CmUwORcUuf4svv0lhi1pUUddgqp2Sztr Mw3YLaoX9esY+fgdjNC23JEJB6Y1TFappgG/PBWEbt52lFuxfONZ/k3GI87yr7dTFU9t I9Qnz+zCTszpjN0UY3HqeE7bIaII5VgC0MOYc= 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=KD/ipIGB0Jl3siPt2DZPznJMr2yPPNqLzODHUI1aaTkM9lRu0uakUNTWADs4GLpJ3o V9RlsXBDFZPZx+Oi+lubgBchBa+s14KsWOQEV72MQhqihqAuTmLsyPYTtd62AtU6Wlir zyPKF5Az7IkPpBXFNji9TCI4iHlt+ikYNGUYs= MIME-Version: 1.0 Received: by 10.231.31.1 with SMTP id w1mr8180786ibc.162.1288808466643; Wed, 03 Nov 2010 11:21:06 -0700 (PDT) Received: by 10.231.191.206 with HTTP; Wed, 3 Nov 2010 11:21:06 -0700 (PDT) In-Reply-To: References: Date: Wed, 3 Nov 2010 11:21:06 -0700 Message-ID: From: Maksim Yevmenkin To: Iain Hibbert Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-bluetooth@freebsd.org Subject: Re: obexapp alloc server channel 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, 03 Nov 2010 18:21:07 -0000 Iain, > one more thing for obexapp, I think FreeBSD has the thing of RFCOMM where > you can bind() to channel 0 and use getsockname() after listen() in order > to find the allocated channel? It was discussed on the list some time ago > anyway, and I did implement it on NetBSD (using RFCOMM_CHANNEL_ANY == 0) > > The patch attached implements this functionality in obexapp, allowing -C > to be optional in server mode. cool. thanks! max From owner-freebsd-bluetooth@FreeBSD.ORG Wed Nov 3 18:27:28 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 629E11065673 for ; Wed, 3 Nov 2010 18:27:28 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 295518FC0A for ; Wed, 3 Nov 2010 18:27:27 +0000 (UTC) Received: by iwn39 with SMTP id 39so1009792iwn.13 for ; Wed, 03 Nov 2010 11:27:27 -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; bh=fNg2yizo+BygqA/dKm8zDgM4Ri9j4r3XlxRhIW8cXis=; b=acKNOURsvaSTYrero5i3BXRrT3Jc9pfIp1n42UGhXDo5VQKOsealNKA40noli/aYXZ 0RwhRj2yu7U+lqx48VS7L+H1VYrdAZW3laqLoKH8coxKhszchG/FdoHe98XuohigcJIl +sxLcr2vQSR/Pii2cEQRYV1maweojl0OG4bdg= 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=GUPTqXsWDX8aCU3WL2J0LOpBuNpUwmjiJVGdMpFITA7dFdewqQ6XE5dSZPclZDzWtg nuhBgGFWfVoKCzoTcoroVVw67h5hbQ3ToN3B7vsQlzdq1/kDqe0f1GhsfRL+t0zlvNSS WX1+FMpDbuDoDIFaXMYOJ7pEuAwx0lrQiezJo= MIME-Version: 1.0 Received: by 10.231.11.201 with SMTP id u9mr11370471ibu.187.1288808847352; Wed, 03 Nov 2010 11:27:27 -0700 (PDT) Received: by 10.231.191.206 with HTTP; Wed, 3 Nov 2010 11:27:27 -0700 (PDT) In-Reply-To: References: Date: Wed, 3 Nov 2010 11:27:27 -0700 Message-ID: From: Maksim Yevmenkin To: Iain Hibbert Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-bluetooth@freebsd.org Subject: Re: obexapp should not use libbsdxml 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, 03 Nov 2010 18:27:28 -0000 On Wed, Nov 3, 2010 at 3:27 AM, Iain Hibbert wrote: > Hi, > > according to the libbsdxml manpage, > > http://www.freebsd.org/cgi/man.cgi?query=libbsdxml&apropos=0&sektion=0&manpath=FreeBSD+8.1-RELEASE&format=html > > it should not really be used by external programs.. using expat directly > (as per patch below) will cut down on a patch that is required on NetBSD > > + expat dependency would need to be added in ports/comms/obexapp > (I guess that translating expat to builtin bsdxml could feature > automatically in ports framework using ln -s) thanks for the patch (again :) i'm not entirely sure about this one. i usually really dislike adding extra dependencies. because you never know what else it would drag. especially in case where everything is built from sources. i think, in this case, i could probably make an exception. these days libexpat is pulled with pretty much anything. so i guess it really probably not that big of a deal. ideally, i'd really want to get rid of openobex library and just put obexapp into base system (where it belongs imo). thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Wed Nov 3 18:59:21 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 C877D1065673 for ; Wed, 3 Nov 2010 18:59:21 +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 8B9DD8FC26 for ; Wed, 3 Nov 2010 18:59:21 +0000 (UTC) Received: from localhost (smtp-filter.ukfsn.org [192.168.54.205]) by mail.ukfsn.org (Postfix) with ESMTP id E0640DEC36; Wed, 3 Nov 2010 18:59:19 +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 Fi+UX9NlmqGj; Wed, 3 Nov 2010 18:59:19 +0000 (GMT) Received: from galant.ukfsn.org (unknown [89.194.39.203]) by mail.ukfsn.org (Postfix) with ESMTP id 67A82DEC33; Wed, 3 Nov 2010 18:59:19 +0000 (GMT) Received: by galant.ukfsn.org (Postfix, from userid 1000) id E088C260261; Wed, 3 Nov 2010 18:58:50 +0000 (GMT) Date: Wed, 3 Nov 2010 18:58:50 +0000 (GMT) From: Iain Hibbert To: Maksim Yevmenkin In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (NEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-bluetooth@freebsd.org Subject: Re: obexapp should not use libbsdxml 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, 03 Nov 2010 18:59:21 -0000 On Wed, 3 Nov 2010, Maksim Yevmenkin wrote: > i'm not entirely sure about this one. i usually really dislike adding > extra dependencies. because you never know what else it would drag. > especially in case where everything is built from sources. i think, in > this case, i could probably make an exception. these days libexpat is > pulled with pretty much anything. so i guess it really probably not that > big of a deal. ideally, i'd really want to get rid of openobex library > and just put obexapp into base system (where it belongs imo). NetBSD now actually includes libexpat as its part of X11R7 (Xorg), does FreeBSD not have the same? I wonder if not, if there is a softlink? the patch itself is not a big deal in fact, I just thought I'd send it as I was sending others :) iain (I think openobex might suck but I don't plan to write a replacement just yet :)