settings usb mouse rate

[Alexander Best]

thanks for the info.

so right now i'm running the patched kernel with no problems whatsoever. mouse
is running smoothly with a rate of 1000. only values < 100 cause the issue i
mentioned beforehand with this mouse. unfortnunately i lost the manual, but i
think two of the buttons on this mouse are meant to control the rate. i don't
know if their're output is just being caught by some windows driver-app or if
the buttons control the mouse rate internaly. here's the output when pressing
both buttons:

Jul 14 19:39:54 otaku kernel: ums_intr_callback:206: sc=0xc826b000 actlen=8
Jul 14 19:39:54 otaku kernel: ums_intr_callback:224: data = 00 00 00 00 00 00
00 00
Jul 14 19:39:55 otaku kernel: ums_intr_callback:206: sc=0xc826b000 actlen=8
Jul 14 19:39:55 otaku kernel: ums_intr_callback:224: data = 00 00 00 01 00 00
00 00
Jul 14 19:39:55 otaku kernel: ums_intr_callback:282: x:0 y:0 z:-1 t:0 w:0
buttons:0x00000000
Jul 14 19:39:55 otaku kernel: ums_intr_callback:206: sc=0xc826b000 actlen=8
Jul 14 19:39:55 otaku kernel: ums_intr_callback:224: data = 00 00 00 00 00 00
00 00
Jul 14 19:39:55 otaku kernel: ums_intr_callback:206: sc=0xc826b000 actlen=8
Jul 14 19:39:55 otaku kernel: ums_intr_callback:224: data = 00 00 00 ff 00 00
00 00
Jul 14 19:39:55 otaku kernel: ums_intr_callback:282: x:0 y:0 z:1 t:0 w:0
buttons:0x00000000
Jul 14 19:39:55 otaku kernel: ums_intr_callback:206: sc=0xc826b000 actlen=8
Jul 14 19:39:55 otaku kernel: ums_intr_callback:224: data = 00 00 00 00 00 00
00 00
Jul 14 19:39:56 otaku kernel: ums_intr_callback:206: sc=0xc826b000 actlen=8
Jul 14 19:39:56 otaku kernel: ums_intr_callback:224: data = 00 00 00 ff 00 00
00 00
Jul 14 19:39:56 otaku kernel: ums_intr_callback:282: x:0 y:0 z:1 t:0 w:0
buttons:0x00000000
Jul 14 19:39:56 otaku kernel: ums_intr_callback:206: sc=0xc826b000 actlen=8
Jul 14 19:39:56 otaku kernel: ums_intr_callback:224: data = 00 00 00 00 00 00
00 00
Jul 14 19:39:56 otaku kernel: ums_intr_callback:206: sc=0xc826b000 actlen=8
Jul 14 19:39:56 otaku kernel: ums_intr_callback:224: data = 00 00 00 ff 00 00
00 00
Jul 14 19:39:56 otaku kernel: ums_intr_callback:282: x:0 y:0 z:1 t:0 w:0
buttons:0x00000000
Jul 14 19:39:56 otaku kernel: ums_intr_callback:206: sc=0xc826b000 actlen=8
Jul 14 19:39:56 otaku kernel: ums_intr_callback:224: data = 00 00 00 00 00 00
00 00
Jul 14 19:39:56 otaku kernel: ums_intr_callback:206: sc=0xc826b000 actlen=8
Jul 14 19:39:56 otaku kernel: ums_intr_callback:224: data = 00 00 00 ff 00 00
00 00
Jul 14 19:39:56 otaku kernel: ums_intr_callback:282: x:0 y:0 z:1 t:0 w:0
buttons:0x00000000
Jul 14 19:39:56 otaku kernel: ums_intr_callback:206: sc=0xc826b000 actlen=8
Jul 14 19:39:56 otaku kernel: ums_intr_callback:224: data = 00 00 00 00 00 00
00 00

alex

Hans Petter Selasky schrieb am 2009-07-14:
> On Tuesday 14 July 2009 18:29:33 Alexander Best wrote:
> > you were right. i attached a different usb mouse and setting the
> > rate to 10
> > or 100 didn't cause the random copy&paste issue.

> > what's the reason the usb polling rate is limited to 1000?
> > performance?
> > because gaming devices feature a very high rate. would be great to
> > have
> > full support for them. i've seen laser mice with a rate of 10.000.

> The USB hardware cannot poll more than 1000 times per second on
> INTERRUPT
> endpoints typically. Using a BULK endpoint you can at maximum poll
> 8000 times
> per second.

> --HPS