Date: Wed, 15 Jun 2011 15:28:44 +1000 From: Da Rock <freebsd-bluetooth@herveybayaustralia.com.au> To: Maksim Yevmenkin <maksim.yevmenkin@gmail.com> Cc: bluetooth@freebsd.org Subject: Re: Asus bluetooth device - 0x1712 Message-ID: <4DF8430C.3010104@herveybayaustralia.com.au> In-Reply-To: <BANLkTi=5rhWfo38T2x-33OB2y47xQasU9A@mail.gmail.com> References: <4DF46049.6080206@herveybayaustralia.com.au> <alpine.NEB.2.00.1106120817050.472@galant.ukfsn.org> <4DF53A6F.9080701@herveybayaustralia.com.au> <alpine.NEB.2.00.1106130738010.14646@galant.ukfsn.org> <BANLkTikGH9nsqgj_ELOM=PakD=4_h-C4Yw@mail.gmail.com> <4DF705C9.7020606@herveybayaustralia.com.au> <alpine.NEB.2.00.1106142057270.1687@galant.ukfsn.org> <4DF7F13C.6090208@herveybayaustralia.com.au> <BANLkTi=5rhWfo38T2x-33OB2y47xQasU9A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 06/15/11 09:47, Maksim Yevmenkin wrote: > On Tue, Jun 14, 2011 at 4:39 PM, Da Rock > <freebsd-bluetooth@herveybayaustralia.com.au> wrote: > >> On 06/15/11 06:17, Iain Hibbert wrote: >> >>> On Tue, 14 Jun 2011, Da Rock wrote: >>> >>> >>> >>>>> first, question: did you load ng_ubt(4) driver? >>>>> >>>>> >>>>> >>>> Naturally. Its in the handbook, and you never discount the handbook :) >>>> >>>> >>>>> if you did and device is still not recognized, could you please dump >>>>> device descriptor, i.e. use usbconfig(8) dump_device_desc command >>>>> >>>>> >>>>> >>>> ugen5.2:<product 0x1712 vendor 0x0b05> at usbus5, cfg=0 md=HOST spd=FULL >>>> (12Mbps) pwr=ON >>>> >>>> bDeviceClass = 0x00e0 >>>> bDeviceSubClass = 0x0001 >>>> bDeviceProtocol = 0x0001 >>>> >>>> >>> seems like the ng_ubt driver should attach to this directly.. >>> >>> >> Probably would if it recognised the product then. What is the correct way to >> do this then? I know about usbdevs, and the awk script to run, but does >> anything then need to be added to the driver to pick it up, or should that >> be all thats needed? >> > it does not look at the product. it looks at interface class, subclass > and protocol. are you sure you are loading ng_ubt(4) from loader.conf? > are there any error messages from ng_ubt(4) in /var/log/messages? > devd.conf problem then? I haven't got it in loader.conf, but I did kldload- dmesg output (although the last 2 lines disappear when unloaded/loaded: ubt0: <vendor 0x0b05 product 0x1712, class 224/1, rev 2.00/19.15, addr 2> on usbus5 WARNING: attempt to domain_add(bluetooth) after domainfinalize() WARNING: attempt to domain_add(netgraph) after domainfinalize() But ls dev shows no devices, and I can't start bluetooth services: /etc/rc.d/bluetooth: ERROR: Unable to setup Bluetooth stack for device ubt0 If it should work, then what am I doing wrong? > >>> >>> >>>>>>> I'm currently learning about this technology (I know, late bloomer >>>>>>> and all... :) ) and its various features- which are why I'm >>>>>>> looking carefully at it now for my current needs. Unfortunately >>>>>>> its the advanced features which I really need :( So if I can help >>>>>>> advance things I will. >>>>>>> >>>>>>> >>>>>>> >>>>>> what advanced features do you need? >>>>>> >>>>>> >>>>>> >>>> I'm a little new to jargon, but the features are stereo audio, better >>>> bitrates, remote control, phone control, etc (HSP, EDR, AV-something or >>>> rather >>>> I think at least). Basically all the cool media stuff available now that >>>> wasn't around with 1.x. Thats what has grabbed my interest now anyway, >>>> file >>>> transfer, dun... meh- I can do that with wifi. >>>> >>>> >>> better bitrates should be supported natively (not sure about the 3.0 HS >>> speeds, perhaps that requires extra work?) and the parts that would not be >>> supported from the top of my head would be "Secure Simple Pairing" and >>> reliable L2CAP channels, most of the rest is just operating over >>> normal L2CAP/RFCOMM sockets anyway.. >>> >>> the Advanced Audio I have wanted to do for some time as an audio daemon >>> but never got around to starting (not sure actually, how complex it will >>> be - for FreeBSD it would require something like the NetBSD pad(4) driver >>> to be added also).. the Heaset will actually use SCO sockets for audio, >>> which I think FreeBSD does support and there is some code in NetBSD that >>> handles it (via a special kernel audio device, but it should be converted >>> to use pad(4)). Similarly for Handsfree (there is a bthfp program that I >>> wrote, basically a proof-of-concept rather than being greatly useful) >>> >>> not sure how the AV?TP profiles/protocols work, I don't think they are all >>> that complex, it might be that they can represent as a HID profile or if >>> it needs to be tied somewhat into a media player software. It does sound >>> interesting, but I rarely use media from my computer and have never found >>> a need.. >>> >>> >> I'll have a look at all that then, the media control is a HID profile >> btw(found that by accident looking into a IR remote and HID keyboard oddly >> enough). >> >>> I was actually looking at a Bluetooth capable printer (HP 470) on ebay the >>> other day, because I'm sick of using a BJ10 and I hate wires, though the >>> price seemed a little out of my range.. >>> >>> btw all the specifications are available from www.bluetooth.com :) >>> >>> >> Thanks Iain, I'll check it out :) >> >>> iain >>> >>> >> _______________________________________________ >> freebsd-bluetooth@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth >> To unsubscribe, send any mail to "freebsd-bluetooth-unsubscribe@freebsd.org" >> >>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4DF8430C.3010104>