Logitech V470 Bluetooth Mouse on FreeBSD ?

[martinko-5]

Hallo lists,

I'm considering buying Logitech V470 Bluetooth Mouse.
Does anyone have any experience with using this mouse on FreeBSD please ?

Cheers,

Martin

PS: Please CC me as I'm not on the lists.
_______________________________________________
freebsd-bluetooth@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth
To unsubscribe, send any mail to "freebsd-bluetooth-unsubscribe@..."

[Maksim Yevmenkin-2]

Martin,

>  I'm considering buying Logitech V470 Bluetooth Mouse.
>  Does anyone have any experience with using this mouse on FreeBSD please ?

chances are it will work. i personally never tried this particular
model, but bluetooth mice from different manufacturers (for example
apple and microsoft) are known to work.

thanks,
max
_______________________________________________
freebsd-bluetooth@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth
To unsubscribe, send any mail to "freebsd-bluetooth-unsubscribe@..."

[martinko-5]

Maksim Yevmenkin wrote:

> Martin,
>
>  
>>  I'm considering buying Logitech V470 Bluetooth Mouse.
>>  Does anyone have any experience with using this mouse on FreeBSD please ?
>>    
>
> chances are it will work. i personally never tried this particular
> model, but bluetooth mice from different manufacturers (for example
> apple and microsoft) are known to work.
>
> thanks,
> max
>  

Hi Max,

I've just bought the mouse and it works, partially.
Well, I couldn't find anything in the handbook but google helped.

However, the mouse has 4-way wheel but horizontal scrolling doesn't work.
I've got the following in my xorg.conf:

Section "InputDevice"
        Identifier  "Mouse0"
        Driver      "mouse"
        Option      "Protocol" "auto"
        Option      "Device" "/dev/sysmouse"
        Option      "ZAxisMapping" "4 5 6 7"
EndSection

Any ideas pls ?

Apart from that I noticed double clicks don't work in console.

With regards,

Martin
_______________________________________________
freebsd-bluetooth@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth
To unsubscribe, send any mail to "freebsd-bluetooth-unsubscribe@..."

[Yousif Hassan]

> However, the mouse has 4-way wheel but horizontal scrolling doesn't work.
> I've got the following in my xorg.conf:
>
> Section "InputDevice"
>        Identifier  "Mouse0"
>        Driver      "mouse"
>        Option      "Protocol" "auto"
>        Option      "Device" "/dev/sysmouse"
>        Option      "ZAxisMapping" "4 5 6 7"
> EndSection
>
> Any ideas pls ?
>
> Apart from that I noticed double clicks don't work in console.

If memory serves, the latter issue is a limitation in the FreeBSD bluetooth
stack, so it's not related to your mouse.  I believe the fomer issue as
well, but I am not as certain as for the double-click problem.

--Y

_______________________________________________
freebsd-bluetooth@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth
To unsubscribe, send any mail to "freebsd-bluetooth-unsubscribe@..."

[Maksim Yevmenkin-2]

 Martin,

>  I've just bought the mouse and it works, partially.
>  Well, I couldn't find anything in the handbook but google helped.
>
>  However, the mouse has 4-way wheel but horizontal scrolling doesn't work.
>  I've got the following in my xorg.conf:
>
>  Section "InputDevice"
>        Identifier  "Mouse0"
>        Driver      "mouse"
>        Option      "Protocol" "auto"
>        Option      "Device" "/dev/sysmouse"
>        Option      "ZAxisMapping" "4 5 6 7"
>  EndSection
>
>  Any ideas pls ?

as Iain already pointed out, you might try adding 'Option "Buttons"
"7"'. also it would be nice if you post hid descriptor for the mouse
from your /etc/bluetooth/bthidd.conf

>  Apart from that I noticed double clicks don't work in console.

yes, from bthidd(8) man page

KNOWN LIMITATIONS
     The bthidd daemon currently does not handle key auto repeat and double
     click mouse events.  Those events work under X(7) just fine, but not in
     text console.

thanks,
max
_______________________________________________
freebsd-bluetooth@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth
To unsubscribe, send any mail to "freebsd-bluetooth-unsubscribe@..."

[martinko-5]

Iain Hibbert wrote:

