Re: usb2 moused issue (Microsoft Wireless Optical)

On Mon, 16 Feb 2009 22:12:36 +0100, Hans Petter Selasky <hselasky_at_freebsd.org> wrote:
> On Monday 16 February 2009, Giorgos Keramidas wrote:
>> It was opened by moused, so I killed it.  There's no output when I
>> attach and move the mouse, other than the following in syslog:
>>
>> Feb 16 21:37:45 kobe kernel: ugen4.2: <Microsoft> at usbus4
>> Feb 16 21:37:45 kobe kernel: ums0: <Microsoft Wireless Optical Mouse 3000
>> (Model 1056), class 0/0, rev 2.00/0.07, addr 2> on usbus4 Feb 16 21:37:45
>> kobe kernel: ums0: 5 buttons and [XYZ] coordinates Feb 16 21:37:45 kobe
>> kernel: ums_attach:582: sc=0xc63cd800
>> Feb 16 21:37:45 kobe kernel: ums_attach:583: X  48/8
>> Feb 16 21:37:45 kobe kernel: ums_attach:584: Y  56/8
>> Feb 16 21:37:45 kobe kernel: ums_attach:585: Z  64/8
>> Feb 16 21:37:45 kobe kernel: ums_attach:586: T  0/0
>> Feb 16 21:37:45 kobe kernel: ums_attach:587: W  0/0
>> Feb 16 21:37:45 kobe kernel: ums_attach:591: B1 40/1
>> Feb 16 21:37:45 kobe kernel: ums_attach:591: B2 41/1
>> Feb 16 21:37:45 kobe kernel: ums_attach:591: B3 42/1
>> Feb 16 21:37:45 kobe kernel: ums_attach:591: B4 43/1
>> Feb 16 21:37:45 kobe kernel: ums_attach:591: B5 44/1
>> Feb 16 21:37:45 kobe kernel: ums_attach:593: size=2, id=19
>> Feb 16 21:37:45 kobe kernel: Symlink: ums0 -> usb4.2.0.16
>>
>> When I kill the moused instance that is launched on attach by devd,
>> start a `cat /dev/ums0' command and move the mouse, click a few buttons,
>> etc. there is no output at all.
>
> Hi,
>
> I found a bug in the HID library:
>
> Can you try the following patch:
>
> http://perforce.freebsd.org/chv.cgi?CH=157814

This looks ok.  I'll give it a run in a few minutes, thanks :-)