From owner-freebsd-bluetooth@FreeBSD.ORG Sun May 18 10:47:04 2008 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 7C55E106567A for ; Sun, 18 May 2008 10:47:04 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id 087C68FC13 for ; Sun, 18 May 2008 10:47:02 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (ppp121-45-62-238.lns11.adl2.internode.on.net [121.45.62.238]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id m4IAM3Ve023733 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Sun, 18 May 2008 19:52:04 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: "Maksim Yevmenkin" Date: Sun, 18 May 2008 19:51:52 +0930 User-Agent: KMail/1.9.7 References: <200805141647.m4EGlUP1021019@repoman.freebsd.org> <200805151814.14386.doconnor@gsoft.com.au> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2164479.fP3nVeyr0z"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200805181952.00112.doconnor@gsoft.com.au> X-Spam-Score: -2.212 () BAYES_00,RDNS_DYNAMIC X-Scanned-By: MIMEDefang 2.63 on 203.31.81.10 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: "freebsd-bluetooth@freebsd.org" Subject: Re: cvs commit: src/usr.bin/bluetooth/rfcomm_sppd rfcomm_sppd.1 rfcomm_sppd.c 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, 18 May 2008 10:47:04 -0000 --nextPart2164479.fP3nVeyr0z Content-Type: multipart/mixed; boundary="Boundary-01=_CNAMI8LKV8p4ImY" Content-Transfer-Encoding: 7bit Content-Disposition: inline --Boundary-01=_CNAMI8LKV8p4ImY Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thu, 15 May 2008, Maksim Yevmenkin wrote: > > How hard would it be to have a '-t auto' and have it print out the > > pty it just allocated? It would make it much easier for scripts to > > work if that was possible. > > > > (Maybe just call openpty()?) > > not hard at all. however, how would rfcomm_sppd(1) print tty name if, > say, it was asked to run in background? perhaps it would be better to > teach rfcomm_sppd(1) to work with nmdm(4)? I don't think nmdm would make a difference in this respect. I am thinking of an operating mode where a script or daemon runs when a=20 device associates and sets up channels the user has configured. So the=20 script runs rfcomm_sppd and groks the output to find what PTY has been=20 allocated and creates a symlink to a human understandable name=20 (eg /dev/gps0 or whatever) I have attached a patch which uses openpty() and seems to work fine=20 (tested quickly against my BT GPS unit & phone). If the patch doesn't=20 make it you can get it from=20 http://www.gsoft.com.au/~doconnor/rfcomm_sppd-pty.diff On a related note I find I have to 'kill -9' rfcomm_sppd sometimes if I=20 have connected to the PTY and then disconnected, eg.. > sudo ./rfcomm_sppd -t -a GPS rfcomm_sppd[43683]: Starting on /dev/ttyp5 > sudo cu -l /dev/ttyp5 ~. ^Crfcomm_sppd[43683]: Signal 2 received. Total 1 signals received > sudo cu -l /dev/ttyp5 rfcomm_sppd[43683]: Completed on /dev/ttyp5 I can't reproduce it very often though - I have had it happen quite a=20 bit in the past though. PS please CC me as I am not on the list. =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --Boundary-01=_CNAMI8LKV8p4ImY-- --nextPart2164479.fP3nVeyr0z Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.8 (FreeBSD) iD8DBQBIMANI5ZPcIHs/zowRAlJ2AJsHvdVQWZtLccSzi3TcbLhQTZH+VACeMlwy rFpybRFYSu37JoWFplDEpoU= =VK87 -----END PGP SIGNATURE----- --nextPart2164479.fP3nVeyr0z-- From owner-freebsd-bluetooth@FreeBSD.ORG Mon May 19 10:45:05 2008 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 AE92F10656A8 for ; Mon, 19 May 2008 10:45:05 +0000 (UTC) (envelope-from lsantagostini@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.228]) by mx1.freebsd.org (Postfix) with ESMTP id 5E0628FC36 for ; Mon, 19 May 2008 10:45:04 +0000 (UTC) (envelope-from lsantagostini@gmail.com) Received: by wx-out-0506.google.com with SMTP id h27so1413797wxd.7 for ; Mon, 19 May 2008 03:45:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; bh=Obhnw1qxcRDmZgc7VmT98XULDnzsTmynbrJBLYC4cHg=; b=fZShTp4I2I/hjH//vh2wJQj+CufczirHRGIUQZ2uIVysd/RGocKyKf3g48ok082HRGSN4cT3K9sZGTzViZBkWSyC0UYra0LkBnwmuB0tVOFPomnVB57VX2kv5c3RVILWfGmorQl6quqhyv6JI/9Ro1bT9fSv/HXDXWTsRqzzIEo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=Huxqdkp7nnOpmyiIwBYN97yEqmSP4jOKEVIdLNi41CzGaidoUZeL8mNBKJZva7wMRcAtQjxTK62sRy4sjsF8le4QjGS4Fd7Bqj5FoiBltmqYphegpr5313/WzdXEMsof++VhJiGKJYsGQ2fAsn66d+tZXDDNAQcS6JLzzSSWF1s= Received: by 10.70.14.14 with SMTP id 14mr5687560wxn.81.1211192362107; Mon, 19 May 2008 03:19:22 -0700 (PDT) Received: by 10.70.116.10 with HTTP; Mon, 19 May 2008 03:19:22 -0700 (PDT) Message-ID: <9ab7eeeb0805190319u30ccbeefq1511afa063bd75fe@mail.gmail.com> Date: Mon, 19 May 2008 10:19:22 +0000 From: "Leonardo Santagostini" To: freebsd-bluetooth@freebsd.org MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_15964_1172413.1211192362091" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Problem with a BCM2035B 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: Mon, 19 May 2008 10:45:05 -0000 ------=_Part_15964_1172413.1211192362091 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi List: I was already googling and browsing over Internet about mi problem. Im using FreeBSD 7.0-RELEASE and the problem is that the donlge dont want to work. I tried kldloanding various modeules, here comes my kldstat pcleo# kldstat Id Refs Address Size Name 1 32 0xc0400000 9130cc kernel 2 1 0xc0d14000 ce30 if_wi.ko 3 1 0xc0d21000 14324 snd_hda.ko 4 2 0xc0d36000 4a5ac sound.ko 5 1 0xc0d81000 19f34 if_ral.ko 6 1 0xc0d9b000 80ea28 nvidia.ko 7 2 0xc15aa000 28658 linux.ko 8 1 0xc15d3000 3130 ubtbcmfw.ko 9 1 0xc15d7000 802c ng_ubt.ko 10 6 0xc15e0000 d3a0 netgraph.ko 11 1 0xc15ee000 1bdc wlan_xauth.ko 12 1 0xc15f0000 6a32c acpi.ko 13 4 0xc5529000 2000 ng_bluetooth.ko 14 1 0xc552b000 d000 ng_hci.ko 15 1 0xc5558000 f000 ng_l2cap.ko 16 1 0xc5569000 19000 ng_btsocket.ko 17 1 0xc558b000 4000 ng_socket.ko The /var/log/messages tells: May 19 07:09:47 pcleo root: Unknown USB device: vendor 0x0a5c product 0x2035 bus uhub1 May 19 07:09:47 pcleo kernel: ubt0: on uhub1 May 19 07:09:47 pcleo kernel: ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 May 19 07:09:47 pcleo kernel: ubt0: Interface 1 (alt.config 4) endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=64; nframes=5, buffer size=320 May 19 07:09:47 pcleo root: /etc/rc.d/bluetooth: ERROR: Unable to setup Bluetooth stack for device ubt0 i been trying bcmfw without results, in fact, when i do a ls -l /dev/u* i cant see an ubtbcmfw device created. pcleo# ls -l /dev/u* crw-r--r-- 1 root operator 0, 79 May 19 06:29 /dev/uhid0 crw------- 1 root wheel 0, 77 May 19 06:29 /dev/ukbd0 lrwxr-xr-x 1 root wheel 6 May 19 06:29 /dev/urandom -> random crw-rw---- 1 root operator 0, 38 May 19 06:29 /dev/usb crw-rw---- 1 root operator 0, 37 May 19 06:29 /dev/usb0 crw-rw---- 1 root operator 0, 39 May 19 06:29 /dev/usb1 crw-rw---- 1 root operator 0, 40 May 19 06:29 /dev/usb2 I followed the instructions for dumping my device, here is. If you can help me i will really apreciate it. Thanks for all Sincerelly Leonardo Santagostini ------=_Part_15964_1172413.1211192362091 Content-Type: application/octet-stream; name=init.dump Content-Transfer-Encoding: base64 X-Attachment-Id: f_fgeq8s3r0 Content-Disposition: attachment; filename=init.dump BAAAALsnMUhW3AcAAQMMAAcAAQC7JzFI6vkIAAQOBAEDDAAEAAAAuycxSKUCCQABCRAADQABALsn MUgxFQkABA4KAQkQAAAAAAAAAAQAAAC7JzFI0x4JAAEDEAAPAAEAuycxSH8wCQAEDgwBAxAA//4N AAAAAAAEAAAAuycxSAY5CQABBRAADgABALsnMUjnSwkABA4LAQUQAHkBEAoAAAAFAAAAuycxSD1W CQABGgwBAwcAAQC7JzFIOGcJAAQOBAEaDAAHAAAAuycxSMRvCQABJAwDDAH/BwABALsnMUhWCwoA BA4EASQMAAUAAAC7JzFI+hQKAAEgDAEABwABALsnMUhUswoABA4EASAMAAUAAAC7JzFIE7wKAAEi DAEABwABALsnMUhdVwsABA4EASIMAPwAAAC7JzFIbWwLAAETDPhwY2xlbyAodWJ0MCkAAAAAAGQI KPTzByggsAgoAGQIKGTov78jxwUoVOi/v0jov78BAAAAAGAIKKyasAcyhwQIAGQIKADov78DAAAA AwAAAABkCCj08wcoIKAIKABgCCik6L+/I8cFKJTov78goAgoAQAAAJ/qBSgAAAAA5IQECDKHBAjX 6AUogKAIKPTzByik6L+/FusFKICgCCj08wco5Oi/vzjIBSgEOggoAQAAANTov78BAAAAAAAAAAAA AAABAAAACOm/v796DCj06L+/AGQIKLTpv7/tVBYokOm/vwQAAAAkhwUItOm/vwAAAAAAAAAAkOm/ vwcAAQC7JzFIwhYMAAQOBAETDAA= ------=_Part_15964_1172413.1211192362091-- From owner-freebsd-bluetooth@FreeBSD.ORG Mon May 19 17:32:54 2008 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 24DA91065683 for ; Mon, 19 May 2008 17:32:54 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from fk-out-0910.google.com (fk-out-0910.google.com [209.85.128.187]) by mx1.freebsd.org (Postfix) with ESMTP id A0C2A8FC14 for ; Mon, 19 May 2008 17:32:53 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: by fk-out-0910.google.com with SMTP id k31so2069913fkk.11 for ; Mon, 19 May 2008 10:32:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; 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; bh=eyQBmi+iEzq9pvvD5fM3BdhJFcLs/Uw/jbl1gq7B5oU=; b=jOiwZwykwgrZ9MAub6CzhP6OLgOabX6p+T0Xm89/+B7vbz/EvGnFm1XJiBjY4fWvZa8sUVi+4krDnaKRdTKrX3hyXclYmRd+UVyyk3xjwkppkB3qMvYOBmOl+7uJwHb1eqk5fQPwuEd88XrBHfBcTq7jf2misI5k2geebZNIbFk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=iC8o5hwVdW61EVllxeIxiiJ4Lnuqw3iH2MLwHl2sFcvIJATo400hM0+aHc3zWqRM4UGWBxW3sof1Lx9lZlXlgPGCviAAVs+B8QaSRANlKnX50h+cJ7tJGPzo/8K+DS0v/zkPucdXYp9BQ83ol/zfGFmOoz+G5CXe1oATNath3Q4= Received: by 10.125.133.13 with SMTP id k13mr6235265mkn.25.1211218373264; Mon, 19 May 2008 10:32:53 -0700 (PDT) Received: by 10.86.66.5 with HTTP; Mon, 19 May 2008 10:32:53 -0700 (PDT) Message-ID: Date: Mon, 19 May 2008 10:32:53 -0700 From: "Maksim Yevmenkin" To: "Leonardo Santagostini" In-Reply-To: <9ab7eeeb0805190319u30ccbeefq1511afa063bd75fe@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <9ab7eeeb0805190319u30ccbeefq1511afa063bd75fe@mail.gmail.com> Cc: freebsd-bluetooth@freebsd.org Subject: Re: Problem with a BCM2035B 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: Mon, 19 May 2008 17:32:54 -0000 Hello, > I was already googling and browsing over Internet about mi problem. > Im using FreeBSD 7.0-RELEASE and the problem is that the donlge dont want to > work. > > I tried kldloanding various modeules, here comes my kldstat > pcleo# kldstat > Id Refs Address Size Name > 1 32 0xc0400000 9130cc kernel > 2 1 0xc0d14000 ce30 if_wi.ko > 3 1 0xc0d21000 14324 snd_hda.ko > 4 2 0xc0d36000 4a5ac sound.ko > 5 1 0xc0d81000 19f34 if_ral.ko > 6 1 0xc0d9b000 80ea28 nvidia.ko > 7 2 0xc15aa000 28658 linux.ko > 8 1 0xc15d3000 3130 ubtbcmfw.ko > 9 1 0xc15d7000 802c ng_ubt.ko > 10 6 0xc15e0000 d3a0 netgraph.ko > 11 1 0xc15ee000 1bdc wlan_xauth.ko > 12 1 0xc15f0000 6a32c acpi.ko > 13 4 0xc5529000 2000 ng_bluetooth.ko > 14 1 0xc552b000 d000 ng_hci.ko > 15 1 0xc5558000 f000 ng_l2cap.ko > 16 1 0xc5569000 19000 ng_btsocket.ko > 17 1 0xc558b000 4000 ng_socket.ko looks fine > The /var/log/messages tells: > > May 19 07:09:47 pcleo root: Unknown USB device: vendor 0x0a5c product 0x2035 > bus uhub1 > May 19 07:09:47 pcleo kernel: ubt0: rev 2.00/1.00, addr 3> on uhub1 > May 19 07:09:47 pcleo kernel: ubt0: Interface 0 endpoints: interrupt=0x81, > bulk-in=0x82, bulk-out=0x2 > May 19 07:09:47 pcleo kernel: ubt0: Interface 1 (alt.config 4) endpoints: > isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=64; nframes=5, buffer size=320 > May 19 07:09:47 pcleo root: /etc/rc.d/bluetooth: ERROR: Unable to setup > Bluetooth stack for device ubt0 this does not look good. i been trying bcmfw without results, in fact, when i do a ls -l /dev/u* i > cant see an ubtbcmfw device created. > > pcleo# ls -l /dev/u* > crw-r--r-- 1 root operator 0, 79 May 19 06:29 /dev/uhid0 > crw------- 1 root wheel 0, 77 May 19 06:29 /dev/ukbd0 > lrwxr-xr-x 1 root wheel 6 May 19 06:29 /dev/urandom -> random > crw-rw---- 1 root operator 0, 38 May 19 06:29 /dev/usb > crw-rw---- 1 root operator 0, 37 May 19 06:29 /dev/usb0 > crw-rw---- 1 root operator 0, 39 May 19 06:29 /dev/usb1 > crw-rw---- 1 root operator 0, 40 May 19 06:29 /dev/usb2 ubtbcmfw(4) is a firmware driver for broadcom bcm2033 chip based bluetooth usb devices. since you have bcm2035b this driver will not work and you do not even need it. > I followed the instructions for dumping my device, here is. ok, i think, i know what problem is. here is the fragment of the dump you sent, i.e. beetle% ./hcidump -xr ~/init.dump HCIDump - HCI packet analyzer ver 1.5 < HCI Command: Reset(0x03|0x0003) plen 0 > HCI Event: Command Complete(0x0e) plen 4 01 03 0C 00 < HCI Command: Read BD ADDR(0x04|0x0009) plen 0 > HCI Event: Command Complete(0x0e) plen 10 01 09 10 00 00 00 00 00 00 00 it appears that in response to the hci "read bd addr" command your device returns an invalid bd_addr, i.e. 00:00:00:00:00:00. i saw a post in one of the linux bluetooth related mailing lists that describes exactly the same problem (http://www.spinics.net/lists/linux-bluetooth/msg00020.html). i have no idea how to fix it at this point, and, inclined to say that this device is broken or needs some non-standard initialization sequence. i'd suggest to get a different dongle if possible. thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Mon May 19 20:07:13 2008 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 8E48210656C0 for ; Mon, 19 May 2008 20:07:13 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.168]) by mx1.freebsd.org (Postfix) with ESMTP id 865D38FC1E for ; Mon, 19 May 2008 20:07:12 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: by ug-out-1314.google.com with SMTP id q2so705029uge.37 for ; Mon, 19 May 2008 13:07:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; 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; bh=ml9AyuQVmKtPU5u/ZumRDfiL7UCIcMlE+HclpQJgOls=; b=ejQwnFGwpYffVMzDYs/lb/g9oM1Zj/ggsWwITVF/sXmlTYFh1YcuAUaGhD13BDTkugaCLH01HLquR82S482G8kQijmr3/ho9VtVJCkq8hfWRxsYSvHNMt1Iu1dFWB4tCQ1m3qC8bI+c1fnTdrJp7qWngYVuJPVQe4xZqcI7lpks= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=AWDrQ8EijOMnBAQcdRXNcU/Rag/m/SQSXeA8T4R6IrofxldgPnekJiCAr4G5UhsksQnQ2sANjwF6LrPTq3+rygZLl3S83uqcD6JxXMiresm1J1mWnL0O00Ni04QXRuT72+RVe6puE5YV0awQoATemNPMI4iTTSl6VRJy8WuZ+/M= Received: by 10.125.164.9 with SMTP id r9mr6401351mko.121.1211227631151; Mon, 19 May 2008 13:07:11 -0700 (PDT) Received: by 10.86.66.5 with HTTP; Mon, 19 May 2008 13:07:11 -0700 (PDT) Message-ID: Date: Mon, 19 May 2008 13:07:11 -0700 From: "Maksim Yevmenkin" To: "Daniel O'Connor" In-Reply-To: <200805181952.00112.doconnor@gsoft.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200805141647.m4EGlUP1021019@repoman.freebsd.org> <200805151814.14386.doconnor@gsoft.com.au> <200805181952.00112.doconnor@gsoft.com.au> Cc: "freebsd-bluetooth@freebsd.org" Subject: Re: cvs commit: src/usr.bin/bluetooth/rfcomm_sppd rfcomm_sppd.1 rfcomm_sppd.c 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, 19 May 2008 20:07:13 -0000 On Sun, May 18, 2008 at 3:21 AM, Daniel O'Connor wrote: > On Thu, 15 May 2008, Maksim Yevmenkin wrote: >> > How hard would it be to have a '-t auto' and have it print out the >> > pty it just allocated? It would make it much easier for scripts to >> > work if that was possible. >> > >> > (Maybe just call openpty()?) >> >> not hard at all. however, how would rfcomm_sppd(1) print tty name if, >> say, it was asked to run in background? perhaps it would be better to >> teach rfcomm_sppd(1) to work with nmdm(4)? > > I don't think nmdm would make a difference in this respect. it depends on usage scenario, imo. please read below. > I am thinking of an operating mode where a script or daemon runs when a > device associates and sets up channels the user has configured. So the > script runs rfcomm_sppd and groks the output to find what PTY has been > allocated and creates a symlink to a human understandable name > (eg /dev/gps0 or whatever) right, that is what i initially wanted to do. the idea was to have complicated configuration file which describes what what rfcomm_sppd(1) should do when a device with a given bd_addr connects on a certain rfcomm channel. then i realized that serial port service is not really good candidate for multiplexing. it all boils down to the fact that only one client can use virtual serial port at a time. i chose pty(4) over nmdm(4) initially to be able to a) call openpty() b) fork() c) redirect child's stdin/out to pty d) exec() something in child. that is similar to how rfcomm_pppd(8) wrapper works (without doing pty part). as i thought about it a bit more, i convinced myself that it probably would be much easier to run multiple instances of rfcomm_sppd(1) on different channels. each instance would then do something different. i still need to write the part where rfcomm_sppd(1) executes something external when client connects. > I have attached a patch which uses openpty() and seems to work fine > (tested quickly against my BT GPS unit & phone). If the patch doesn't > make it you can get it from > http://www.gsoft.com.au/~doconnor/rfcomm_sppd-pty.diff i do not see how slave pty name is being passed back to rfcomm_sppd(1) invoker in _server_ mode. are you suggesting to parse syslog messages? or are you suggesting to have other process that is actively looking for "known" bluetooth devices in range (i.e. perform discovery or ping) and, when found, proactively start rfcomm_sppd(1) in _client_ mode to connect to found devices? > On a related note I find I have to 'kill -9' rfcomm_sppd sometimes if I > have connected to the PTY and then disconnected, eg.. hmm... interesting... i will take a look. just need to find my old bluetooth gps unit. thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Mon May 19 23:16:14 2008 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 10E0B106567F for ; Mon, 19 May 2008 23:16:14 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id 4E18E8FC20 for ; Mon, 19 May 2008 23:16:13 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (ppp121-45-148-169.lns11.adl6.internode.on.net [121.45.148.169]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id m4JNG5F6032043 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 20 May 2008 08:46:07 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: "Maksim Yevmenkin" Date: Tue, 20 May 2008 08:45:50 +0930 User-Agent: KMail/1.9.7 References: <200805141647.m4EGlUP1021019@repoman.freebsd.org> <200805181952.00112.doconnor@gsoft.com.au> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1737171.bu05tt8xdj"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200805200845.57007.doconnor@gsoft.com.au> X-Spam-Score: -2.212 () BAYES_00,RDNS_DYNAMIC X-Scanned-By: MIMEDefang 2.63 on 203.31.81.10 Cc: "freebsd-bluetooth@freebsd.org" Subject: Re: cvs commit: src/usr.bin/bluetooth/rfcomm_sppd rfcomm_sppd.1 rfcomm_sppd.c 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, 19 May 2008 23:16:14 -0000 --nextPart1737171.bu05tt8xdj Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tue, 20 May 2008, Maksim Yevmenkin wrote: > > I am thinking of an operating mode where a script or daemon runs > > when a device associates and sets up channels the user has > > configured. So the script runs rfcomm_sppd and groks the output to > > find what PTY has been allocated and creates a symlink to a human > > understandable name (eg /dev/gps0 or whatever) > > right, that is what i initially wanted to do. the idea was to have > complicated configuration file which describes what what > rfcomm_sppd(1) should do when a device with a given bd_addr connects Shouldn't be that complex ;) > on a certain rfcomm channel. then i realized that serial port service > is not really good candidate for multiplexing. it all boils down to > the fact that only one client can use virtual serial port at a time. Why would you be multiplexing it? It's a virtual serial port, pty sounds=20 like a pretty good match. ie I think I am misunderstanding what you are=20 trying to say. > i chose pty(4) over nmdm(4) initially to be able to > > a) call openpty() > b) fork() > c) redirect child's stdin/out to pty > d) exec() something in child. > > that is similar to how rfcomm_pppd(8) wrapper works (without doing > pty part). as i thought about it a bit more, i convinced myself that > it probably would be much easier to run multiple instances of > rfcomm_sppd(1) on different channels. each instance would then do > something different. i still need to write the part where > rfcomm_sppd(1) executes something external when client connects. OK. > > I have attached a patch which uses openpty() and seems to work fine > > (tested quickly against my BT GPS unit & phone). If the patch > > doesn't make it you can get it from > > http://www.gsoft.com.au/~doconnor/rfcomm_sppd-pty.diff > > i do not see how slave pty name is being passed back to > rfcomm_sppd(1) invoker in _server_ mode. are you suggesting to parse > syslog messages? or are you suggesting to have other process that is Mmm good point :( I was thinking that in server mode it opened the PTY then waited for a=20 connection but that isn't the case.. I guess it could be (although it mangles up the code) > actively looking for "known" bluetooth devices in range (i.e. perform > discovery or ping) and, when found, proactively start rfcomm_sppd(1) > in _client_ mode to connect to found devices? I was thinking basically of only using client mode - I haven't used=20 server mode so it didn't really enter my thoughts :) As you say I was thinking that you poll for known devices (that the user=20 has entered into a config file) and run rfcomm_sppd in client mode to=20 connect to them. I am not sure how/why server mode is actually used - I only have=20 experience with devices that are basically using BT as an RS232=20 replacement. > > On a related note I find I have to 'kill -9' rfcomm_sppd sometimes > > if I have connected to the PTY and then disconnected, eg.. > > hmm... interesting... i will take a look. just need to find my old > bluetooth gps unit. Thanks.. Could be my dodgy GPS unit of course :) ($35 off ebay) =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1737171.bu05tt8xdj Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.8 (FreeBSD) iD8DBQBIMgos5ZPcIHs/zowRApKpAJwPUv8CGlfr8CNqZTyxOnpkJUCE6QCdHlph uaxJE6h3pOgLxWbkx2BQtqw= =GbjA -----END PGP SIGNATURE----- --nextPart1737171.bu05tt8xdj-- From owner-freebsd-bluetooth@FreeBSD.ORG Mon May 19 23:56:23 2008 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 C6EB3106564A for ; Mon, 19 May 2008 23:56:23 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.185]) by mx1.freebsd.org (Postfix) with ESMTP id 4CEC88FC1E for ; Mon, 19 May 2008 23:56:23 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: by nf-out-0910.google.com with SMTP id h3so1034549nfh.33 for ; Mon, 19 May 2008 16:56:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; 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; bh=Nwa/uld+bnIENkNuHiptkDUU4P7NfU1V01P3mALIvUQ=; b=uDaIe7On+O/A/LN5Mlwla8MVGLhuGDKoMDmv5oYWDIxJhYv8mk9x+KYXfsVVREs6pLdjGLZujaUDppv4Fe2vLNUyxZ52AsVWF+D3UXd4s3lKgEbSH+ADyxz/HMe+L6Qi+ztgVTyMgQHxK4nLidz67Ky8Y9JRU+2ZUZ3/QKXb840= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=x53uwhKcEdbVAI//dmZCU52/7W3vD4YlcG5cqnT9/zwjiLnwOB0vFW5bMiwcKT8wOuGqNdkp1gjRmPuMmih6jUWqTgJqQBDo/9Fe4bIFGZawfT+WgMD7gSbuTwoA4jd4lc8MXmMMNUwZtrVyrKF7YC2FwRFRrb+ObCwGvG2qmqI= Received: by 10.125.100.8 with SMTP id c8mr630306mkm.144.1211241381739; Mon, 19 May 2008 16:56:21 -0700 (PDT) Received: by 10.86.66.5 with HTTP; Mon, 19 May 2008 16:56:21 -0700 (PDT) Message-ID: Date: Mon, 19 May 2008 16:56:21 -0700 From: "Maksim Yevmenkin" To: "Daniel O'Connor" In-Reply-To: <200805200845.57007.doconnor@gsoft.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200805141647.m4EGlUP1021019@repoman.freebsd.org> <200805181952.00112.doconnor@gsoft.com.au> <200805200845.57007.doconnor@gsoft.com.au> Cc: "freebsd-bluetooth@freebsd.org" Subject: Re: cvs commit: src/usr.bin/bluetooth/rfcomm_sppd rfcomm_sppd.1 rfcomm_sppd.c 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, 19 May 2008 23:56:23 -0000 On Mon, May 19, 2008 at 4:15 PM, Daniel O'Connor wrote: > On Tue, 20 May 2008, Maksim Yevmenkin wrote: >> > I am thinking of an operating mode where a script or daemon runs >> > when a device associates and sets up channels the user has >> > configured. So the script runs rfcomm_sppd and groks the output to >> > find what PTY has been allocated and creates a symlink to a human >> > understandable name (eg /dev/gps0 or whatever) >> >> right, that is what i initially wanted to do. the idea was to have >> complicated configuration file which describes what what >> rfcomm_sppd(1) should do when a device with a given bd_addr connects > > Shouldn't be that complex ;) well, yes :) >> on a certain rfcomm channel. then i realized that serial port service >> is not really good candidate for multiplexing. it all boils down to >> the fact that only one client can use virtual serial port at a time. > > Why would you be multiplexing it? It's a virtual serial port, pty sounds > like a pretty good match. ie I think I am misunderstanding what you are > trying to say. ok, i will give you an example. lets say i have a couple of bluetooth devices. lets say device #1 is a handheld and device #2 is some other client device that wants to use serial port service on the pc. say, its a bluetooth scanner/keyboard/etc. type device that proactively connects to the host computer and sends stream of data. with virtual serial port there is no real need to register two (or more) serial port services on the host pc. one could argue that rfcomm_sppd(1) should have a configuration file that says if connected to device #1 { execute sync application } if connected to device #2 { dump data } technically, both devices could use the same serial port service registered on the same rfcomm channel on the same host pc. the data coming from two different rfcomm connections from two different devices. the server bluetooth endpoint just happens to be the same, but the server will have two connections and two separate pty's for both clients. this is the soft of multiplexing i'm talking about. the same will work in client mode too. >> > I have attached a patch which uses openpty() and seems to work fine >> > (tested quickly against my BT GPS unit & phone). If the patch >> > doesn't make it you can get it from >> > http://www.gsoft.com.au/~doconnor/rfcomm_sppd-pty.diff >> >> i do not see how slave pty name is being passed back to >> rfcomm_sppd(1) invoker in _server_ mode. are you suggesting to parse >> syslog messages? or are you suggesting to have other process that is > > Mmm good point :( > I was thinking that in server mode it opened the PTY then waited for a > connection but that isn't the case.. this is the case. it opens pty first then it does listen/accept/etc. > I guess it could be (although it mangles up the code) > >> actively looking for "known" bluetooth devices in range (i.e. perform >> discovery or ping) and, when found, proactively start rfcomm_sppd(1) >> in _client_ mode to connect to found devices? > > I was thinking basically of only using client mode - I haven't used > server mode so it didn't really enter my thoughts :) > > As you say I was thinking that you poll for known devices (that the user > has entered into a config file) and run rfcomm_sppd in client mode to > connect to them. > > I am not sure how/why server mode is actually used - I only have > experience with devices that are basically using BT as an RS232 > replacement. right, there aren't many examples of server mode usage, but i was thinking about "serial console" over bluetooth type thing. of course it will never be a real serial console, just another out-of-band access. could be useful to somebody. thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Tue May 20 01:45:18 2008 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 BDD4C106566B for ; Tue, 20 May 2008 01:45:18 +0000 (UTC) (envelope-from lsantagostini@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.239]) by mx1.freebsd.org (Postfix) with ESMTP id 09FE58FC16 for ; Tue, 20 May 2008 01:45:17 +0000 (UTC) (envelope-from lsantagostini@gmail.com) Received: by wx-out-0506.google.com with SMTP id h27so1685405wxd.7 for ; Mon, 19 May 2008 18:45:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=OOErIX4Q7FYZNTCVI/rl4eOeWhEZTxfo7IjOUgMj8Y0=; b=X2KwSGwxlgifcwKcL63ZdK/BjOkTvkRuIwtTbdw/zapoA+Hb6okGmIaPqIDfAvet5B8yyg++I1mPLCl7AThct61UVedR6msKLhfjD1cqKThtEUunn0VVbf4S9EswfWjpNmrdJ1GxHJr0mvOFztI22BhpL2jwIyHRXEW2fiy4k/w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=rfn0ziHbm4sAwllOyFl46/n2rGZrxNrbCW7S4vC8IjvUmJaf7OhuFSDmVzADCz3ofJljAMybNa5h5ykyZ/+YOhpvph13wNjqxtpAU643FHwFxTbjf+hhOo811ejL2C4EprlqLmrcfgpACTikJeQQYKxF/Dr7KR1GYCwt3v88jxE= Received: by 10.70.23.2 with SMTP id 2mr10178537wxw.5.1211247917060; Mon, 19 May 2008 18:45:17 -0700 (PDT) Received: by 10.70.116.10 with HTTP; Mon, 19 May 2008 18:45:16 -0700 (PDT) Message-ID: <9ab7eeeb0805191845y3e185cb3w42988296b449d35c@mail.gmail.com> Date: Tue, 20 May 2008 01:45:16 +0000 From: "Leonardo Santagostini" To: "Maksim Yevmenkin" In-Reply-To: MIME-Version: 1.0 References: <9ab7eeeb0805190319u30ccbeefq1511afa063bd75fe@mail.gmail.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-bluetooth@freebsd.org Subject: Re: Problem with a BCM2035B 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, 20 May 2008 01:45:18 -0000 Ok thanks for the reply Max. I will try with another dongle But, if you want to make some probes with this dongle, just tellme you will be welcome ;) Sincerely. Leonardo 2008/5/19 Maksim Yevmenkin : > Hello, > > > I was already googling and browsing over Internet about mi problem. > > Im using FreeBSD 7.0-RELEASE and the problem is that the donlge dont want > to > > work. > > > > I tried kldloanding various modeules, here comes my kldstat > > pcleo# kldstat > > Id Refs Address Size Name > > 1 32 0xc0400000 9130cc kernel > > 2 1 0xc0d14000 ce30 if_wi.ko > > 3 1 0xc0d21000 14324 snd_hda.ko > > 4 2 0xc0d36000 4a5ac sound.ko > > 5 1 0xc0d81000 19f34 if_ral.ko > > 6 1 0xc0d9b000 80ea28 nvidia.ko > > 7 2 0xc15aa000 28658 linux.ko > > 8 1 0xc15d3000 3130 ubtbcmfw.ko > > 9 1 0xc15d7000 802c ng_ubt.ko > > 10 6 0xc15e0000 d3a0 netgraph.ko > > 11 1 0xc15ee000 1bdc wlan_xauth.ko > > 12 1 0xc15f0000 6a32c acpi.ko > > 13 4 0xc5529000 2000 ng_bluetooth.ko > > 14 1 0xc552b000 d000 ng_hci.ko > > 15 1 0xc5558000 f000 ng_l2cap.ko > > 16 1 0xc5569000 19000 ng_btsocket.ko > > 17 1 0xc558b000 4000 ng_socket.ko > > looks fine > > > The /var/log/messages tells: > > > > May 19 07:09:47 pcleo root: Unknown USB device: vendor 0x0a5c product > 0x2035 > > bus uhub1 > > May 19 07:09:47 pcleo kernel: ubt0: > rev 2.00/1.00, addr 3> on uhub1 > > May 19 07:09:47 pcleo kernel: ubt0: Interface 0 endpoints: > interrupt=0x81, > > bulk-in=0x82, bulk-out=0x2 > > May 19 07:09:47 pcleo kernel: ubt0: Interface 1 (alt.config 4) endpoints: > > isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=64; nframes=5, buffer size=320 > > May 19 07:09:47 pcleo root: /etc/rc.d/bluetooth: ERROR: Unable to setup > > Bluetooth stack for device ubt0 > > this does not look good. > > i been trying bcmfw without results, in fact, when i do a ls -l /dev/u* i > > cant see an ubtbcmfw device created. > > > > pcleo# ls -l /dev/u* > > crw-r--r-- 1 root operator 0, 79 May 19 06:29 /dev/uhid0 > > crw------- 1 root wheel 0, 77 May 19 06:29 /dev/ukbd0 > > lrwxr-xr-x 1 root wheel 6 May 19 06:29 /dev/urandom -> > random > > crw-rw---- 1 root operator 0, 38 May 19 06:29 /dev/usb > > crw-rw---- 1 root operator 0, 37 May 19 06:29 /dev/usb0 > > crw-rw---- 1 root operator 0, 39 May 19 06:29 /dev/usb1 > > crw-rw---- 1 root operator 0, 40 May 19 06:29 /dev/usb2 > > ubtbcmfw(4) is a firmware driver for broadcom bcm2033 chip based > bluetooth usb devices. since you have bcm2035b this driver will not > work and you do not even need it. > > > I followed the instructions for dumping my device, here is. > > ok, i think, i know what problem is. here is the fragment of the dump > you sent, i.e. > > beetle% ./hcidump -xr ~/init.dump > HCIDump - HCI packet analyzer ver 1.5 > < HCI Command: Reset(0x03|0x0003) plen 0 > > HCI Event: Command Complete(0x0e) plen 4 > 01 03 0C 00 > < HCI Command: Read BD ADDR(0x04|0x0009) plen 0 > > HCI Event: Command Complete(0x0e) plen 10 > 01 09 10 00 00 00 00 00 00 00 > > it appears that in response to the hci "read bd addr" command your > device returns an invalid bd_addr, i.e. 00:00:00:00:00:00. i saw a > post in one of the linux bluetooth related mailing lists that > describes exactly the same problem > (http://www.spinics.net/lists/linux-bluetooth/msg00020.html). i have > no idea how to fix it at this point, and, inclined to say that this > device is broken or needs some non-standard initialization sequence. > i'd suggest to get a different dongle if possible. > > thanks, > max > -- Saludos.- Leonardo Santagostini From owner-freebsd-bluetooth@FreeBSD.ORG Tue May 20 01:48:35 2008 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 E3ED810656C5 for ; Tue, 20 May 2008 01:48:35 +0000 (UTC) (envelope-from lsantagostini@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.230]) by mx1.freebsd.org (Postfix) with ESMTP id A55128FC1B for ; Tue, 20 May 2008 01:48:35 +0000 (UTC) (envelope-from lsantagostini@gmail.com) Received: by wx-out-0506.google.com with SMTP id h27so1686284wxd.7 for ; Mon, 19 May 2008 18:48:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=v1tkpj0vSbSuN1WNq2JhsgbgBmUWyi6n1DUo7JUGd/Q=; b=R6TBdQ3SzXDgi1tI8jHIZd7SZQRMcDVF5yTCQbG+xqC3wvbksniH6PuNqLBV1W5BcFx0oBJSuL8Tf8mw3xnbgq36JHOplqbt6+Q1mMI0irb1nPBWvUxyMfbrNqBF0DZpahec6D750/Xp0DxmFfaxB3EkkhGkz5sAFNuO6EyUVSM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=GnnwTpnBOKpAi33CZshLpJdCnReqpyfYvnkyRQ37QcnleWaJZo/LL9+0fHK43sh534hLPLvjA0V9rAcRLpzLVNdkpWF3E5PMXkHKCjMFOaoZzRO3gppptDRk45OCCEMH98c2PM6Lj4PI9cz2Qk34fGNkjhgonAFefKuK+AibJYQ= Received: by 10.70.54.2 with SMTP id c2mr10118179wxa.85.1211248114192; Mon, 19 May 2008 18:48:34 -0700 (PDT) Received: by 10.70.116.10 with HTTP; Mon, 19 May 2008 18:48:34 -0700 (PDT) Message-ID: <9ab7eeeb0805191848p11e3b6d4u9bdd423e4e7d2533@mail.gmail.com> Date: Tue, 20 May 2008 01:48:34 +0000 From: "Leonardo Santagostini" To: "Maksim Yevmenkin" In-Reply-To: MIME-Version: 1.0 References: <9ab7eeeb0805190319u30ccbeefq1511afa063bd75fe@mail.gmail.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-bluetooth@freebsd.org Subject: Re: Problem with a BCM2035B 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, 20 May 2008 01:48:36 -0000 Sorry, but, by the way. In the manufacturer page says: The BCM2035 is based on the production and UnPlugFest proven architecture of the BCM2033 Bluetooth baseband core (BBC), peripheral transport unit (PTU) http://broadcom.com/products/Bluetooth/Bluetooth-RF-Silicon-and-Software-Solutions/BCM2035 Do you think we can make something ? Yours, Leonardo 2008/5/19 Maksim Yevmenkin : > Hello, > > > I was already googling and browsing over Internet about mi problem. > > Im using FreeBSD 7.0-RELEASE and the problem is that the donlge dont want > to > > work. > > > > I tried kldloanding various modeules, here comes my kldstat > > pcleo# kldstat > > Id Refs Address Size Name > > 1 32 0xc0400000 9130cc kernel > > 2 1 0xc0d14000 ce30 if_wi.ko > > 3 1 0xc0d21000 14324 snd_hda.ko > > 4 2 0xc0d36000 4a5ac sound.ko > > 5 1 0xc0d81000 19f34 if_ral.ko > > 6 1 0xc0d9b000 80ea28 nvidia.ko > > 7 2 0xc15aa000 28658 linux.ko > > 8 1 0xc15d3000 3130 ubtbcmfw.ko > > 9 1 0xc15d7000 802c ng_ubt.ko > > 10 6 0xc15e0000 d3a0 netgraph.ko > > 11 1 0xc15ee000 1bdc wlan_xauth.ko > > 12 1 0xc15f0000 6a32c acpi.ko > > 13 4 0xc5529000 2000 ng_bluetooth.ko > > 14 1 0xc552b000 d000 ng_hci.ko > > 15 1 0xc5558000 f000 ng_l2cap.ko > > 16 1 0xc5569000 19000 ng_btsocket.ko > > 17 1 0xc558b000 4000 ng_socket.ko > > looks fine > > > The /var/log/messages tells: > > > > May 19 07:09:47 pcleo root: Unknown USB device: vendor 0x0a5c product > 0x2035 > > bus uhub1 > > May 19 07:09:47 pcleo kernel: ubt0: > rev 2.00/1.00, addr 3> on uhub1 > > May 19 07:09:47 pcleo kernel: ubt0: Interface 0 endpoints: > interrupt=0x81, > > bulk-in=0x82, bulk-out=0x2 > > May 19 07:09:47 pcleo kernel: ubt0: Interface 1 (alt.config 4) endpoints: > > isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=64; nframes=5, buffer size=320 > > May 19 07:09:47 pcleo root: /etc/rc.d/bluetooth: ERROR: Unable to setup > > Bluetooth stack for device ubt0 > > this does not look good. > > i been trying bcmfw without results, in fact, when i do a ls -l /dev/u* i > > cant see an ubtbcmfw device created. > > > > pcleo# ls -l /dev/u* > > crw-r--r-- 1 root operator 0, 79 May 19 06:29 /dev/uhid0 > > crw------- 1 root wheel 0, 77 May 19 06:29 /dev/ukbd0 > > lrwxr-xr-x 1 root wheel 6 May 19 06:29 /dev/urandom -> > random > > crw-rw---- 1 root operator 0, 38 May 19 06:29 /dev/usb > > crw-rw---- 1 root operator 0, 37 May 19 06:29 /dev/usb0 > > crw-rw---- 1 root operator 0, 39 May 19 06:29 /dev/usb1 > > crw-rw---- 1 root operator 0, 40 May 19 06:29 /dev/usb2 > > ubtbcmfw(4) is a firmware driver for broadcom bcm2033 chip based > bluetooth usb devices. since you have bcm2035b this driver will not > work and you do not even need it. > > > I followed the instructions for dumping my device, here is. > > ok, i think, i know what problem is. here is the fragment of the dump > you sent, i.e. > > beetle% ./hcidump -xr ~/init.dump > HCIDump - HCI packet analyzer ver 1.5 > < HCI Command: Reset(0x03|0x0003) plen 0 > > HCI Event: Command Complete(0x0e) plen 4 > 01 03 0C 00 > < HCI Command: Read BD ADDR(0x04|0x0009) plen 0 > > HCI Event: Command Complete(0x0e) plen 10 > 01 09 10 00 00 00 00 00 00 00 > > it appears that in response to the hci "read bd addr" command your > device returns an invalid bd_addr, i.e. 00:00:00:00:00:00. i saw a > post in one of the linux bluetooth related mailing lists that > describes exactly the same problem > (http://www.spinics.net/lists/linux-bluetooth/msg00020.html). i have > no idea how to fix it at this point, and, inclined to say that this > device is broken or needs some non-standard initialization sequence. > i'd suggest to get a different dongle if possible. > > thanks, > max > -- Saludos.- Leonardo Santagostini From owner-freebsd-bluetooth@FreeBSD.ORG Tue May 20 16:50:46 2008 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 656C5106564A for ; Tue, 20 May 2008 16:50:46 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from fk-out-0910.google.com (fk-out-0910.google.com [209.85.128.187]) by mx1.freebsd.org (Postfix) with ESMTP id E6E878FC1F for ; Tue, 20 May 2008 16:50:45 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: by fk-out-0910.google.com with SMTP id k31so2552630fkk.11 for ; Tue, 20 May 2008 09:50:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; 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; bh=O5GcQM40YF2aFHA+ykYeBhm08+iVWkm0SHcO+VrA5vk=; b=PzAWRoEbvM1AQmYy1Pq/gClONKDg+HCq52JSfSyNzwWlEbCtR2B3YgBg5d3XuqFa6gLJvoRqIUf26gSAXtMMRBg1mHTddwsPA4NMRAmpymR5g6WiRrPwi4fdvMf0Ecwc6kwMRu8EPenPalRxl0kSlKF25g0pOAnP0CGZ2KszAuY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=loXWnd4/3JR3tUKYgIKAFD7AlwkRdLolT3Z0h9VmLYWeWvH6MqP+MUMSc4WrTUXbfD7z55lSHIUandnY/EjXWyxovBXRyg8j275tsv34tLdmvcCTBhJ6NSBsC8r9ltKNEg/HepsSkVPpkfKD2cHwcQKfGzBSTK+VCuXSAO36MQ8= Received: by 10.125.164.7 with SMTP id r7mr7380790mko.132.1211302244286; Tue, 20 May 2008 09:50:44 -0700 (PDT) Received: by 10.86.66.5 with HTTP; Tue, 20 May 2008 09:50:44 -0700 (PDT) Message-ID: Date: Tue, 20 May 2008 09:50:44 -0700 From: "Maksim Yevmenkin" To: "Leonardo Santagostini" In-Reply-To: <9ab7eeeb0805191848p11e3b6d4u9bdd423e4e7d2533@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <9ab7eeeb0805190319u30ccbeefq1511afa063bd75fe@mail.gmail.com> <9ab7eeeb0805191848p11e3b6d4u9bdd423e4e7d2533@mail.gmail.com> Cc: freebsd-bluetooth@freebsd.org Subject: Re: Problem with a BCM2035B 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, 20 May 2008 16:50:46 -0000 On 5/19/08, Leonardo Santagostini wrote: > Sorry, but, by the way. > In the manufacturer page says: > > The BCM2035 is based on the production and UnPlugFest proven architecture of > the BCM2033 Bluetooth baseband core (BBC), peripheral transport unit (PTU) it really does not mean anything. its just marking buzz words, imo. "architecture" is too much generic word. all it probably means is that the 2035 chip has the same functional blocks as 2033 chip, i.e. cpu, memory, flash, radio etc. > Do you think we can make something ? did your 2035 dongle come with driver cd (for windows)? can you find any .bin or .hex files on the driver cd? what would really be helpful is a usb snoop trace (from windows) that shows how windows initializes this device. thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Tue May 20 19:29:19 2008 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 E421B1065679 for ; Tue, 20 May 2008 19:29:19 +0000 (UTC) (envelope-from Tom@Malcolmson.com) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id C1D5C8FC18 for ; Tue, 20 May 2008 19:29:19 +0000 (UTC) (envelope-from Tom@Malcolmson.com) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 4057D10A522 for ; Tue, 20 May 2008 15:11:07 -0400 (EDT) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Tue, 20 May 2008 15:11:07 -0400 X-Sasl-enc: ttnh8HRqw5PXsVIMSjnJuXroXb1o3H41sgX041ve9vSi 1211310667 Received: from [192.168.0.138] (TOROON12-1177741232.sdsl.bell.ca [70.50.231.176]) by mail.messagingengine.com (Postfix) with ESMTPSA id F2B28371C for ; Tue, 20 May 2008 15:11:06 -0400 (EDT) Message-ID: <48332249.3010709@Malcolmson.com> Date: Tue, 20 May 2008 15:11:05 -0400 From: Tom Malcolmson User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: freebsd-bluetooth@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Looking for mini-pci bluetooth adapter 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, 20 May 2008 19:29:20 -0000 Is there a BSD driver for any mini-pci bluetooth adapters? Preferably one that is 'current' - ie. is still available for purchase and supports bluetooth 2.0. Thanks, Tom. From owner-freebsd-bluetooth@FreeBSD.ORG Tue May 20 19:31:02 2008 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 177F71065672 for ; Tue, 20 May 2008 19:31:02 +0000 (UTC) (envelope-from lsantagostini@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.238]) by mx1.freebsd.org (Postfix) with ESMTP id C514F8FC17 for ; Tue, 20 May 2008 19:31:01 +0000 (UTC) (envelope-from lsantagostini@gmail.com) Received: by wx-out-0506.google.com with SMTP id h27so1964869wxd.7 for ; Tue, 20 May 2008 12:31:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=TUNisboPrKgqKqQKXVtes7u9vWWyjL6AcFmfSYwARUQ=; b=hV0C5BvfAPdWlEcn//TgBVNoSCjc5INJ5mS60Sz2uxkpNfukAf6MpNSuueDoRk2ZEEf9u9ZM63/vc3ajyU/nUoG0YcQXeY8IXphNZNNiyDl+2rplXwcBLdf5R0MRJjHd/uGi/blBzGLAnsaZm3mkfhu0myw/bt0VrCvmzzyn10c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=CNj6ksPBO87JBT/TotMVpv0d4h2jnUnNI2pRO9TKc1C/76pa2iIu8qD8OKe1wXdm3sHeDSAiwnBbt9Qu8j0yJKwUKnhZGwiKazCt6KhzbpjnNXxzYK8W6uRlyfi2KJWKqI9Tsq99kAdJmWWCgNKvHt9jqzjLjdYstF4Hg6JjMjI= Received: by 10.70.9.8 with SMTP id 8mr11341417wxi.27.1211311860969; Tue, 20 May 2008 12:31:00 -0700 (PDT) Received: by 10.70.116.10 with HTTP; Tue, 20 May 2008 12:31:00 -0700 (PDT) Message-ID: <9ab7eeeb0805201231o65e5058h427f4bafa8d27a39@mail.gmail.com> Date: Tue, 20 May 2008 16:31:00 -0300 From: "Leonardo Santagostini" To: "Maksim Yevmenkin" In-Reply-To: MIME-Version: 1.0 References: <9ab7eeeb0805190319u30ccbeefq1511afa063bd75fe@mail.gmail.com> <9ab7eeeb0805191848p11e3b6d4u9bdd423e4e7d2533@mail.gmail.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-bluetooth@freebsd.org Subject: Re: Problem with a BCM2035B 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, 20 May 2008 19:31:02 -0000 Max: I have not installed windows at home, but i like challenges and i will install it onto a hard disk and i will find the drivers to make it work on windows. Do you have any tool to make a trace from the usb device ? Thanks really much Yours, Leonardo 2008/5/20 Maksim Yevmenkin : > On 5/19/08, Leonardo Santagostini wrote: > > Sorry, but, by the way. > > In the manufacturer page says: > > > > The BCM2035 is based on the production and UnPlugFest proven architecture > of > > the BCM2033 Bluetooth baseband core (BBC), peripheral transport unit > (PTU) > > it really does not mean anything. its just marking buzz words, imo. > "architecture" is too much generic word. all it probably means is that > the 2035 chip has the same functional blocks as 2033 chip, i.e. cpu, > memory, flash, radio etc. > > > Do you think we can make something ? > > did your 2035 dongle come with driver cd (for windows)? can you find > any .bin or .hex files on the driver cd? > > what would really be helpful is a usb snoop trace (from windows) that > shows how windows initializes this device. > > thanks, > max > -- Saludos.- Leonardo Santagostini From owner-freebsd-bluetooth@FreeBSD.ORG Tue May 20 23:43:14 2008 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 B90801065675 for ; Tue, 20 May 2008 23:43:14 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.155]) by mx1.freebsd.org (Postfix) with ESMTP id 4AB288FC16 for ; Tue, 20 May 2008 23:43:13 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: by fg-out-1718.google.com with SMTP id l26so2937073fgb.35 for ; Tue, 20 May 2008 16:43:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; 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; bh=Mn+z60yZWLhJrMxvkh3RZP8Ef/ET5n1elSPVFaXnWDk=; b=pBwx2qPd3kh6QiGvZ21l5Ppp89qsVjCjj0dWkvC9Lma5mBEoSvuN0AcQLta5cmL52GprJUyNBlqnYTXoTDUmUEUzu1ye2K+je46oMSCDHRE4KYREVBuvGYlbwu5AwK7zNN33xR06n7VTMiXe0Dc0lpEHnX0zABU+K4iFzcAckPU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=wE5LtftaDZMmd/qL+FMOXlNcAS+hzzZhjjj7/+SKtP0JK62V6xgxPH9xAUr2Zyv8VE11V4Us7/d8KRFbmOql/Yb0gmXEaxJFjHZ6MMXj23BloH8h7Q753QNt/DqlU2RN6LHZgIUOz9o2rDVR4Tm2RLKz0a0FtrUt5Hl+SKi+zLQ= Received: by 10.125.16.5 with SMTP id t5mr7766320mki.50.1211326992862; Tue, 20 May 2008 16:43:12 -0700 (PDT) Received: by 10.86.66.5 with HTTP; Tue, 20 May 2008 16:43:12 -0700 (PDT) Message-ID: Date: Tue, 20 May 2008 16:43:12 -0700 From: "Maksim Yevmenkin" To: "Leonardo Santagostini" In-Reply-To: <9ab7eeeb0805201231o65e5058h427f4bafa8d27a39@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <9ab7eeeb0805190319u30ccbeefq1511afa063bd75fe@mail.gmail.com> <9ab7eeeb0805191848p11e3b6d4u9bdd423e4e7d2533@mail.gmail.com> <9ab7eeeb0805201231o65e5058h427f4bafa8d27a39@mail.gmail.com> Cc: freebsd-bluetooth@freebsd.org Subject: Re: Problem with a BCM2035B 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, 20 May 2008 23:43:14 -0000 On 5/20/08, Leonardo Santagostini wrote: > Max: > > I have not installed windows at home, but i like challenges and i will > install it onto a hard disk and i will find the drivers to make it work on > windows. > > Do you have any tool to make a trace from the usb device ? here is one - never tried to use it myself http://sourceforge.net/projects/usbsnoop/ thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Tue May 20 23:52:55 2008 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 7C1BF106567E for ; Tue, 20 May 2008 23:52:55 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from gv-out-0910.google.com (gv-out-0910.google.com [216.239.58.184]) by mx1.freebsd.org (Postfix) with ESMTP id 0B2498FC14 for ; Tue, 20 May 2008 23:52:54 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: by gv-out-0910.google.com with SMTP id n8so455880gve.39 for ; Tue, 20 May 2008 16:52:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; 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; bh=ySWC4MpWVEq33fn8cj//iyDbmySdqr/H5fYoPNXq3S4=; b=nklQrUfbnGHOlSDPvwKHVfg2SjYw2IC1EXAGO6Mz6/Em72cuBGdXGvoZsHQLRKMWuJYilVYP/CsFl1E1aHUPIDM9jcsA9I7JeCeAscivP8sukFuh2Rk5YzzWZylXBU/xtNFgSZfuFmpac9ynBVHku8kxUL/t5GW5xE6/T2kMNy0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=kxttql5e8WgTSQRpXDtWA66YqOih/H3+eyxUTVAdCfJuyzzmL1NzVw5jxDwKC5ywRMwdEnDCOMshpQ1z/F2cCpIei0a/kTt7YNhKJOZDuobNwqFn3oun2pClOkQDjG6x3yiyObiXqe50TbliObGgCSTgmRVOVoXc46oroWHlLf0= Received: by 10.125.164.9 with SMTP id r9mr7765896mko.120.1211327573129; Tue, 20 May 2008 16:52:53 -0700 (PDT) Received: by 10.86.66.5 with HTTP; Tue, 20 May 2008 16:52:53 -0700 (PDT) Message-ID: Date: Tue, 20 May 2008 16:52:53 -0700 From: "Maksim Yevmenkin" To: "Tom Malcolmson" In-Reply-To: <48332249.3010709@Malcolmson.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <48332249.3010709@Malcolmson.com> Cc: freebsd-bluetooth@freebsd.org Subject: Re: Looking for mini-pci bluetooth adapter 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, 20 May 2008 23:52:55 -0000 On 5/20/08, Tom Malcolmson wrote: > Is there a BSD driver for any mini-pci bluetooth adapters? Preferably one > that is 'current' - ie. is still available for purchase and supports > bluetooth 2.0. it depends on the particular mini-pci bluetooth card and how it presents itself. it could be a serial port, usb bluetooth device or something else. if the card looks like serial port or usb device then it will likely to work. usually no special drivers are required for usb or serial bluetooth devices. thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Wed May 21 00:02:46 2008 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 C4EAF1065670 for ; Wed, 21 May 2008 00:02:46 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id 20EBB8FC14 for ; Wed, 21 May 2008 00:02:45 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (ppp121-45-148-169.lns11.adl6.internode.on.net [121.45.148.169]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id m4L02grl098234 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 21 May 2008 09:32:43 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: "Maksim Yevmenkin" Date: Wed, 21 May 2008 09:32:39 +0930 User-Agent: KMail/1.9.7 References: <200805141647.m4EGlUP1021019@repoman.freebsd.org> <200805200845.57007.doconnor@gsoft.com.au> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1255834.XBC80CXTYJ"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200805210932.40993.doconnor@gsoft.com.au> X-Spam-Score: -2.212 () BAYES_00,RDNS_DYNAMIC X-Scanned-By: MIMEDefang 2.63 on 203.31.81.10 Cc: "freebsd-bluetooth@freebsd.org" Subject: Re: cvs commit: src/usr.bin/bluetooth/rfcomm_sppd rfcomm_sppd.1 rfcomm_sppd.c 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, 21 May 2008 00:02:47 -0000 --nextPart1255834.XBC80CXTYJ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tue, 20 May 2008, Maksim Yevmenkin wrote: > > Why would you be multiplexing it? It's a virtual serial port, pty > > sounds like a pretty good match. ie I think I am misunderstanding > > what you are trying to say. > > ok, i will give you an example. lets say i have a couple of bluetooth > devices. lets say device #1 is a handheld and device #2 is some other > client device that wants to use serial port service on the pc. say, > its a bluetooth scanner/keyboard/etc. type device that proactively > connects to the host computer and sends stream of data. > > with virtual serial port there is no real need to register two (or > more) serial port services on the host pc. one could argue that > rfcomm_sppd(1) should have a configuration file that says > > if connected to device #1 { execute sync application } > if connected to device #2 { dump data } > > technically, both devices could use the same serial port service > registered on the same rfcomm channel on the same host pc. the data > coming from two different rfcomm connections from two different > devices. the server bluetooth endpoint just happens to be the same, > but the server will have two connections and two separate pty's for > both clients. this is the soft of multiplexing i'm talking about. the > same will work in client mode too. OK. > > Mmm good point :( > > I was thinking that in server mode it opened the PTY then waited > > for a connection but that isn't the case.. > > this is the case. it opens pty first then it does listen/accept/etc. Huh yes so it does! > > I am not sure how/why server mode is actually used - I only have > > experience with devices that are basically using BT as an RS232 > > replacement. > > right, there aren't many examples of server mode usage, but i was > thinking about "serial console" over bluetooth type thing. of course > it will never be a real serial console, just another out-of-band > access. could be useful to somebody. Selfishly, I think it's better to focus on the client stuff - heck I use=20 it, so must everyone else ;) I wonder if the server stuff should be split into a separate program. At=20 the moment rfcomm_sppd works perfectly well as a client program (with=20 my patch anyway ;) but server mode needs more work to be properly=20 useful (IMO) as it needs the config file and ability to exec stuff on=20 demand etc.. =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1255834.XBC80CXTYJ Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.8 (FreeBSD) iD8DBQBIM2ag5ZPcIHs/zowRAjJoAJwMupdVBzQ2aq43rzZEdqUDVH15HgCeIOWq yiIatMtl7HsSj4zIa5l8RyA= =tZgq -----END PGP SIGNATURE----- --nextPart1255834.XBC80CXTYJ--