> On Sun, 30 Mar 2008, mato wrote:
>
>  
>> Section "InputDevice"
>>        Identifier  "Mouse0"
>>        Driver      "mouse"
>>        Option      "Protocol" "auto"
>>        Option      "Device" "/dev/sysmouse"
>>        Option      "ZAxisMapping" "4 5 6 7"
>> EndSection
>>    
>
> FWIW this at least is probably correct, but I found that last year when I
> bought an "Apple Mighty Mouse" I still had some trouble because the
> bsd_mouse driver for X was not handling the Z direction. Of course, this
> was on NetBSD/wsmouse so it is different but the bsd_mouse.c file s the
> same handler.
>
> Also you may need
> Option        "Buttons" "7"
>
>  

I hadn't found this option in xorg.conf manual.  Thanks.
Unfortunately it did not help in this case.

>> Any ideas pls ?
>>    
>
> also, I think bthidd does not handle the Z direction**. Note that
> sometimes a mouse will present the horizontal component of the scroll ball
> as "Consumer/PAN" instead of "Generic Desktop/Z"
>
> hth,
> iain
>
> ** confusingly, HUG_WHEEL is the vertical scroll and HUG_Z is horizontal
> but the vertical scroll is internally called Z and sometimes HUG_Z is the
> vertical direction when there is no HUG_WHEEL.
>  

Well, this mouse of mine presents itself exactly as you said ...

Input   id=2 size=12 count=1 page=Generic_Desktop usage=X Variable
Relative, log
ical range -2047..2047
Input   id=2 size=12 count=1 page=Generic_Desktop usage=Y Variable
Relative, log
ical 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, logica
l range -127..127

What can be done about it ??

Cheers,

Martin
_______________________________________________
freebsd-bluetooth@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth
To unsubscribe, send any mail to "freebsd-bluetooth-unsubscribe@..."

[martinko-5]

Maksim Yevmenkin wrote:

>  Martin,
>
>  
>>  I've just bought the mouse and it works, partially.
>>  Well, I couldn't find anything in the handbook but google helped.
>>
>>  However, the mouse has 4-way wheel but horizontal scrolling doesn't work.
>>  I've got the following in my xorg.conf:
>>
>>  Section "InputDevice"
>>        Identifier  "Mouse0"
>>        Driver      "mouse"
>>        Option      "Protocol" "auto"
>>        Option      "Device" "/dev/sysmouse"
>>        Option      "ZAxisMapping" "4 5 6 7"
>>  EndSection
>>
>>  Any ideas pls ?
>>    
>
> as Iain already pointed out, you might try adding 'Option "Buttons"
> "7"'. also it would be nice if you post hid descriptor for the mouse
> from your /etc/bluetooth/bthidd.conf
>
>  
>>  Apart from that I noticed double clicks don't work in console.
>>    
>
> yes, from bthidd(8) man page
>
> KNOWN LIMITATIONS
>      The bthidd daemon currently does not handle key auto repeat and double
>      click mouse events.  Those events work under X(7) just fine, but not in
>      text console.
>
> thanks,
> max
>  

Hi Max,

Option Buttons did not help me. :-(

$ bthidcontrol -a mato-mouse query
device {
        bdaddr                  00:07:61:a7:64:15;
        control_psm             0x11;
        interrupt_psm           0x13;
        reconnect_initiate      true;
        battery_power           true;
        normally_connectable    false;
        hid_descriptor          {
                0x05 0x01 0x09 0x02 0xa1 0x01 0x85 0x02
                0x09 0x01 0xa1 0x00 0x05 0x09 0x19 0x01
                0x29 0x08 0x15 0x00 0x25 0x01 0x75 0x01
                0x95 0x08 0x81 0x02 0x05 0x01 0x09 0x30
                0x09 0x31 0x16 0x01 0xf8 0x26 0xff 0x07
                0x75 0x0c 0x95 0x02 0x81 0x06 0x09 0x38
                0x15 0x81 0x25 0x7f 0x75 0x08 0x95 0x01
                0x81 0x06 0x05 0x0c 0x0a 0x38 0x02 0x75
                0x08 0x95 0x01 0x81 0x06 0xc0 0xc0 0x06
                0x00 0xff 0x09 0x01 0xa1 0x01 0x85 0x10
                0x75 0x08 0x95 0x06 0x15 0x00 0x26 0xff
                0x00 0x09 0x01 0x81 0x00 0x09 0x01 0x91
                0x00 0xc0
        };
}

$ bthidcontrol -a mato-mouse dump
Collection page=Generic_Desktop usage=Mouse
Collection page=Generic_Desktop usage=Pointer
Input   id=2 size=1 count=1 page=Button usage=Button_1 Variable, logical
range 0
..1
Input   id=2 size=1 count=1 page=Button usage=Button_2 Variable, logical
range 0
..1
Input   id=2 size=1 count=1 page=Button usage=Button_3 Variable, logical
range 0
..1
Input   id=2 size=1 count=1 page=Button usage=Button_4 Variable, logical
range 0
..1
Input   id=2 size=1 count=1 page=Button usage=Button_5 Variable, logical
range 0
..1
Input   id=2 size=1 count=1 page=Button usage=Button_6 Variable, logical
range 0
..1
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, log
ical range -2047..2047
Input   id=2 size=12 count=1 page=Generic_Desktop usage=Y Variable
Relative, log
ical 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, logica
l range -127..127
End collection
End collection
Input   id=16 size=8 count=6 page=Microsoft usage=0x0001, logical range
0..255
Output  id=16 size=8 count=6 page=Microsoft usage=0x0001, logical range
0..255
Collection page=Microsoft usage=0x0001

_______________________________________________
freebsd-bluetooth@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth
To unsubscribe, send any mail to "freebsd-bluetooth-unsubscribe@..."

[Iain Hibbert]

On Mon, 31 Mar 2008, mato wrote:

> Well, this mouse of mine presents itself exactly as you said ...
>
> Input   id=2 size=12 count=1 page=Generic_Desktop usage=X Variable Relative,
> Input   id=2 size=12 count=1 page=Generic_Desktop usage=Y Variable Relative,

wow thats a sensitive mouse, 12 bit movements! :)

