On Fri, Sep 19, 2008 at 01:29:58PM +0200, Søren Hauberg wrote:
I do have a follow-up question (you can't get rid of me that easy :-)
). I have modified the 'usbtouchscreen' kernel module such that it can
use calibration parameters. With this in place, my touchscreen works
in X with the 'evdev'
Søren Hauberg wrote:
I'm sorry but I don't quite understand (I don't know that much about
either X, nor the kernel). But you think it would be better to solve
this in X, right? Via a special driver for touch screens? And then I
can use these 'device properties' to set the calibration
2008/9/22 Peter Hutterer [EMAIL PROTECTED]:
On Fri, Sep 19, 2008 at 01:29:58PM +0200, Søren Hauberg wrote:
I do have a follow-up question (you can't get rid of me that easy :-)
). I have modified the 'usbtouchscreen' kernel module such that it can
use calibration parameters. With this in
Søren Hauberg wrote:
I do have a follow-up question (you can't get rid of me that easy :-)
). I have modified the 'usbtouchscreen' kernel module such that it can
use calibration parameters. With this in place, my touchscreen works
in X with the 'evdev' driver, i.e. out of the box. Do you guys
Søren Hauberg wrote:
Can I somehow force the evdev driver to only accept absolute events?
I'll see if I can find the time to look into fixing the issue, as I
guess it could be related to my problems. But like everybody else I'm
in lack of time, so I'm not sure if it'll be doable.
Adding an
2008/9/18 Peter Hutterer [EMAIL PROTECTED]:
On Wed, Sep 17, 2008 at 06:46:17AM -0700, Hauberg wrote:
Now, my problem is that X seems to somehow accelerate the output from the
'usbtouchscreen' module, so that when I move my finger to the left, the
cursor moves about twice as far to the left
that output is sent from 'usbtouchscreen'
using 'input_report_abs' which calls 'input_event' with the 'EV_ABS' flag.
--
View this message in context:
http://www.nabble.com/Raw-mouse-input-is-distorted-tp19532482p19532482.html
Sent from the Free Desktop - xorg mailing list archive at Nabble.com
Søren Hauberg wrote:
2008/9/17 Simon Thum [EMAIL PROTECTED]:
Yeah, it does some fancy things for relative devices. Technically, you don't
have one, but you should be able to suppress it with
xset 1 1
crap. I meant
xset m 1 1
the kernel. But I'm a bit confused about one thing: the kernel
On Wed, Sep 17, 2008 at 09:26:08PM +0200, Simon Thum wrote:
Maybe evdev works better? I seems there is a problem when both absolute
AND relative axes are exposed,
The reason for this is that there's a couple of popular devices
(keyboard/mouse combos) that claim to have both relative x/y axes
