Date: Mon, 20 Dec 2004 00:09:23 +0300 From: Vladimir Grebenschikov <vova@fbsd.ru> To: Maksim Yevmenkin <maksim.yevmenkin@savvis.net> Cc: bluetooth@freebsd.org Subject: Re: Bluetooth mouse Message-ID: <1103490563.1721.28.camel@localhost> In-Reply-To: <41C32471.2050805@savvis.net> References: <1100552998.1098.5.camel@localhost> <419B8353.7040908@savvis.net> <opshmg45c1lo1qsj@mail.xs4all.nl> <419B9EF8.2090401@savvis.net> <1103269957.974.7.camel@localhost> <41C32471.2050805@savvis.net>
next in thread | previous in thread | raw e-mail | index | archive | help
=F7 =D0=D4, 17/12/2004 =D7 10:24 -0800, Maksim Yevmenkin =D0=C9=DB=C5=D4:
> Vladimir,
> > Also, I think, it is better to provide usual /dev/*msX interface for
> > moused ?=20
>=20
> why?
Just because all other mouses use moused as userland programs to get
bytes from driver and push them to console.
Actually moused do two things
1. "knows" how to work with different mouse hardware
2. "knows" how to adjust mouse settings (rate, buttons mappings, axis,
wheels, 3-button emulation, double-click, resolution, etc)
And 1. is clearly has nothing to do with bluetooth mouse, but as for 2.
- I do not think we want to duplicate all these staff in bthidd.
Probably I was not right when talk about one more netgraph module, and
better way is to add opened bt socket support to moused and then spawn
moused from bthidd when new mouse connected.
What you think about this idea ?=20
> > It looks like I need to write ng node which will connect to l2cap node
> > one side and create /dev/btmsX on another side ?=20
>=20
> well, actually its much simpler :) most of the work already was done.=20
> take a look at /usr/src/usr.sbin/bluetooth/{bthidcontrol,bthidd}. these=20
> are not yet connected to the build, but you should be able to compile=20
> and run them.
Yes, good surprise !
> bthidcontrol(8) is a utility that can query bluetooth hid devices and=20
> create configuration for bthidd(8).
>=20
> % nroff -man bthidcontrol.8 | less -- for more information
>=20
> bthidd(8) is a bluetooth hid daemon (incomplete but mouse should work).=20
> it will read configuration created by bthidcontrol(8) and talk to=20
> bluetooth hid devices.
Unfortunately it does not work for me (I have write details in separate
message). So I need first get it work.
> whats needs to be done:
>=20
> 1) finish and test bthidd(8) and vkbd(4) integration (bluetooth keyboard=20
> support). i've done most of it, but was never able to finish and test it =
:(
Unfortunately still have not bluetooth keyboard.
> 2) better handling of bluetooth mouse events, i.e. detect double clicks=20
> etc. and send appropriate ioctl(2) to /dev/console. double clicks etc.=20
> will work in X, but not in the text mode.
Yes, it is what I talk before, all these stuff is already exists in
moused.
> thanks,
> max
--=20
Vladimir B. Grebenchikov
vova@fbsd.ru
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1103490563.1721.28.camel>