> Input   id=2 size=8 count=1 page=Generic_Desktop usage=Wheel Variable
> Input   id=2 size=8 count=1 page=Consumer usage=AC_Pan Variable Relative,
>
> What can be done about it ??

I don't know - bthidd(4) could grow the support for AC_Pan fairly easily
but I don't know how you would get that into the kernel - the mouse_info
structure has no W direction and the ioctl would need to be versioned if
the structure was extended as there was no padding..

btw just to make you feel better I should say that sideways scroll does
not always work in applications; eg GThumb considers the extra buttons
to be 'next' and 'prev' instead and sideways scroll just jumps to the next
picture.

iain
_______________________________________________
freebsd-bluetooth@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth
To unsubscribe, send any mail to "freebsd-bluetooth-unsubscribe@..."

[Maksim Yevmenkin-2]

On 4/2/08, Iain Hibbert <plunky@...> wrote:
> On Mon, 31 Mar 2008, mato wrote:
>
> > Well, this mouse of mine presents itself exactly as you said ...
> >
> > Input   id=2 size=12 count=1 page=Generic_Desktop usage=X Variable Relative,
> > Input   id=2 size=12 count=1 page=Generic_Desktop usage=Y Variable Relative,
>
> wow thats a sensitive mouse, 12 bit movements! :)

amazing what you can get these days, huh? :)

> > Input   id=2 size=8 count=1 page=Generic_Desktop usage=Wheel Variable
> > Input   id=2 size=8 count=1 page=Consumer usage=AC_Pan Variable Relative,
> > What can be done about it ??
>
> I don't know - bthidd(4) could grow the support for AC_Pan fairly easily
>  but I don't know how you would get that into the kernel - the mouse_info
>  structure has no W direction and the ioctl would need to be versioned if
>  the structure was extended as there was no padding..

exactly Iain. parsing hid messages in bthidd(8) and extracting all the
data is trivial. the question is how to feed those data into the
kernel. right now, bthidd(8) uses console ioctl to feed data into the
kernel. as you pointed out, mouse_info structure (specifically
mouse_data union) does not have have w direction.

>  btw just to make you feel better I should say that sideways scroll does
>  not always work in applications; eg GThumb considers the extra buttons
>  to be 'next' and 'prev' instead and sideways scroll just jumps to the next
>  picture.

i have a wired usb apple mighty mouse here and horizontal scrolling
does not work for me at all. quick look at ums(4) showed that it does
not export w data (it tries to locate both wheel and z axis, however
it does not look for ac_pan axis).

so, it appears that we need to teach moused(8), sysmouse(4) and mice
drivers about second wheel. it appears to be a somewhat bigger chunk
of work.

thanks,
max


>
>
>  iain
>
_______________________________________________
freebsd-bluetooth@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth
To unsubscribe, send any mail to "freebsd-bluetooth-unsubscribe@..."

[Mark Hobden-2]

