[PATCH] Add "input.mouse" capability to VMware's absolute USB mouse

[Philip Langdale]

Matthew Garrett wrote:
> 
> On Wed, Jan 30, 2008 at 02:01:44AM -0800, Vinay Reddy wrote:
>> Currently, VMware's absolute USB mouse is not correctly tagged by hald
>> (it only gets the "input" capability). Here's a patch that adds the
>> "input.mouse" capability to VMware's absolute USB mouse.
> 
> It turns out that this makes flagging joysticks correctly kind of
> awkward. Do you have the evtest output for the vmware emulated mouse?

Hi Matthew,

I know you already proposed a fix for this in a separate patch - which
gets my thumbs up, but here's the evtest output:

> Input driver version is 1.0.0
> Input device ID: bus 0x3 vendor 0xe0f product 0x3 version 0x110
> Input device name: "VMware VMware Virtual USB Mouse"
> Supported events:
>   Event type 0 (Reset)
>     Event code 0 (Reset)
>     Event code 1 (Key)
>     Event code 2 (Relative)
>     Event code 3 (Absolute)
>     Event code 4 (?)
>   Event type 1 (Key)
>     Event code 272 (LeftBtn)
>     Event code 273 (RightBtn)
>     Event code 274 (MiddleBtn)
>     Event code 275 (SideBtn)
>     Event code 276 (ExtraBtn)
>   Event type 2 (Relative)
>     Event code 8 (Wheel)
>   Event type 3 (Absolute)
>     Event code 0 (X)
>       Value  39607
>       Min        0
>       Max    65535
>     Event code 1 (Y)
>       Value  34038
>       Min        0
>       Max    65535
>   Event type 4 (?)
>     Event code 4 (?)

I guess it's worth pointing out that it's technically not VMware specific -
there are other devices out there that look like non-touch absolute devices;
I've seen discussion about an HP ILO device that presents its mouse input in
the same way.

Thanks,

--phil