Date: Tue, 14 Jul 2009 19:43:06 +0200 (CEST) From: Alexander Best <alexbestms@math.uni-muenster.de> To: Hans Petter Selasky <hselasky@c2i.net> Cc: freebsd-usb@freebsd.org Subject: Re: settings usb mouse rate Message-ID: <permail-20090714174306f7e55a9d000037d4-a_best01@message-id.uni-muenster.de> In-Reply-To: <200907141848.18037.hselasky@c2i.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?permail-20090714174306f7e55a9d000037d4-a_best01>