On 02/04/2008, Maksim Yevmenkin <maksim.yevmenkin@...> wrote:

> > I don't know - bthidd(4) could grow the support for AC_Pan fairly easily
>  >  but I don't know how you would get that into the kernel - the mouse_info
>  >  structure has no W direction and the ioctl would need to be versioned if
>  >  the structure was extended as there was no padding..
>
>  exactly Iain. parsing hid messages in bthidd(8) and extracting all the
>  data is trivial. the question is how to feed those data into the
>  kernel. right now, bthidd(8) uses console ioctl to feed data into the
>  kernel. as you pointed out, mouse_info structure (specifically
>  mouse_data union) does not have have w direction.
>
>  >  btw just to make you feel better I should say that sideways scroll does
>  >  not always work in applications; eg GThumb considers the extra buttons
>  >  to be 'next' and 'prev' instead and sideways scroll just jumps to the next
>  >  picture.
>
>  i have a wired usb apple mighty mouse here and horizontal scrolling
>  does not work for me at all. quick look at ums(4) showed that it does
>  not export w data (it tries to locate both wheel and z axis, however
>  it does not look for ac_pan axis).
>
>  so, it appears that we need to teach moused(8), sysmouse(4) and mice
>  drivers about second wheel. it appears to be a somewhat bigger chunk
>  of work.
>
>  thanks,
>  max

Hi Martin,

I have a patch somewhere at home that manages to do all of the above. I
had planned to re-wite part of it to not require increasing the size of an xorg
structure I changed - but it doesn't look like I will have time to do that for a
while.

At present it applies on top of the uhidev patches but it probably wouldn't
be too difficult to get it to apply without them. I have been using it
for a little
while now and its been working fine for me.

I will try and clean it up and document what needs to be re-compiled to get it
working and then post it sometime in the next few days.

Kind Regards,

Mark Hobden.
_______________________________________________
freebsd-bluetooth@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth
To unsubscribe, send any mail to "freebsd-bluetooth-unsubscribe@..."

[martinko-5]

Iain Hibbert wrote:

> On Mon, 31 Mar 2008, mato wrote:
>
>  
>> Well, this mouse of mine presents itself exactly as you said ...
>>
>> Input   id=2 size=12 count=1 page=Generic_Desktop usage=X Variable Relative,
>> Input   id=2 size=12 count=1 page=Generic_Desktop usage=Y Variable Relative,
>>    
>
> wow thats a sensitive mouse, 12 bit movements! :)
>
>  

Well, I don't know how much is it -- 12 bits across what ?  1 inch ?

Anyway, I must say that mouse is quite sensitive and I'd like to adjust
it a bit as it's sometimes difficult to control.  However, I've no idea
how to achieve this.  Any suggestions please ?

>> Input   id=2 size=8 count=1 page=Generic_Desktop usage=Wheel Variable
>> Input   id=2 size=8 count=1 page=Consumer usage=AC_Pan Variable Relative,
>>
>> What can be done about it ??
>>    
>
> I don't know - bthidd(4) could grow the support for AC_Pan fairly easily
> but I don't know how you would get that into the kernel - the mouse_info
> structure has no W direction and the ioctl would need to be versioned if
> the structure was extended as there was no padding..
>
> btw just to make you feel better I should say that sideways scroll does
> not always work in applications; eg GThumb considers the extra buttons
> to be 'next' and 'prev' instead and sideways scroll just jumps to the next
> picture.
>
> iain
>  

