From owner-freebsd-bluetooth@FreeBSD.ORG Sun Apr 22 02:35:01 2007 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 32CC316A402 for ; Sun, 22 Apr 2007 02:35:01 +0000 (UTC) (envelope-from tscmga@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.246]) by mx1.freebsd.org (Postfix) with ESMTP id E385C13C46A for ; Sun, 22 Apr 2007 02:35:00 +0000 (UTC) (envelope-from tscmga@gmail.com) Received: by an-out-0708.google.com with SMTP id c24so1449836ana for ; Sat, 21 Apr 2007 19:35:00 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:from:reply-to:organization:to:subject:date:user-agent:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=QM81GaZpnoTZmdVcTQIU87oo9ZsYbkO9NQZnODPkY2SrQje/vDRc3tpMXziZyGfp9G8JlOy621kJJ3lY76e6yhUEqgy/BPGKx0EhxA2N9pdG7mY7XL61ETthoR6oXIdut+WaSpRrFF8pQqwXQ3iWAa4iqQXiSkp9QRWM20Dwjqc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:from:reply-to:organization:to:subject:date:user-agent:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=hA58iOHZPQfxXIGG1PvbQgKckZvwRR5j+Wha7ApKMzQ4HD72hqn8UVNlft2sixinDnsvOOxAQXxKwSfsndyUDn4pP8vbtCgjpQrR43RzL3NfX0RvipFyWb0pQ2sYM3g/bU9la2eSMBZHtghPQgA2kHUUdlQ9wyiNBwdMzjcgXgs= Received: by 10.114.108.15 with SMTP id g15mr1925484wac.1177207571382; Sat, 21 Apr 2007 19:06:11 -0700 (PDT) Received: from ?192.168.1.11? ( [218.79.151.163]) by mx.google.com with ESMTP id a8sm7200397poa.2007.04.21.19.06.09; Sat, 21 Apr 2007 19:06:10 -0700 (PDT) From: zhengzhi Organization: none To: freebsd-bluetooth@freebsd.org Date: Sun, 22 Apr 2007 10:09:31 +0000 User-Agent: KMail/1.8.2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200704221009.32512.tscmga@gmail.com> Subject: I bought a bluetooth headset yesterday, but I don't know how to use it in FreeBSD. X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: tscmga@gmail.com List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Apr 2007 02:35:01 -0000 Hi. I have googled , read the FreeBSD Handbook and some old threads in this maillist. There are documents about how to use the headset in NetBSD and linux. Someone had talked this in this maillist at Apr 2006 , at that time headset (is/was/did/had been) not supported . From owner-freebsd-bluetooth@FreeBSD.ORG Sun Apr 22 03:21:34 2007 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A75A816A400 for ; Sun, 22 Apr 2007 03:21:34 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.246]) by mx1.freebsd.org (Postfix) with ESMTP id 49B0213C44C for ; Sun, 22 Apr 2007 03:21:34 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: by an-out-0708.google.com with SMTP id c24so1456509ana for ; Sat, 21 Apr 2007 20:21:33 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Zby/WKxiaaF6KJngXXkdgrE/0VSSEwSLiIHvIrv+RjzXwCs7ufu1WIgtnY06w6AYMx7Rr7M0o5yEAP5AiQn4qHGCr8c5yvhHvmsC129Gq4ZGAHJbi28jgPcCOgwBRqvON6Nu1H/qcUApAWv74gMlOv4EcgQRAZHHCrPAfilu+Tw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=q8gSsIyJl7/PbIRo+7kcjF6TeHObR5qU3+Xx9wEAB01d6FxZLuwUBu1xl2AohvtYg9ZT+Awzq/N2jO/w262s+PLLN0gnX5G89ZHHKzEoqafdASGqjk+aoAIGmAvJaaYbDkz+2gQa0x5dHlBbPkCYq6Kvn8kTsz0RZbbiyls1JcU= Received: by 10.100.191.5 with SMTP id o5mr2715758anf.1177212093638; Sat, 21 Apr 2007 20:21:33 -0700 (PDT) Received: by 10.100.111.18 with HTTP; Sat, 21 Apr 2007 20:21:33 -0700 (PDT) Message-ID: Date: Sat, 21 Apr 2007 20:21:33 -0700 From: "Maksim Yevmenkin" To: tscmga@gmail.com In-Reply-To: <200704221009.32512.tscmga@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200704221009.32512.tscmga@gmail.com> Cc: freebsd-bluetooth@freebsd.org Subject: Re: I bought a bluetooth headset yesterday, but I don't know how to use it in FreeBSD. 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, 22 Apr 2007 03:21:34 -0000 On 4/22/07, zhengzhi wrote: > Hi. > I have googled , read the FreeBSD Handbook and some old threads in this > maillist. There are documents about how to use the headset in NetBSD and > linux. Someone had talked this in this maillist at Apr 2006 , at that time > headset (is/was/did/had been) not supported . still not supported. thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Mon Apr 23 05:10:54 2007 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0CB7F16A400 for ; Mon, 23 Apr 2007 05:10:54 +0000 (UTC) (envelope-from tscmga@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.228]) by mx1.freebsd.org (Postfix) with ESMTP id BCEB513C484 for ; Mon, 23 Apr 2007 05:10:53 +0000 (UTC) (envelope-from tscmga@gmail.com) Received: by wr-out-0506.google.com with SMTP id 70so1475392wra for ; Sun, 22 Apr 2007 22:10:53 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:from:reply-to:organization:to:subject:date:user-agent:references:in-reply-to:cc:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=W7njn9zZ5ieqZF/OlWeBgv1wFOWhtgf8x8Kox/cUyav9dFif8fCsSSlR0NlSJ4A5Fw+lTtdh8fdlYYVL+YheDA0rF6A2rqLyzefSxrtroCwPrqvC2oKOlJXlUBbp5kXZCLkRxzz94bIhTsKIhP8loBdTCRy24b0MDQu5w1OzkdU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:from:reply-to:organization:to:subject:date:user-agent:references:in-reply-to:cc:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=tMdGTbERIgLO9/DAzy71F0004veLIsCDfzmrbu0hBfOoUSUn0vA+HMVWYg/8gm4jnMehsq8bKzB5He1ktzHwjWIr9/wSYXQ1esNI5hUDNv1Xij0I08f2rUZEk1kNJR3XAVxfS0tb2eTKZYZDk151kZw6DPNU1cb2Cob1nzOBnmE= Received: by 10.114.209.1 with SMTP id h1mr2315045wag.1177305052627; Sun, 22 Apr 2007 22:10:52 -0700 (PDT) Received: from ?192.168.1.11? ( [58.35.2.4]) by mx.google.com with ESMTP id m29sm343347poh.2007.04.22.22.10.50; Sun, 22 Apr 2007 22:10:51 -0700 (PDT) From: zhengzhi Organization: none To: "Maksim Yevmenkin" Date: Mon, 23 Apr 2007 13:13:45 +0000 User-Agent: KMail/1.8.2 References: <200704221009.32512.tscmga@gmail.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200704231313.46374.tscmga@gmail.com> Cc: freebsd-bluetooth@freebsd.org Subject: Re: I bought a bluetooth headset yesterday, but I don't know how to use it in FreeBSD. X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: tscmga@gmail.com List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Apr 2007 05:10:54 -0000 On Sunday 22 April 2007 03:21 am, you wrote: > On 4/22/07, zhengzhi wrote: > > Hi. > > I have googled , read the FreeBSD Handbook and some old > > threads in this maillist. There are documents about how to use the > > headset in NetBSD and linux. Someone had talked this in this maillist at > > Apr 2006 , at that time headset (is/was/did/had been) not supported . > > still not supported. > > thanks, > max Thank you for the precise answer ! From owner-freebsd-bluetooth@FreeBSD.ORG Mon Apr 23 08:32:32 2007 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DFFA016A400 for ; Mon, 23 Apr 2007 08:32:32 +0000 (UTC) (envelope-from mlists@shadow-security.net) Received: from pecan.exetel.com.au (pecan.exetel.com.au [220.233.0.17]) by mx1.freebsd.org (Postfix) with ESMTP id 651A713C45A for ; Mon, 23 Apr 2007 08:32:32 +0000 (UTC) (envelope-from mlists@shadow-security.net) Received: from 26.214.233.220.exetel.com.au ([220.233.214.26] helo=[192.168.0.8]) by pecan.exetel.com.au with esmtp (Exim 4.63) (envelope-from ) id 1HfsdQ-0000E4-UP for freebsd-bluetooth@freebsd.org; Mon, 23 Apr 2007 17:06:53 +1000 Message-ID: <462C5A20.3030300@shadow-security.net> Date: Mon, 23 Apr 2007 17:02:56 +1000 From: Sh4d03 User-Agent: Thunderbird 1.5.0.10 (X11/20070306) MIME-Version: 1.0 To: freebsd-bluetooth@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Creating a PAN with Thinkpad R51, Samsung D500 and iPaq RX4240 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, 23 Apr 2007 08:32:33 -0000 Hello all, Ultimately I want to be able to connect my Laptop, PDA and Mobile together to share/synchronise appointments and contacts - the usual guff. My Hardware is as follows: IBM Thinkpad R51 USB Bluetooth Adapter (unknown brand) Samsung D500 Mobile Phone (Cellular) HP iPaq RX4240 Personal Digital Assistant My Software (so far): FreeBSD 6.2-STABLE obexapp-1.4.5 openobex-1.3 I've read/followed the handbook section for Bluetooth and accomplished the following so far: I've loaded the Kernel Module # kldload ng_ubt I've plugged in my USB Dongle and received the following in dmesg: ubt0: vendor 0x0a12 product 0x0001, rev 2.00/15.93, addr 3 ubt0: vendor 0x0a12 product 0x0001, rev 2.00/15.93, addr 3 ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=49; nframes=6, buffer size=294 I've copied /usr/share/examples/netgraph/bluetooth/rc.bluetooth to /etc/rc.bluetooth - despite 6.1 and above apparently being able to start bluetooth automagically. Now I run 'hccontrol -n ubt0hci inquiry' and receive: # hccontrol -n ubt0hci inquiry Inquiry result, num_responses=1 Inquiry result #0 BD_ADDR: 00:12:47:5c:be:6a Page Scan Rep. Mode: 0x1 Page Scan Period Mode: 00 Page Scan Mode: 00 Class: 52:02:04 Clock offset: 0x15e3 Inquiry result, num_responses=1 Inquiry result #0 BD_ADDR: Sh4d03_PDA Page Scan Rep. Mode: 00 Page Scan Period Mode: 0x2 Page Scan Mode: 00 Class: 32:01:10 Clock offset: 0x59fd Inquiry complete. Status: No error [00] # Next, to find out whether the first entry is really my phone I run 'hccontrol -n ubt0hci remote_name_request 00:12:47:5c:be:6a' # hccontrol -n ubt0hci remote_name_request 00:12:47:5c:be:6a BD_ADDR: 00:12:47:5c:be:6a Name: Sh4d03_Mobile Yep, it sure is. Next, I do 'hccontrol -n ubt0hci read_connection_list' and receive only the column headings - i.e. no currently open connections, which would make sense - right? Next, I attempt an l2ping to both devices: # sudo l2ping -a 00:12:47:5c:be:6a -c 4 4 bytes from 00:12:47:5c:be:6a seq_no=1313822285 time=560.831 ms result=0 4 bytes from 00:12:47:5c:be:6a seq_no=1313822285 time=36.562 ms result=0 4 bytes from 00:12:47:5c:be:6a seq_no=1313822285 time=31.758 ms result=0 4 bytes from 00:12:47:5c:be:6a seq_no=1313822285 time=42.943 ms result=0 # sudo l2ping -a Sh4d03_PDA -c 4 44 bytes from Sh4d03_PDA seq_no=0 time=31.945 ms result=0 44 bytes from Sh4d03_PDA seq_no=1 time=43.630 ms result=0 44 bytes from Sh4d03_PDA seq_no=2 time=31.823 ms result=0 44 bytes from Sh4d03_PDA seq_no=3 time=34.018 ms result=0 Now I figure it's time I should pair my devices, so firstly I add the following entries into /etc/bluetooth/hcsecd.conf: device { bdaddr 00:12:47:6c:be:6a name "Sh4d03_Mobile" key nokey; pin "1777"; } device { bdaddr Sh4d03_PDA name "Sh4d03_PDA" key nokey; pin "1777"; } I then added the line 'hcsecd_enable="YES"' to my /etc/rc.conf. I can't remember whether this process automagically started but while writing this I kill -9'd the process and started it manually like so: # hcsecd -f /etc/bluetooth/hcsecd.conf # ps auxw | grep hcsecd root 18341 0.0 0.1 1432 720 ?? Is 4:46PM 0:00.00 hcsecd -f /etc/bluetooth/hcsecd.conf Next I used sdpcontrol to browse the services of the PDA: # sdpcontrol -a Sh4d03_PDA browse Record Handle: 0x00010000 Service Class ID List: GN (0x1117) Protocol Descriptor List: L2CAP (0x0100) Protocol specific parameter #1: u/int/uuid16 15 BNEP (0x000f) Protocol specific parameter #1: u/int/uuid16 256 Protocol specific parameter #2: 0x09 0x08 00 0x09 0x08 0x06 Bluetooth Profile Descriptor List: GN (0x1117) ver. 1.0 Record Handle: 0x00010001 Service Class ID List: PANU (0x1115) Protocol Descriptor List: L2CAP (0x0100) Protocol specific parameter #1: u/int/uuid16 15 BNEP (0x000f) Protocol specific parameter #1: u/int/uuid16 256 Protocol specific parameter #2: 0x09 0x08 00 0x09 0x08 0x06 Bluetooth Profile Descriptor List: PANU (0x1115) ver. 1.0 Record Handle: 0x00010002 Service Class ID List: Serial Port (0x1101) Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 1 Bluetooth Profile Descriptor List: Serial Port (0x1101) ver. 1.0 Record Handle: 0x00010003 Service Class ID List: OBEX Object Push (0x1105) Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 2 OBEX (0x0008) Bluetooth Profile Descriptor List: OBEX Object Push (0x1105) ver. 1.0 Record Handle: 0x00010004 Service Class ID List: OBEX File Transfer (0x1106) Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 3 OBEX (0x0008) Bluetooth Profile Descriptor List: OBEX File Transfer (0x1106) ver. 1.0 Record Handle: 0x00010005 Service Class ID List: Headset Audio Gateway (0x1112) Generic Audio (0x1203) Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 4 Bluetooth Profile Descriptor List: Headset (0x1108) ver. 1.1 And then the same for the Mobile Phone: # sdpcontrol -a 00:12:47:6c:be:6a browse Could not execute command "browse". Host is down Ah, the first sign of trouble. I stopped working on the Phone from here on but would appreciate any input on a possible cause. I've previously had this Phone working with (I think) FreeBSD - however it *may* have been when I was still using Gentoo. Back to the PDA - I can see the services offered by the PDA so I installed obexapp and tried to connect: # cd /usr/ports/comms/obexapp # make install clean # obexapp -c -a Sh4d03_PDA -C 1 This looked promising because the PDA then asked me for a pass key - I entered the same as I entered in the hcsecd.conf and hit ok, but obexapp simply dropped to a new line where I believe I should have received the obexftp prompt or something similar. My hcidump -x of this connection is as follows: Before running obexapp: p# hcidump -x HCIDump - HCI packet analyzer ver 1.5 device: any snap_len: 65535 filter: 0xffffffff After starting obexapp, before entering code into PDA: < HCI Command: Create Connection(0x01|0x0005) plen 13 68 75 1A 18 10 00 18 CC 00 00 00 00 00 > HCI Event: Command Status(0x0f) plen 4 00 01 05 04 > HCI Event: Connect Complete(0x03) plen 11 00 2B 00 68 75 1A 18 10 00 01 00 < HCI Command: Write Link Policy Settings(0x02|0x000d) plen 4 2B 00 0E 00 < ACL data: handle 0x002b flags 0x02 dlen 12 L2CAP(s): Connect req: psm 3 scid 0x006b > HCI Event: Number of Completed Packets(0x13) plen 5 01 2B 00 01 00 > HCI Event: Max Slots Change(0x1b) plen 3 2B 00 05 > HCI Event: Command Complete(0x0e) plen 6 01 0D 08 00 2B 00 > ACL data: handle 0x002b flags 0x02 dlen 16 L2CAP(s): Connect rsp: dcid 0x0041 scid 0x006b result 0 status 0 < ACL data: handle 0x002b flags 0x02 dlen 12 L2CAP(s): Config req: dcid 0x0041 flags 0x0000 clen 0 > ACL data: handle 0x002b flags 0x02 dlen 16 L2CAP(s): Config req: dcid 0x006b flags 0x0000 clen 4 MTU 1691 < ACL data: handle 0x002b flags 0x02 dlen 14 L2CAP(s): Config rsp: scid 0x0041 flags 0x0000 result 0 clen 0 > HCI Event: Number of Completed Packets(0x13) plen 5 01 2B 00 01 00 > ACL data: handle 0x002b flags 0x02 dlen 14 L2CAP(s): Config rsp: scid 0x006b flags 0x0000 result 0 clen 0 < ACL data: handle 0x002b flags 0x02 dlen 8 L2CAP(d): cid 0x41 len 4 [psm 3] RFCOMM(s): SABM: cr 1 dlci 0 pf 1 ilen 0 fcs 0x1c > HCI Event: Number of Completed Packets(0x13) plen 5 01 2B 00 01 00 > HCI Event: Number of Completed Packets(0x13) plen 5 01 2B 00 01 00 > ACL data: handle 0x002b flags 0x02 dlen 8 L2CAP(d): cid 0x6b len 4 [psm 3] RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7 < ACL data: handle 0x002b flags 0x02 dlen 18 L2CAP(d): cid 0x41 len 14 [psm 3] RFCOMM(s): PN CMD: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_len 8 dlci 2 frame_type 0 credit_flow 15 pri 7 ack_timer 0 frame_size 667 max_retrans 0 credits 7 > HCI Event: Number of Completed Packets(0x13) plen 5 01 2B 00 01 00 > ACL data: handle 0x002b flags 0x02 dlen 18 L2CAP(d): cid 0x6b len 14 [psm 3] RFCOMM(s): PN RSP: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_len 8 dlci 2 frame_type 0 credit_flow 14 pri 7 ack_timer 0 frame_size 660 max_retrans 0 credits 7 < ACL data: handle 0x002b flags 0x02 dlen 8 L2CAP(d): cid 0x41 len 4 [psm 3] RFCOMM(s): SABM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x59 > HCI Event: Number of Completed Packets(0x13) plen 5 01 2B 00 01 00 After entering code into PDA: > HCI Event: PIN Code Request(0x16) plen 6 68 75 1A 18 10 00 < HCI Command: PIN Code Request Negative Reply(0x01|0x000e) plen 6 68 75 1A 18 10 00 > HCI Event: Command Complete(0x0e) plen 10 01 0E 04 00 68 75 1A 18 10 00 > HCI Event: Disconn Complete(0x05) plen 4 00 2A 00 05 From this point on I'm stuck. Googling 'PIN Code Request Negative Reply' didn't give me much useful information. Any assistance would be greatly appreciated. I've been very verbose in the information I've provided so hopefully I've given all the required details. When the journey is over I'll be documenting and posting to my website what was necessary to get to where I wanted to be with Bluetooth, my phone, my PDA, my laptop and FreeBSD. Kind Regards, Sh4d03 From owner-freebsd-bluetooth@FreeBSD.ORG Mon Apr 23 18:54:00 2007 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 820A916A401 for ; Mon, 23 Apr 2007 18:54:00 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.245]) by mx1.freebsd.org (Postfix) with ESMTP id C9F6613C4F3 for ; Mon, 23 Apr 2007 18:53:59 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: by an-out-0708.google.com with SMTP id c24so2017109ana for ; Mon, 23 Apr 2007 11:53:59 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=XctebP2TClQ4PryXByxM1NxJ7XFm0IIwJwe1NyIh23SzvnSzn0h/rgFEeyas6ILIKGye1RXNvHCD3n1FtY5z+CgpMqhTJe5ML+1CkYLxMIoLzXCdxoJflsk7HJz5J89hy8KUhy7uCoqZp+M1jTXermB8Fvu0LO89uAF0dIm5VHc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=RY7PAjIFrqt2oG6tsM8Q5nuktU2f18O2G5Zd+Yd7MK8p3IyxYjywVvaxMBWqMAeQFdy8FXjaSbW2pAsGlyoffXUXHKBNcI8rwGXddzTCnsU/o1KIZCIUTDMowniLYWupDPCSOVie1io0A1/xqMxka+nVjaKLpP2iQgQx3+xzywQ= Received: by 10.100.163.12 with SMTP id l12mr3947945ane.1177354438822; Mon, 23 Apr 2007 11:53:58 -0700 (PDT) Received: by 10.100.111.18 with HTTP; Mon, 23 Apr 2007 11:53:58 -0700 (PDT) Message-ID: Date: Mon, 23 Apr 2007 11:53:58 -0700 From: "Maksim Yevmenkin" To: Sh4d03 In-Reply-To: <462C5A20.3030300@shadow-security.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <462C5A20.3030300@shadow-security.net> Cc: freebsd-bluetooth@freebsd.org Subject: Re: Creating a PAN with Thinkpad R51, Samsung D500 and iPaq RX4240 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, 23 Apr 2007 18:54:00 -0000 On 4/23/07, Sh4d03 wrote: > Hello all, > > Ultimately I want to be able to connect my Laptop, PDA and Mobile > together to share/synchronise appointments and contacts - the usual guff. > > My Hardware is as follows: > > IBM Thinkpad R51 > USB Bluetooth Adapter (unknown brand) > Samsung D500 Mobile Phone (Cellular) > HP iPaq RX4240 Personal Digital Assistant > > My Software (so far): > > FreeBSD 6.2-STABLE > obexapp-1.4.5 > openobex-1.3 > > > I've read/followed the handbook section for Bluetooth and accomplished > the following so far: > > I've loaded the Kernel Module > > # kldload ng_ubt > > I've plugged in my USB Dongle and received the following in dmesg: > > ubt0: vendor 0x0a12 product 0x0001, rev 2.00/15.93, addr 3 > ubt0: vendor 0x0a12 product 0x0001, rev 2.00/15.93, addr 3 > ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 > ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3; > wMaxPacketSize=49; nframes=6, buffer size=294 > > I've copied /usr/share/examples/netgraph/bluetooth/rc.bluetooth to > /etc/rc.bluetooth - despite 6.1 and above apparently being able to start > bluetooth automagically. > > Now I run 'hccontrol -n ubt0hci inquiry' and receive: > > # hccontrol -n ubt0hci inquiry > Inquiry result, num_responses=1 > Inquiry result #0 > BD_ADDR: 00:12:47:5c:be:6a > Page Scan Rep. Mode: 0x1 > Page Scan Period Mode: 00 > Page Scan Mode: 00 > Class: 52:02:04 > Clock offset: 0x15e3 > Inquiry result, num_responses=1 > Inquiry result #0 > BD_ADDR: Sh4d03_PDA > Page Scan Rep. Mode: 00 > Page Scan Period Mode: 0x2 > Page Scan Mode: 00 > Class: 32:01:10 > Clock offset: 0x59fd > Inquiry complete. Status: No error [00] > # > > Next, to find out whether the first entry is really my phone I run > 'hccontrol -n ubt0hci remote_name_request 00:12:47:5c:be:6a' > > # hccontrol -n ubt0hci remote_name_request 00:12:47:5c:be:6a > BD_ADDR: 00:12:47:5c:be:6a > Name: Sh4d03_Mobile > > Yep, it sure is. > > Next, I do 'hccontrol -n ubt0hci read_connection_list' and receive only > the column headings - i.e. no currently open connections, which would > make sense - right? > > Next, I attempt an l2ping to both devices: > > # sudo l2ping -a 00:12:47:5c:be:6a -c 4 > 4 bytes from 00:12:47:5c:be:6a seq_no=1313822285 time=560.831 ms result=0 > 4 bytes from 00:12:47:5c:be:6a seq_no=1313822285 time=36.562 ms result=0 > 4 bytes from 00:12:47:5c:be:6a seq_no=1313822285 time=31.758 ms result=0 > 4 bytes from 00:12:47:5c:be:6a seq_no=1313822285 time=42.943 ms result=0 > > # sudo l2ping -a Sh4d03_PDA -c 4 > 44 bytes from Sh4d03_PDA seq_no=0 time=31.945 ms result=0 > 44 bytes from Sh4d03_PDA seq_no=1 time=43.630 ms result=0 > 44 bytes from Sh4d03_PDA seq_no=2 time=31.823 ms result=0 > 44 bytes from Sh4d03_PDA seq_no=3 time=34.018 ms result=0 everything until here looks just fine. > > Now I figure it's time I should pair my devices, so firstly I add the > following entries into /etc/bluetooth/hcsecd.conf: > > device { > bdaddr 00:12:47:6c:be:6a > name "Sh4d03_Mobile" > key nokey; > pin "1777"; > } > > device { > bdaddr Sh4d03_PDA > name "Sh4d03_PDA" > key nokey; > pin "1777"; > } your /etc/bluetooth/hcsecd.conf entries are wrong: 1) you have missed the ';' after "bdaddr 00:12:47:6c:be:6a" and "name ."Sh4d03_Mobile"" 2) you can _not_ use symbolic names in bdaddr, i.e. "bdaddr Sh4d03_PDA" is wrong > I then added the line 'hcsecd_enable="YES"' to my /etc/rc.conf. I can't > remember whether this process automagically started but while writing > this I kill -9'd the process and started it manually like so: > > # hcsecd -f /etc/bluetooth/hcsecd.conf > # ps auxw | grep hcsecd > root 18341 0.0 0.1 1432 720 ?? Is 4:46PM 0:00.00 hcsecd -f > /etc/bluetooth/hcsecd.conf > > > Next I used sdpcontrol to browse the services of the PDA: > > # sdpcontrol -a Sh4d03_PDA browse > > Record Handle: 0x00010000 > Service Class ID List: > GN (0x1117) > Protocol Descriptor List: > L2CAP (0x0100) > Protocol specific parameter #1: u/int/uuid16 15 > BNEP (0x000f) > Protocol specific parameter #1: u/int/uuid16 256 > Protocol specific parameter #2: 0x09 0x08 00 0x09 0x08 > 0x06 > Bluetooth Profile Descriptor List: > GN (0x1117) ver. 1.0 > > Record Handle: 0x00010001 > Service Class ID List: > PANU (0x1115) > Protocol Descriptor List: > L2CAP (0x0100) > Protocol specific parameter #1: u/int/uuid16 15 > BNEP (0x000f) > Protocol specific parameter #1: u/int/uuid16 256 > Protocol specific parameter #2: 0x09 0x08 00 0x09 0x08 > 0x06 > Bluetooth Profile Descriptor List: > PANU (0x1115) ver. 1.0 > > Record Handle: 0x00010002 > Service Class ID List: > Serial Port (0x1101) > Protocol Descriptor List: > L2CAP (0x0100) > RFCOMM (0x0003) > Protocol specific parameter #1: u/int8/bool 1 > Bluetooth Profile Descriptor List: > Serial Port (0x1101) ver. 1.0 > > Record Handle: 0x00010003 > Service Class ID List: > OBEX Object Push (0x1105) > Protocol Descriptor List: > L2CAP (0x0100) > RFCOMM (0x0003) > Protocol specific parameter #1: u/int8/bool 2 > OBEX (0x0008) > Bluetooth Profile Descriptor List: > OBEX Object Push (0x1105) ver. 1.0 > > Record Handle: 0x00010004 > Service Class ID List: > OBEX File Transfer (0x1106) > Protocol Descriptor List: > L2CAP (0x0100) > RFCOMM (0x0003) > Protocol specific parameter #1: u/int8/bool 3 > OBEX (0x0008) > Bluetooth Profile Descriptor List: > OBEX File Transfer (0x1106) ver. 1.0 > > Record Handle: 0x00010005 > Service Class ID List: > Headset Audio Gateway (0x1112) > Generic Audio (0x1203) > Protocol Descriptor List: > L2CAP (0x0100) > RFCOMM (0x0003) > Protocol specific parameter #1: u/int8/bool 4 > Bluetooth Profile Descriptor List: > Headset (0x1108) ver. 1.1 looks fine > > > And then the same for the Mobile Phone: > > # sdpcontrol -a 00:12:47:6c:be:6a browse > Could not execute command "browse". Host is down > > Ah, the first sign of trouble. I stopped working on the Phone from here > on but would appreciate any input on a possible cause. I've previously > had this Phone working with (I think) FreeBSD - however it *may* have > been when I was still using Gentoo. is bluetooth on the phone? have you tried to execute sdpcontrol one more time? sometimes phones miss initial page request and it causes 'host down' error (basically baseband connection can not be established) > Back to the PDA - I can see the services offered by the PDA so I > installed obexapp and tried to connect: > > # cd /usr/ports/comms/obexapp > # make install clean > > > # obexapp -c -a Sh4d03_PDA -C 1 > > This looked promising because the PDA then asked me for a pass key - I > entered the same as I entered in the hcsecd.conf and hit ok, but obexapp > simply dropped to a new line where I believe I should have received the > obexftp prompt or something similar. > > My hcidump -x of this connection is as follows: > > > Before running obexapp: > > p# hcidump -x > HCIDump - HCI packet analyzer ver 1.5 > device: any snap_len: 65535 filter: 0xffffffff > > > After starting obexapp, before entering code into PDA: > > > < HCI Command: Create Connection(0x01|0x0005) plen 13 > 68 75 1A 18 10 00 18 CC 00 00 00 00 00 > > HCI Event: Command Status(0x0f) plen 4 > 00 01 05 04 > > HCI Event: Connect Complete(0x03) plen 11 > 00 2B 00 68 75 1A 18 10 00 01 00 > < HCI Command: Write Link Policy Settings(0x02|0x000d) plen 4 > 2B 00 0E 00 > < ACL data: handle 0x002b flags 0x02 dlen 12 > L2CAP(s): Connect req: psm 3 scid 0x006b > > HCI Event: Number of Completed Packets(0x13) plen 5 > 01 2B 00 01 00 > > HCI Event: Max Slots Change(0x1b) plen 3 > 2B 00 05 > > HCI Event: Command Complete(0x0e) plen 6 > 01 0D 08 00 2B 00 > > ACL data: handle 0x002b flags 0x02 dlen 16 > L2CAP(s): Connect rsp: dcid 0x0041 scid 0x006b result 0 status 0 > < ACL data: handle 0x002b flags 0x02 dlen 12 > L2CAP(s): Config req: dcid 0x0041 flags 0x0000 clen 0 > > ACL data: handle 0x002b flags 0x02 dlen 16 > L2CAP(s): Config req: dcid 0x006b flags 0x0000 clen 4 > MTU 1691 > < ACL data: handle 0x002b flags 0x02 dlen 14 > L2CAP(s): Config rsp: scid 0x0041 flags 0x0000 result 0 clen 0 > > HCI Event: Number of Completed Packets(0x13) plen 5 > 01 2B 00 01 00 > > ACL data: handle 0x002b flags 0x02 dlen 14 > L2CAP(s): Config rsp: scid 0x006b flags 0x0000 result 0 clen 0 > < ACL data: handle 0x002b flags 0x02 dlen 8 > L2CAP(d): cid 0x41 len 4 [psm 3] > RFCOMM(s): SABM: cr 1 dlci 0 pf 1 ilen 0 fcs 0x1c > > HCI Event: Number of Completed Packets(0x13) plen 5 > 01 2B 00 01 00 > > HCI Event: Number of Completed Packets(0x13) plen 5 > 01 2B 00 01 00 > > ACL data: handle 0x002b flags 0x02 dlen 8 > L2CAP(d): cid 0x6b len 4 [psm 3] > RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7 > < ACL data: handle 0x002b flags 0x02 dlen 18 > L2CAP(d): cid 0x41 len 14 [psm 3] > RFCOMM(s): PN CMD: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_len 8 > dlci 2 frame_type 0 credit_flow 15 pri 7 ack_timer 0 frame_size > 667 max_retrans 0 credits 7 > > HCI Event: Number of Completed Packets(0x13) plen 5 > 01 2B 00 01 00 > > ACL data: handle 0x002b flags 0x02 dlen 18 > L2CAP(d): cid 0x6b len 14 [psm 3] > RFCOMM(s): PN RSP: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_len 8 > dlci 2 frame_type 0 credit_flow 14 pri 7 ack_timer 0 frame_size > 660 max_retrans 0 credits 7 > < ACL data: handle 0x002b flags 0x02 dlen 8 > L2CAP(d): cid 0x41 len 4 [psm 3] > RFCOMM(s): SABM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x59 > > HCI Event: Number of Completed Packets(0x13) plen 5 > 01 2B 00 01 00 > > > After entering code into PDA: > > > > HCI Event: PIN Code Request(0x16) plen 6 > 68 75 1A 18 10 00 > < HCI Command: PIN Code Request Negative Reply(0x01|0x000e) plen 6 > 68 75 1A 18 10 00 > > HCI Event: Command Complete(0x0e) plen 10 > 01 0E 04 00 68 75 1A 18 10 00 > > HCI Event: Disconn Complete(0x05) plen 4 > 00 2A 00 05 yes, that is because your /etc/bluetooth/hcsecd.conf is screwed up > From this point on I'm stuck. Googling 'PIN Code Request Negative > Reply' didn't give me much useful information. > > Any assistance would be greatly appreciated. I've been very verbose in > the information I've provided so hopefully I've given all the required > details. fix the hcsecd.conf and it should work. > When the journey is over I'll be documenting and posting to my website > what was necessary to get to where I wanted to be with Bluetooth, my > phone, my PDA, my laptop and FreeBSD. sigh... i wish people would stop putting freebsd/bluetooth stuff onto their own web sites and instead put it info the freebsd handbook. thanks, max p.s. bluetooth pan is not supported under freebsd From owner-freebsd-bluetooth@FreeBSD.ORG Mon Apr 23 19:07:02 2007 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7DF2E16A403 for ; Mon, 23 Apr 2007 19:07:02 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from mh1.centtech.com (moat3.centtech.com [64.129.166.50]) by mx1.freebsd.org (Postfix) with ESMTP id 5257813C44C for ; Mon, 23 Apr 2007 19:07:00 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from neutrino.centtech.com (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.8/8.13.8) with ESMTP id l3NJ6xNd052037; Mon, 23 Apr 2007 14:06:59 -0500 (CDT) (envelope-from anderson@freebsd.org) Message-ID: <462D03D3.9040908@freebsd.org> Date: Mon, 23 Apr 2007 14:06:59 -0500 From: Eric Anderson User-Agent: Thunderbird 2.0.0.0 (X11/20070420) MIME-Version: 1.0 To: Maksim Yevmenkin References: <462C5A20.3030300@shadow-security.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.88.4/3151/Mon Apr 23 11:11:26 2007 on mh1.centtech.com X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=8.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.6 X-Spam-Checker-Version: SpamAssassin 3.1.6 (2006-10-03) on mh1.centtech.com Cc: freebsd-bluetooth@freebsd.org Subject: Re: Creating a PAN with Thinkpad R51, Samsung D500 and iPaq RX4240 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, 23 Apr 2007 19:07:02 -0000 On 04/23/07 13:53, Maksim Yevmenkin wrote: > On 4/23/07, Sh4d03 wrote: >> Hello all, >> >> Ultimately I want to be able to connect my Laptop, PDA and Mobile >> together to share/synchronise appointments and contacts - the usual guff. [..snip..] >> When the journey is over I'll be documenting and posting to my website >> what was necessary to get to where I wanted to be with Bluetooth, my >> phone, my PDA, my laptop and FreeBSD. > > sigh... i wish people would stop putting freebsd/bluetooth stuff onto > their own web sites and instead put it info the freebsd handbook. > > thanks, > max Putting it into the handbook means editing the SGML and submitting a patch (if it didn't, then doc/src committers would just get the data from the web page and check it in, right?). Most of the people writing up docs are writing them because they took notes, and simply converted the notes to html, often using a blog or wiki, which is a zero-brain usage activity. That's important because these aren't people who are kernel coders, etc, they are just trying to make something work, usually a 'utility' feature like syncing a device, making a ppp connection, etc, which they are doing for its function, and don't really have a lot of interest in making FreeBSD doc pages. I'm not saying I disagree, I'm just saying the person documenting it really should be someone who enjoys doing doc work (like the freebsd-doc@ team I suppose), or the maintainer of the code. The user has done the painful work, now someone with SGML foo should finish it and thank the user for writing it up at all. Eric From owner-freebsd-bluetooth@FreeBSD.ORG Wed Apr 25 15:10:07 2007 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B25E216A407 for ; Wed, 25 Apr 2007 15:10:07 +0000 (UTC) (envelope-from tscmga@gmail.com) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.226]) by mx1.freebsd.org (Postfix) with ESMTP id 72C4413C459 for ; Wed, 25 Apr 2007 15:10:07 +0000 (UTC) (envelope-from tscmga@gmail.com) Received: by nz-out-0506.google.com with SMTP id r28so338505nza for ; Wed, 25 Apr 2007 08:10:06 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:from:reply-to:organization:to:subject:date:user-agent:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=F4YvJvVOcAuTbReoj/UPxNUnv6Urc3r5V3Y49XrXPv06+IRGCuQFRKsvOkSt1XG1tNCodg11SqLCmWyDvwm508ggsn1bTOBeEbFYmahkp1uFo8OAM1RCVUxAmGR9iqrLeZfSieypA8rHdhcHU5Bn7jUNEEWz/p1SyBXJ4NBk6JE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:from:reply-to:organization:to:subject:date:user-agent:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=h2JSyTt92UamMA0+kAMtZYmhgUkh69PUKYPESJHEhQEcyeXwbfMa7KSj6GzVkElT06DTtTCM9sE+/qLFGO5jdnivwLIDKYAEtbQSaNa7Ut8hwDluclOgBlU04RjoCqpfokrZBwgwO1T5MFsvQ0n+eM7/SVMCpl62lPOhLPL6+kA= Received: by 10.114.12.9 with SMTP id 9mr210157wal.1177513806150; Wed, 25 Apr 2007 08:10:06 -0700 (PDT) Received: from ?192.168.1.11? ( [58.38.0.253]) by mx.google.com with ESMTP id m28sm398668poh.2007.04.25.08.10.04; Wed, 25 Apr 2007 08:10:05 -0700 (PDT) From: zhengzhi Organization: none To: freebsd-bluetooth@freebsd.org Date: Wed, 25 Apr 2007 23:13:37 +0000 User-Agent: KMail/1.8.2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200704252313.37725.tscmga@gmail.com> Subject: Is it easy to write an program to make FreeBSD supoort Headset ? X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: tscmga@gmail.com List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Apr 2007 15:10:07 -0000 Hi. I want to use my headset in FreeBSD now. I 've read some documents about bluetooth , headset profile .Headset Control is the higher level layer of SDP and RFCOMM ,and not complex.FreeBSD supports SDP and RFCOMM. So What I have to do is implement the Headset Control layer and wrap it as a audio device ? From owner-freebsd-bluetooth@FreeBSD.ORG Wed Apr 25 16:55:15 2007 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C10C516A404 for ; Wed, 25 Apr 2007 16:55:15 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.247]) by mx1.freebsd.org (Postfix) with ESMTP id 80EA713C48C for ; Wed, 25 Apr 2007 16:55:15 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: by an-out-0708.google.com with SMTP id c24so145574ana for ; Wed, 25 Apr 2007 09:55:14 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=fyh8akt3CT7MPlCeB7Mt1WEddrx1j1qo0KWug5BeHY5r+Ax5E9hoUFT8dGi+6kfcK6O6E7i2JQpelyVWAoExLxNOV5oDJh+z32HjhKGMvZ3n5GZQhbmDb0EDCN+F/kwCwOAGzn6f4jlQ/as3diejs9LsvW0DnxbSkDwqDuQulKg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=XLFdgwa6fXBZxWqVeICRKP+fkU/KxD9fVbAH6EEL37jXBalnnBU6Vz/ohoceP70CP8yRHH126G0AWd6QUDGUyyvqJD8pgGif0gSN5EenNOivQYvAPk0MVAktZremZsHg5PANCGVoEfBNFIg+4LtjIesH33V/RtZn3jyYXJKFAJw= Received: by 10.100.93.5 with SMTP id q5mr366380anb.1177520114025; Wed, 25 Apr 2007 09:55:14 -0700 (PDT) Received: by 10.100.111.18 with HTTP; Wed, 25 Apr 2007 09:55:13 -0700 (PDT) Message-ID: Date: Wed, 25 Apr 2007 09:55:13 -0700 From: "Maksim Yevmenkin" To: tscmga@gmail.com In-Reply-To: <200704252313.37725.tscmga@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200704252313.37725.tscmga@gmail.com> Cc: freebsd-bluetooth@freebsd.org Subject: Re: Is it easy to write an program to make FreeBSD supoort Headset ? 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, 25 Apr 2007 16:55:15 -0000 On 4/25/07, zhengzhi wrote: > Hi. > I want to use my headset in FreeBSD now. I 've read some documents about > bluetooth , headset profile .Headset Control is the higher level layer of > SDP and RFCOMM ,and not complex.FreeBSD supports SDP and RFCOMM. > So What I have to do is implement the Headset Control layer and wrap it as > a audio device ? 1) sco support in ng_ubt(4) - some code exists but was not committed 2) sco sockets support - some code exists but was not committed 3) figure out a clean and good way to plug bluetooth sco into audio subsystem 4) actually implement headset profile item 1 to 3 are definitely kernel work. implementation of item 4 largely depends on implementation of item 3 and may or may not be in userspace. thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Wed Apr 25 18:22:45 2007 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 415A016A40E for ; Wed, 25 Apr 2007 18:22:45 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.241]) by mx1.freebsd.org (Postfix) with ESMTP id E792E13C487 for ; Wed, 25 Apr 2007 18:22:44 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: by an-out-0708.google.com with SMTP id c24so179924ana for ; Wed, 25 Apr 2007 11:22:44 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=j9YvjQUX0whRw4RaCfZR0crwmuFqkZmzt1NeIUnrSRdBVF5yh4iPB1wu4riukd+atl/reuiB7Qp8Hb5TP3yXaznd8/i+KPoUXtmK8X8HbP6TJFZExdru19F2J9ItmPdPjeKEx5KmI+WFtS/qApUaQz0hJIX9swzp4xuwOad3i7c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=l5qCVvS6eP1X/45Upezwx39v/UmsDv9iDi64qixSIBgn/vGnzFgeOMiEIHrLkOPzSxOs5njHnOjzIQf7U/EmoeNAvsFVMDu30NlqeXUJ6cmRKi1P9HxlihfgME6bvvokDnn+adwlcbuxS4kxAOPLhRJWxJ2ua7h5XRQ2FMgfs4M= Received: by 10.100.190.8 with SMTP id n8mr416032anf.1177525363951; Wed, 25 Apr 2007 11:22:43 -0700 (PDT) Received: by 10.100.111.18 with HTTP; Wed, 25 Apr 2007 11:22:43 -0700 (PDT) Message-ID: Date: Wed, 25 Apr 2007 11:22:43 -0700 From: "Maksim Yevmenkin" To: "freebsd-bluetooth@freebsd.org" MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: obexapp-1.4.6 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, 25 Apr 2007 18:22:45 -0000 Dear Bluetooth Users, obexapp-1.4.6 is available at http://www.geocities.com/m_evmenkin/obexapp-1.4.6.tar.gz this release includes fixes and improvements from Iain Hibbert who is actively working on Bluetooth support in NetBSD. there should not be any user visible changes, except -a and -A command options not work in slightly different way. please read man page for more details. please give it a try and let me know if you have any problems. thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Thu Apr 26 17:02:07 2007 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1946C16A40A for ; Thu, 26 Apr 2007 17:02:07 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.245]) by mx1.freebsd.org (Postfix) with ESMTP id C75E513C48A for ; Thu, 26 Apr 2007 17:02:06 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: by an-out-0708.google.com with SMTP id c24so320609ana for ; Thu, 26 Apr 2007 10:02:06 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=uBexvmuPd0sVqB9jl+CqP0P1dlT0VeVQTVwfAvLUsu4PSXg4M179Ko5lzqUx2ndmJMUVL5Mf1Sl7vb/ePZv40aiIT6hhj+UizUMaJlsavNYKXqbJcbzOl+n61VoD53tPqEHoN0Rln6vdOiP9YaOMzzXg4IBkUcqUBcRP9SqNV4c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=juDLup6ssGWc7+I9CpCHwfMbk6wFwFSsaMIZFzmAn9DSRgfF52yIG8qxBsHF+lWUhgQa2z1rkj8OC0yiywr5mp+dhObj82eZzGPIJOoFksUs9QGWB7ehW+rsX/P/RVKnBBVirAY/JFPiK9rGkUrSjKK3yKoQJTMUnkeTTBdAdbc= Received: by 10.100.133.9 with SMTP id g9mr1290729and.1177606925693; Thu, 26 Apr 2007 10:02:05 -0700 (PDT) Received: by 10.100.111.18 with HTTP; Thu, 26 Apr 2007 10:02:05 -0700 (PDT) Message-ID: Date: Thu, 26 Apr 2007 10:02:05 -0700 From: "Maksim Yevmenkin" To: "=?GB2312?B?t73Wvg==?=" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-2022-JP; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200704252313.37725.tscmga@gmail.com> Cc: "freebsd-bluetooth@freebsd.org" Subject: Re: Is it easy to write an program to make FreeBSD supoort Headset ? 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, 26 Apr 2007 17:02:07 -0000 On 4/26/07, $BJ};V(B wrote: > "Isochronous USB transfers are broken.This means that the USB > device will not be able to transfer SCO date (voice)." (from man 4 > ng_utb) . > > Do you means that these functions > "ubt_isoc_in_start" > "ubt_isoc_in_complete" > "ubt_isoc_in_complete2" > "ubt_isoc_out_start" > "ubt_isoc_out_complete" > "ubt_isoc_out_complete2" > in /usr/src/sys/netgraph/bluetooth/drivers/ubt/ng_ubt.c dosen't work > properly? yes. when i initially wrote them, i had very little knowledge about usb isoc. transfers. right now (i'd like to think) i have a better understanding of usb isoc. transfers on freebsd and have some code (locally) that seems to work. > I didn't know the official documents on bluetooth and headset > profile are available freely on www.bluetooth.com but not on > www.bluetooth.org . i not sure what are you saying, but yes, bluetooth profile documents available at http://www.bluetooth.com/Bluetooth/Learn/Technology/Specifications/ and specifically headset http://www.bluetooth.com/NR/rdonlyres/5C0DEE05-84CD-4D79-BD52-7ECA283430A0/981/HSP_SPEC_V11.pdf thanks, max > > > > > > On 4/25/07, Maksim Yevmenkin wrote: > > On 4/25/07, zhengzhi wrote: > > > Hi. > > > I want to use my headset in FreeBSD now. I 've read some documents > > about > > > bluetooth , headset profile .Headset Control is the higher level layer of > > > SDP and RFCOMM ,and not complex.FreeBSD supports SDP and RFCOMM. > > > So What I have to do is implement the Headset Control layer and wrap it > > as > > > a audio device ? > > > > 1) sco support in ng_ubt(4) - some code exists but was not committed > > > > 2) sco sockets support - some code exists but was not committed > > > > 3) figure out a clean and good way to plug bluetooth sco into audio > > subsystem > > > > 4) actually implement headset profile > > > > item 1 to 3 are definitely kernel work. implementation of item 4 > > largely depends on implementation of item 3 and may or may not be in > > userspace. > > > > thanks, > > max > > > From owner-freebsd-bluetooth@FreeBSD.ORG Fri Apr 27 21:55:05 2007 Return-Path: X-Original-To: freebsd-bluetooth@FreeBSD.org Delivered-To: freebsd-bluetooth@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4417216A400 for ; Fri, 27 Apr 2007 21:55:05 +0000 (UTC) (envelope-from lioux@FreeBSD.org) Received: from vette.gigo.com (vette.gigo.com [216.218.228.114]) by mx1.freebsd.org (Postfix) with ESMTP id 2BD7013C44C for ; Fri, 27 Apr 2007 21:55:05 +0000 (UTC) (envelope-from lioux@FreeBSD.org) Received: from 201.24.51.130 (unknown [201.24.51.130]) by vette.gigo.com (Postfix) with ESMTP id 2AC5CD9 for ; Fri, 27 Apr 2007 14:27:28 -0700 (PDT) Received: (qmail 56767 invoked from network); 27 Apr 2007 18:10:37 -0300 Received: from unknown (HELO ?127.0.0.1?) (127.0.0.1) by exxodus.fedaykin.here with SMTP; 27 Apr 2007 18:10:37 -0300 Message-ID: <463266C8.3070606@FreeBSD.org> Date: Fri, 27 Apr 2007 18:10:32 -0300 From: =?UTF-8?B?TcOhcmlvIFPDqXJnaW8gRnVqaWthd2EgRmVycmVpcmE=?= User-Agent: Thunderbird 1.5.0.10 (X11/20070308) MIME-Version: 1.0 To: freebsd-bluetooth@FreeBSD.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: Subject: Is Trendnet TBW-104UB supported? Is it good? X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lioux@FreeBSD.org List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Apr 2007 21:55:05 -0000 Hi, I would like to know if the Trendnet TBW-104UB usb adapter is supported under FreeBSD 6-STABLE e 7. http://www.trendnet.com/products/TBW-104UB.htm Is it a good adapter? It is a Class I Bluetooth v2.0 with EDR. Regards, Mário Ferreira From owner-freebsd-bluetooth@FreeBSD.ORG Fri Apr 27 22:00:27 2007 Return-Path: X-Original-To: freebsd-bluetooth@FreeBSD.org Delivered-To: freebsd-bluetooth@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B456516A406 for ; Fri, 27 Apr 2007 22:00:27 +0000 (UTC) (envelope-from lioux@FreeBSD.org) Received: from vette.gigo.com (vette.gigo.com [216.218.228.114]) by mx1.freebsd.org (Postfix) with ESMTP id A214F13C44C for ; Fri, 27 Apr 2007 22:00:27 +0000 (UTC) (envelope-from lioux@FreeBSD.org) Received: from 201.24.51.130 (unknown [201.24.51.130]) by vette.gigo.com (Postfix) with ESMTP id E1FE6F6 for ; Fri, 27 Apr 2007 15:00:26 -0700 (PDT) Received: (qmail 3605 invoked from network); 27 Apr 2007 18:58:00 -0300 Received: from unknown (HELO ?127.0.0.1?) (127.0.0.1) by exxodus.fedaykin.here with SMTP; 27 Apr 2007 18:58:00 -0300 Message-ID: <463271C4.6040206@FreeBSD.org> Date: Fri, 27 Apr 2007 18:57:24 -0300 From: =?UTF-8?B?TcOhcmlvIFPDqXJnaW8gRnVqaWthd2EgRmVycmVpcmE=?= User-Agent: Thunderbird 1.5.0.10 (X11/20070308) MIME-Version: 1.0 To: freebsd-bluetooth@FreeBSD.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: Subject: Bluetooth headset? X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lioux@FreeBSD.org List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Apr 2007 22:00:27 -0000 Hi, Do bluetooth headsets work under FreeBSD 6 or 7? I would like to use one with skype. Anything I can do to help other than write code? :) I can be the patches guinea pig. Regards, Mário Ferreira From owner-freebsd-bluetooth@FreeBSD.ORG Fri Apr 27 22:10:02 2007 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2827F16A404 for ; Fri, 27 Apr 2007 22:10:02 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.240]) by mx1.freebsd.org (Postfix) with ESMTP id D564113C45B for ; Fri, 27 Apr 2007 22:10:01 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: by an-out-0708.google.com with SMTP id c24so782744ana for ; Fri, 27 Apr 2007 15:10:01 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=B6PeE+eR/D6FH+eNGJUVG0ICopPpBAc+T/J4VfODpr6Z8LHfdAiTvh2nEYmO8P2S0aJO2ralDakwxdPbpH5Cc4zbelxzr2YqcttrHsDnkeIBNN55z42Ug+vLzkymCulI4ZEle8LGCZkGQZAJAkvleROR8THtEEPZ/NaQm9z2FHo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=KgLK+X42wjpTJdLoR0piEOH5q9bXGS++G5s9+U14FeC3DDxUMkMYEVO9+MIbDuGcPWA5QYZscJR4m5VTbx/Ronp6b+H6uXL6XQ3ufMSM4vbtWv+TxJVEyGXwtPLWtAqp2J35pKAkUUPQ6TJKBPtX279SU4XB54U4B3OCHf491LY= Received: by 10.100.154.13 with SMTP id b13mr2264130ane.1177711800924; Fri, 27 Apr 2007 15:10:00 -0700 (PDT) Received: by 10.100.111.18 with HTTP; Fri, 27 Apr 2007 15:10:00 -0700 (PDT) Message-ID: Date: Fri, 27 Apr 2007 15:10:00 -0700 From: "Maksim Yevmenkin" To: lioux@freebsd.org In-Reply-To: <463271C4.6040206@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <463271C4.6040206@FreeBSD.org> Cc: freebsd-bluetooth@freebsd.org Subject: Re: Bluetooth headset? 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: Fri, 27 Apr 2007 22:10:02 -0000 On 4/27/07, M=E1rio S=E9rgio Fujikawa Ferreira wrote: > Hi, > > Do bluetooth headsets work under FreeBSD 6 or 7? I would like to use > one with skype. no > Anything I can do to help other than write code? :) I > can be the patches guinea pig. writing code is the critical thing right now :) thanks, max > > Regards, > M=E1rio Ferreira > _______________________________________________ > 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 Fri Apr 27 22:14:06 2007 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A36D516A400 for ; Fri, 27 Apr 2007 22:14:06 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.241]) by mx1.freebsd.org (Postfix) with ESMTP id 606CD13C45D for ; Fri, 27 Apr 2007 22:14:06 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: by an-out-0708.google.com with SMTP id c24so783569ana for ; Fri, 27 Apr 2007 15:14:05 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=UZ3Ql18nlCUVlvP/RShZV/PYVhkBTr5Y3Sn0l/zuy1LdvvSE+u6U6BfeuJdcJSWEDnHytRYAjPBM0i5cGNI5tm4CX1QwYxTpU9r8ftXeNFGGIPWwLpUoU4rpXp1pzrxn6fjoroRgW4z9Y5JsbEJGUTEbm/EhQUq70okxhyLP5gQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=kImtyKwwHmEmrnsYpvSdW8ES7gKzGI8X6Jehx1dKsw4PhGPkPcStJv3vLZUcsgOTK1HRZzaTJ+xrbGxHCIdQeKaRh+qsTeR4wpD/EFVHelaJfah2DfXj6oMhVD1P2Ppiu8KumaLBySi17danLyPH13UeDX9EnTwwSfQ29zEQLf0= Received: by 10.100.133.9 with SMTP id g9mr2395039and.1177712045278; Fri, 27 Apr 2007 15:14:05 -0700 (PDT) Received: by 10.100.111.18 with HTTP; Fri, 27 Apr 2007 15:14:05 -0700 (PDT) Message-ID: Date: Fri, 27 Apr 2007 15:14:05 -0700 From: "Maksim Yevmenkin" To: lioux@freebsd.org In-Reply-To: <463266C8.3070606@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <463266C8.3070606@FreeBSD.org> Cc: freebsd-bluetooth@freebsd.org Subject: Re: Is Trendnet TBW-104UB supported? Is it good? 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: Fri, 27 Apr 2007 22:14:06 -0000 On 4/27/07, M=E1rio S=E9rgio Fujikawa Ferreira wrote: > Hi, > > I would like to know if the Trendnet TBW-104UB usb adapter is > supported under FreeBSD 6-STABLE e 7. > > http://www.trendnet.com/products/TBW-104UB.htm do not know about this particular model, but i have tbw-101ub (or tbw-102ub?) and it works just fine. so, chances are it will work. thanks, max > > Is it a good adapter? It is a Class I Bluetooth v2.0 with EDR. > > Regards, > M=E1rio Ferreira > _______________________________________________ > 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 Sat Apr 28 03:28:44 2007 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5A21116A401 for ; Sat, 28 Apr 2007 03:28:44 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.243]) by mx1.freebsd.org (Postfix) with ESMTP id 1B95B13C44B for ; Sat, 28 Apr 2007 03:28:43 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: by an-out-0708.google.com with SMTP id c24so832798ana for ; Fri, 27 Apr 2007 20:28:43 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=q5CdC/sMMKswb/5UgLXC4UoR7F3hxngHmJg5L3E8uG3u6BLledR6gPzZQfE8UKguSC1HHFi0oMizpuYnGRAT9DdgOTYzUwdYvt64DYhUiTGLQ4f+jrYDC+UCtOXcuaJLJmMPzHfyGGE0DR+U4yJ9hw6DIWUiiCgQ9ealWT4ITHk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=AB8FGhCINkJxp7rp3NWVWcH7SqGD4KOqKhsDGqwdK21dEuheO2KGbux9PViLLIFxAGwIOE8j29IWMGDo1Fni9K44OvZSUuesGWgHzcP74L5pDKsWzjVJVbcQWwEMMpHNcQtkOj2gxBmUg4JQEtWIPqdKWVssylt4dUud5EPKpbs= Received: by 10.100.190.8 with SMTP id n8mr68604anf.1177730923472; Fri, 27 Apr 2007 20:28:43 -0700 (PDT) Received: by 10.100.111.18 with HTTP; Fri, 27 Apr 2007 20:28:43 -0700 (PDT) Message-ID: Date: Fri, 27 Apr 2007 20:28:43 -0700 From: "Maksim Yevmenkin" To: "Chuan-Heng Hsiao" In-Reply-To: <485337.74158.qm@web54614.mail.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <485337.74158.qm@web54614.mail.yahoo.com> Cc: "freebsd-bluetooth@freebsd.org" Subject: Re: Fw: wii remote on FreeBSD. 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: Sat, 28 Apr 2007 03:28:44 -0000 Hi, cc'd to freebsd-bluetooth for wider audience > I wrote a primitive wii remote driver on FreeBSD > based on your bthidd program. > > There is no one knowing this program yet, but I intend > to release it soon (in next week.) > > Could you tell me what else I should do besides informing > you and retain your copyright claim in every file to fulfill the > patent issue? > > The following video clip may help you what I have done: > http://cns.bu.edu/~chhsiao/bsdmoted/xeyes.mpg looks pretty cool from what i see :) is there a reason you wrote a separate piece of code? is not possible to integrate your work into bthidd(8)? i'm not sure what 'patent issue' are you talking about. i will be more then happy to review and commit your work into freebsd source tree, but you have to release your code under bsd-style license. and, of course, your name and copyright will be kept on all your source files. thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Sat Apr 28 08:36:06 2007 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id ED47E16A402 for ; Sat, 28 Apr 2007 08:36:06 +0000 (UTC) (envelope-from plunky@rya-online.net) Received: from smarthost01.eng.net (smarthost01.eng.net [213.130.146.173]) by mx1.freebsd.org (Postfix) with ESMTP id BB14B13C458 for ; Sat, 28 Apr 2007 08:36:06 +0000 (UTC) (envelope-from plunky@rya-online.net) Received: from netmail01.eng.net ([213.130.128.38] helo=rya-online.net) by smarthost01.eng.net with smtp (Exim 4.62) (envelope-from ) id 1HhiPR-0005Z1-35; Sat, 28 Apr 2007 09:36:05 +0100 Received: (nullmailer pid 7875 invoked by uid 1000); Sat, 28 Apr 2007 08:07:33 -0000 Date: Sat, 28 Apr 2007 09:07:33 +0100 (BST) To: Maksim Yevmenkin In-Reply-To: References: <462C5A20.3030300@shadow-security.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Message-Id: <1177747653.710071.9561.nullmailer@galant.ukfsn.org> From: Iain Hibbert Cc: freebsd-bluetooth@freebsd.org Subject: Bluetooth PAN 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: Sat, 28 Apr 2007 08:36:07 -0000 On Mon, 23 Apr 2007, Maksim Yevmenkin wrote: > p.s. bluetooth pan is not supported under freebsd FWIW there is no reason it should not work, if somebody would write a userland PAN program that works as a bridge between an L2CAP socket and a tap(4) device (or tun(4), I'm not sure of the difference). The BNEP protocol looks very simple (just encapsulate ethernet frames in L2CAP packets) - alas I currently have no hardware that supports PAN profiles otherwise I would write a daemon, maybe I will look into that over the summer.. iain