cvs commit: src/share/man/man4 Makefile ng_bluetooth.4 ng_bt3c.4 ng_btsocket.4 ng_h4.4 ng_hci.4 ng_l2cap.4 ng_ubt.4 ubtbcmfw.4 src/sys/modules/netgraph/bluetooth Makefile src/sys/modules/netgraph/bluetooth/bluetooth Makefile src/sys/modules/netgraph/bluetooth/bt3c Makefile ...

[Maksim Yevmenkin]

Folks,

i'm sorry for the late reply :)

[...]

> > >> >   Submitted by:   Maksim Yevmenkin <m_evmenkin at yahoo.com>
> > >> >   Approved by: re@
> > >> 
> > >> What is the actual content?  New features, bugfixes?
> > > 
> > > lots of bugfixes and code to support new devices and features.
> > 
> > Usually an abbreviated list of these things is included in commit
> > messages when drivers are updated.  Otherwise, people don't know
> > what new devices are supported, what bugs are fixed, etc.
> 
> 	Maxsim is really good at giving us nice hints
> 	about what stuff is supported by his latest code drop! (on
> 	-current).  I wouldn't mind setting up project page, e.g.
> 	http://www.FreeBSD.ORG/projects/bluetooth, if time permits;
> 	provided Maksim provides me with some sort of a list! 8-)

first of all let me appologize for the size of the patches (quite extensive)
and for the inappropriate time (just before 5.1R) they went in :) i will most
definetely try to avoid doing such things in the future :)

as Hiten said, i try to list important things in the message every time i
make new snapshot available for download. it is clearly not the best way.
perhaps i should maintain ChangeLog file somewhere and include it in the
snapshot. i can also send the the list of changes every time i submit the
patches to Julian.

as for supported device list then, frankly, i can't help :) Bluetooth spec
defines the way Host (PC) should talk to Host Controller (device). device
could be serial (RS-232), UART or USB. external serial dongles should work.
UART based devices may or may not work. it depends on sio(4) driver. if sio(4)
supports UART in the device then it will work, otherwise it will not. of 
course serial/UART based devices do not work very well because of "sio 
overflow" problem, and Bluetooth *can not* tolerate that. all USB devices
should work as long as they are conform the Bluetooth spec. USB device should
have bDeviceClass, bDeviceSubClass and bDeviceProtocol set to certain values.
the ng_ubt(4) driver has generic ATTACH routine that checks for these values.
all Bluetooth devices are based on Bluetooth chips from few different vendors,
i.e. CSR, Broadcomm etc. it does not really matter what label is on the
device, but rather what chip inside. 

as reference you can look at USB devices section at

http://www.holtmann.org/linux/bluetooth/devices.html

if "driver" column says "hci_usb" or "hci_usb + bluefw" then the device is
most likely to work with FreeBSD.

thanks
max

__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com