Well, I would expect "better" applications would allow to configure
those extra buttons.
Anyway, it's a bit shame having these cool buttons with no way to use
them. :-(

Regards,

Martin
_______________________________________________
freebsd-bluetooth@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth
To unsubscribe, send any mail to "freebsd-bluetooth-unsubscribe@..."

[martinko-5]

Maksim Yevmenkin wrote:

> On 4/2/08, Iain Hibbert <plunky@...> wrote:
>  
>> On Mon, 31 Mar 2008, mato wrote:
>>    
>>> Input   id=2 size=8 count=1 page=Generic_Desktop usage=Wheel Variable
>>> Input   id=2 size=8 count=1 page=Consumer usage=AC_Pan Variable Relative,
>>> What can be done about it ??
>>>      
>> I don't know - bthidd(4) could grow the support for AC_Pan fairly easily
>>  but I don't know how you would get that into the kernel - the mouse_info
>>  structure has no W direction and the ioctl would need to be versioned if
>>  the structure was extended as there was no padding..
>>    
>
> exactly Iain. parsing hid messages in bthidd(8) and extracting all the
> data is trivial. the question is how to feed those data into the
> kernel. right now, bthidd(8) uses console ioctl to feed data into the
> kernel. as you pointed out, mouse_info structure (specifically
> mouse_data union) does not have have w direction.
>
>  
>>  btw just to make you feel better I should say that sideways scroll does
>>  not always work in applications; eg GThumb considers the extra buttons
>>  to be 'next' and 'prev' instead and sideways scroll just jumps to the next
>>  picture.
>>    
>
> i have a wired usb apple mighty mouse here and horizontal scrolling
> does not work for me at all. quick look at ums(4) showed that it does
> not export w data (it tries to locate both wheel and z axis, however
> it does not look for ac_pan axis).
>
> so, it appears that we need to teach moused(8), sysmouse(4) and mice
> drivers about second wheel. it appears to be a somewhat bigger chunk
> of work.
>
>  

The current situation seems to me not ideal and rather complicated.  You
said bthidd injects messages directly to kernel.  I don't know what the
consequences are but I noticed the following ... When I run moused my BT
mouse works in console (except double clicks etc.).  Unfortunately,
because I wanted extra functionality from my Synaptics touchpad I
installed x11-drivers/synaptics port which required disabling moused
which handled the touchpad as ps/2 mouse.  Now synaptics works great in
X11 but it doesn't work in console at all and my BT mouse doesn't work
in console either.  But if I plug in a USB mouse devd runs moused and
suddenly my BT mouse works in console too.  Funny but very inconvenient,
I can tell you.  Fortunately I don't work in console that much anymore.

With regards,

Martin
_______________________________________________
freebsd-bluetooth@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth
To unsubscribe, send any mail to "freebsd-bluetooth-unsubscribe@..."

[Maksim Yevmenkin-2]

[...]

> > i have a wired usb apple mighty mouse here and horizontal scrolling
> > does not work for me at all. quick look at ums(4) showed that it does
> > not export w data (it tries to locate both wheel and z axis, however
> > it does not look for ac_pan axis).
> >
> > so, it appears that we need to teach moused(8), sysmouse(4) and mice
> > drivers about second wheel. it appears to be a somewhat bigger chunk
> > of work.
>
>  The current situation seems to me not ideal and rather complicated.  You
> said bthidd injects messages directly to kernel.  I don't know what the
> consequences are but I noticed the following ... When I run moused my BT
> mouse works in console (except double clicks etc.).  Unfortunately, because
> I wanted extra functionality from my Synaptics touchpad I installed
> x11-drivers/synaptics port which required disabling moused which handled the
> touchpad as ps/2 mouse.  Now synaptics works great in X11 but it doesn't
> work in console at all and my BT mouse doesn't work in console either.  But
> if I plug in a USB mouse devd runs moused and suddenly my BT mouse works in
> console too.  Funny but very inconvenient, I can tell you.  Fortunately I
> don't work in console that much anymore.

freebsd offers something called sysmouse(4). it allows the console and
the user process (such as xorg) to share the mouse. if you use
sysmouse(4) in xorg - the mouse will be shared between both console
and xorg. if you use specific mouse driver (such as ums(4)) you will
need to put /dev/ums0 in your xorg.conf and use appropriate xorg mouse
driver. in the later case, the mouse will not be shared and will not
work in the console.

bthidd(8) uses console ioctl's to feed bluetooth mouse events into the
kernel (i.e. feed events to sysmouse(4)). this way we automatically
share bluetooth mouse between console and xorg. however, because
sysmouse(4) protocol lacks knowledge about all the fancy buttons and
wheels we can not pass this data to xorg. basically we are limited to
whatever sysmouse(4) protocol knows about.

currently, it is not possible to use bluetooth mouse directly from
xorg/whatever, because there is no device node for it. in other words,
there is no /dev/btmsX device node that feeds data in some protocol to
consumers. i guess, it would be possible to write virtual mouse vms(4)
driver (similar to virtual keyboard driver vkbd(4)) that would simply
be used to pass through mouse data in, say, microsoft protocol or
something like that. however, i think it would be better to add
another level of operation to sysmouse(4) and change protocol so it
can accommodate future extensions.

thanks,
max

>
>  With regards,
>
>  Martin
>
_______________________________________________
freebsd-bluetooth@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth
To unsubscribe, send any mail to "freebsd-bluetooth-unsubscribe@..."