As per my last comment, closing this bug as out of date; we're focusing
on -evdev for touch displays now, so if evdev does not support that
device, a bug report should be filed against -evdev (or really, against
the kernel, since the X evdev driver is just a reflection of the kernel
evdev support.)
xserver-xorg-input-evdev would be the package to file evdev issues
against.
Loic, it would be helpful if you could re-test this at some point with
-evdev. It's probably too late now for Intrepid so no big hurry to
test.
** Changed in: xf86-input-evtouch (Ubuntu)
Assignee: Bryce Harrington (
Sorry, xserver-xorg-evdev. Essentially, I'm wondering whether it is
possible to calibrate absolute input device max/min values using some
undocumented "xinput set-int-prop"
--
Uncalibrated and can't calibrate with 0.8.7-2 on Samsung Q1 Ultra
https://bugs.launchpad.net/bugs/163850
You received thi
What package should we report input-hotplug touchscreen problems
against? xorg-server-evdev?
--
Uncalibrated and can't calibrate with 0.8.7-2 on Samsung Q1 Ultra
https://bugs.launchpad.net/bugs/163850
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
For Intrepid we do plan to switch to input-hotplug (and evdev), so if
that makes this problem go away, we can consider that the solution. I'm
anticipating this deployed in Intrepid within a month or so.
** Changed in: xf86-input-evtouch (Ubuntu)
Status: Confirmed => Triaged
--
Uncalibrat
I just installed 8.04 on a new machine that has an older Microtouch-
based screen. By default X coordinates are find but Y is reversed.
Swapping MinY and MaxY cause the pointer to get stuck at the bottom.
Tracking through the code, I indeed found that *conversion_proc() is no
longer called. I fil
I had some issues with calibration as well, here is my experience :
* Problem 1 : ev_calibrate searches for /empty_cursor.xpm (bug that
should be fixed), thus, no display is available. Copying the xpm at the
right place "/" solves the issue.
* Problem 2 : no text is present, to activate the cal
** Changed in: xf86-input-evtouch (Ubuntu)
Importance: Undecided => High
Assignee: (unassigned) => Bryce Harrington (bryceharrington)
Status: New => Confirmed
--
Uncalibrated and can't calibrate with 0.8.7-2 on Samsung Q1 Ultra
https://bugs.launchpad.net/bugs/163850
You received th
I have similar problems with another touch screen, calibrate.sh always returns
the same values for MinX/Y and x/y0 points, which do not work.
Only the upper left part of the screen can be made to work (get the mouse
moving actually :p) by tweaking the settings by hand.
I: Bus=0003 Vendor=0430 Pr
Relevant /proc/bus/input/devices extract to help configuring evdev for
anyone capable of reading this:
I: Bus=0003 Vendor=0eef Product=0001 Version=0112
N: Name="Touchkit Touch"
P: Phys=usb-:00:1d.1-1/input0
S: Sysfs=/class/input/input2
U: Uniq=
H: Handlers=mouse1 event2
B: EV=b
B: KEY=401 0
** Tags added: ume-hardy-regressions
--
Uncalibrated and can't calibrate with 0.8.7-2 on Samsung Q1 Ultra
https://bugs.launchpad.net/bugs/163850
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bu
One option worth investigating, as pointed by Mike, is whether we could
now switch to evdev from the xserver-xorg-input-evdev package (based on
the upstream xf86-input-evdev module). hardy has version
1:1.2.0~git20070819-4 and gutsy had 1:1.1.5-3; the module seems to have
seen major update for the
Also reported as broken with xorg 1.4 in Gentoo:
http://gentoo-wiki.com/HARDWARE_Samsung_UMPC_Q1-Ultra
--
Uncalibrated and can't calibrate with 0.8.7-2 on Samsung Q1 Ultra
https://bugs.launchpad.net/bugs/163850
You received this bug notification because you are a member of Ubuntu
Bugs, which is t
I checked in the xorg-server git tree, and
hw/xfree86/common/xf86Xinput.c:xf86PostMotionEvent() used to call
*local->conversion_proc() in e.g. xorg-server-1.2.99.905, but doesn't in
the current tip.
--
Uncalibrated and can't calibrate with 0.8.7-2 on Samsung Q1 Ultra
https://bugs.launchpad.net/bu
According to this thread:
http://lists.freedesktop.org/pipermail/xorg/2007-February/thread.html#22126
it seems that only clipping is done with newer xserver; the driver has
the burden of remapping coordinates, which was not the case in the past.
The thread seems to suggest some people would be inte
For some reason, the xorg input driver passes raw absolute vars to
xf86PostMotionEvent(); I can't tell whether this is correct (and xorg is
supposed to adjust basing on the values passed to
xf86InitValuatorAxisStruct()) or whether the values should be adjusted
by the driver.
I started looking at t
I reverted your change; after reverting, the behavior was similar but
slightly different.
My current feeling is that the driver doesn't configure Xinput properly
for input values higher than 1024; I guess this started being a problem
when moving from InitValuatorAxisStruct() to
xf86InitValuatorAxi
Loic,
I was the original author of this patch -- How do I get the upstream so
I can see if the patch still applies?
Michael
--
Uncalibrated and can't calibrate with 0.8.7-2 on Samsung Q1 Ultra
https://bugs.launchpad.net/bugs/163850
You received this bug notification because you are a member of
18 matches
Mail list logo
