Hello,
I’m having problems with mouse response under X windows.
System:
QNX 4.24
Xgeneric (the X that QNX sold, not Xfree86)
DB9 serial mouse
/etc/config/sysinit.1:
mousetrap start
/etc/config/X11/Xconfig.1:
Mouse QNXmouse_2emulate3 /dev/mouse
When I start X, the mouse response is sluggish. It does work, but the
refresh rate seems slow. It’s like the mouse is only being updated at
3-4 Hz.
I don’t think it’s a CPU load problem - I have plenty of idle cycles.
Any ideas?
What does the throttle factor (-t) on Input do?
Paul wrote:
Hello,
I’m having problems with mouse response under X windows.
System:
QNX 4.24
Xgeneric (the X that QNX sold, not Xfree86)
DB9 serial mouse/etc/config/sysinit.1:
mousetrap start/etc/config/X11/Xconfig.1:
Mouse QNXmouse_2emulate3 /dev/mouseWhen I start X, the mouse response is sluggish. It does work, but the
refresh rate seems slow. It’s like the mouse is only being updated at
3-4 Hz.I don’t think it’s a CPU load problem - I have plenty of idle cycles.
Any ideas?
Look at the xset man pages.
Use “xset m” to set the X server mouse parameters. There are two
parameters: acceleration and threshold.
Acceleration can be an integral value or a fractional value (x/y); it
accelerates the pointer travel any time the
mouse is moved more than threshold pixels. This eliminates jitter on small
mouse movements, but moves the pointer
faster when the mouse is moved more.
“Paul” <pdkrocul@netscape.net> wrote in message
news:422F3ACB.683C2B08@netscape.net…
What does the throttle factor (-t) on Input do?
Paul wrote:
Hello,
I’m having problems with mouse response under X windows.
System:
QNX 4.24
Xgeneric (the X that QNX sold, not Xfree86)
DB9 serial mouse/etc/config/sysinit.1:
mousetrap start/etc/config/X11/Xconfig.1:
Mouse QNXmouse_2emulate3 /dev/mouseWhen I start X, the mouse response is sluggish. It does work, but the
refresh rate seems slow. It’s like the mouse is only being updated at
3-4 Hz.I don’t think it’s a CPU load problem - I have plenty of idle cycles.
Any ideas?
I found my problem to the mouse jitter, and I thought I’d document the
answer for others.
The system I was working on had:
Dev.ser -t 14
Which configures the UART to use a 14 character buffer. From what
I’ve read, the UART will only signal the CPU for service when 14
characters are recieved, OR when some characters have been received,
and 4 idle character frames have elapsed.
So, in my case, if the user was moving the mouse, the pointer would
only update after 14 bytes came in from the mouse.