Date: Thu, 20 Jan 2011 09:55:39 -0800 From: Maksim Yevmenkin <maksim.yevmenkin@gmail.com> To: David Demelier <demelier.david@gmail.com> Cc: freebsd-bluetooth@freebsd.org Subject: Re: Bluetooth mouse does not connect after reboot Message-ID: <AANLkTimBRoSoYPTepFyiE9ezKLjtSsUPPe2hS0CDTJVt@mail.gmail.com> In-Reply-To: <4D37F7DB.4020709@gmail.com> References: <4D36ED39.7070807@gmail.com> <4D372C27.3040606@gmail.com> <AANLkTinmMHa-Mtf%2B=6jRBkFJ7j3hgJSZdjvcrOBB0%2BRN@mail.gmail.com> <4D37F7DB.4020709@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jan 20, 2011 at 12:52 AM, David Demelier <demelier.david@gmail.com> wrote: > On 19/01/2011 20:10, Maksim Yevmenkin wrote: >> >> On Wed, Jan 19, 2011 at 10:23 AM, David Demelier >> <demelier.david@gmail.com> wrote: >>> >>> It works ! In fact I didn't need to press the connect the button, only >>> moving it or clicking. It was easier than I tought. Thanks. >> >> great. glad to hear this :) >> >>> I'm just guessing, there is two more logical buttons in the wheel >>> (backward/forward) that are not understood by bthidd. >>> >>> Is this a bthidd limitation? >>> >>> [..snip..] >>> Input id=2 size=1 count=1 page=Button usage=Button_7 Variable, logical >>> range 0..1 >>> Input id=2 size=1 count=1 page=Button usage=Button_8 Variable, logical >>> range 0..1 >>> Input id=2 size=12 count=1 page=Generic_Desktop usage=X Variable >>> Relative, >>> logical range -2047..2047 >>> Input id=2 size=12 count=1 page=Generic_Desktop usage=Y Variable >>> Relative, >>> logical range -2047..2047 >>> Input id=2 size=8 count=1 page=Generic_Desktop usage=Wheel Variable >>> Relative, logical range -127..127 >>> Input id=2 size=8 count=1 page=Consumer usage=AC_Pan Variable Relative, >>> logical range -127..127 >>> End collection >>> >>> I think it should be the button 7 and 8 that are not usable. >> >> bthidd(8) has little to do with it. what bthidd(8) does is simply >> receives hid reports from the device, decodes hid reports according to >> the provided hid descriptor, and, feeds those events to kernel. >> freebsd syscons(4) relies heavily on moused(8) to handle things like >> double clicks etc. i did not want to replicate this in bthidd(8). >> bottom line is that bluetooth mouse in text console is kinda lacking, >> i.e. x, y, z direction and button clicks (single) -- basically >> MOUSE_ACTION ioctl. Xorg however, can be configured to support for all >> the buttons/wheels etc (using /dev/sysmouse as input device). >> >> thanks, >> max > > Then I should edit my mouse section in my xorg.conf ? I tried this : > > Section "InputDevice" > Identifier "Mouse0" > Driver "mouse" > Option "Protocol" "auto" > Option "Device" "/dev/sysmouse" > Option "ZAxisMapping" "4 5 6 7" > Option "Buttons" "7" > EndSection > > But it does not change anything could you please be more specific what exactly works and what does not? your configuration seems to be correct. so, i would expect that x, y and vertical scroll/wheel should work. horizontal scroll (AC_Pan) is not currently decoded by bthidd(8). while it is very easy to add it, mouse_info structure has no place to put the value in :( so, basically, bthidd(8) is limited by what sysmouse(4) can understand. thanks, max
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTimBRoSoYPTepFyiE9ezKLjtSsUPPe2hS0CDTJVt>