On 06/14/11 05:27, Maksim Yevmenkin wrote:
On Sun, Jun 12, 2011 at 11:48 PM, Iain Hibbert<[email protected]> wrote:
On Mon, 13 Jun 2011, Da Rock wrote:
On 06/12/11 17:30, Iain Hibbert wrote:
On Sun, 12 Jun 2011, Da Rock wrote:
Trying to get this device to work on my laptop (after some time of neglect
-
I've had no use or time to look into it as yet), but none of the drivers
seem
to be working. I've even tried the atheros driver by Rusty which doesn't
appear to be the same device anyway.
Under usbconfig I get:
<vendor 0x0b05 product 0x1712, class 224/1, rev 2.00/19.15, addr 2> on
usbus5
Any ideas?
class 224/1 is wireless/rf, is there a way to check the device protocol?
it should be 1 (bluetooth) for the ubt driver to match..
How do I find that out? Isn't it the rev number there? Or do I need to run a
command to find that out? I can't physically look at the device as its built
into the laptop board.
No, the rev number is the USB device rev number and AFAIK has no relevance
to anything..
usbconfig(8) manpage seems to be a bit sparse, you might have to check the
source for tips as to what it can print out..
if the device is built in, is there some way of disabling it? (my laptop
has a disable wireless switch, and also a disable bluetooth method.. mind
you, both of them cause the usb device to disappear entirely)
No. Its builtin and the only switch is for the wifi.
first, question: did you load ng_ubt(4) driver?
Naturally. Its in the handbook, and you never discount the handbook :)
if you did and device is still not recognized, could you please dump
device descriptor, i.e. use usbconfig(8) dump_device_desc command
ugen5.2: <product 0x1712 vendor 0x0b05> at usbus5, cfg=0 md=HOST
spd=FULL (12Mbps) pwr=ON
bLength = 0x0012
bDescriptorType = 0x0001
bcdUSB = 0x0200
bDeviceClass = 0x00e0
bDeviceSubClass = 0x0001
bDeviceProtocol = 0x0001
bMaxPacketSize0 = 0x0040
idVendor = 0x0b05
idProduct = 0x1712
bcdDevice = 0x1915
iManufacturer = 0x0000 <no string>
iProduct = 0x0000 <no string>
iSerialNumber = 0x0003 <0194E8-5B-0002>
bNumConfigurations = 0x0001
Also, what is the state of bluetooth 2.x? Everything I've read has only
mentioned 1.1.
4.0, 3.0& 2.x spec are all mostly backwards compatible (there are very
few deprecations) and the FreeBSD stack should continue to work on all
modern devices, albeit without advanced features..
Ok, I get that people are busy working on other (possibly) more important
things, but what is required to get the advanced features working? Where can I
find out the current status of these projects and how to help?
here :)
Good to know. I've been following the list for a while, just not
actively. I thought there might be project pages or something to read...
I'm currently learning about this technology (I know, late bloomer and all...
:) ) and its various features- which are why I'm looking carefully at it now
for my current needs. Unfortunately its the advanced features which I really
need :( So if I can help advance things I will.
what advanced features do you need?
I'm a little new to jargon, but the features are stereo audio, better
bitrates, remote control, phone control, etc (HSP, EDR, AV-something or
rather I think at least). Basically all the cool media stuff available
now that wasn't around with 1.x. Thats what has grabbed my interest now
anyway, file transfer, dun... meh- I can do that with wifi.
thanks, Iain :)
Iain, as to your previous post I thought I had recognized your name on
the list of other BSD flavours... :)
max
Thanks Max. What now? Can I add the product ID to the ng_ubt driver and
it just work? If so, any chance you could clarify the right way to do
that- I'm still a little green with coding for BSD :) (and once I have
done that and it works I'll swing it by you to check it out and commit
even if you don't mind).
Cheers
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth
To unsubscribe, send any mail to "[email protected]"
