mutouch 1.2.0 has issues with the current X server as it does not handle
inverted axes (or handles them as inverted even when they aren't). This is
fixed now, and I have anecdotal evidence that it even works.
Peter Hutterer (6):
Check for XINPUT ABI 3.
Remove trailing whitespaces.
2008/10/1 Peter Hutterer [EMAIL PROTECTED]:
Ok, I took your patches, split them up and fiddled with them a bit.
Great, Thanks! I'm hoping to get an hour or so with the touch screen
on friday. Then I'll test, to make sure things are working. Also, I
hope to borrow a different touch screen from my
On Tue, 2008-09-30 at 17:05 +0200, Søren Hauberg wrote:
I don't quite know where to publish this, so I figured this list
would be a start. Attached is a program for calibrating a touch
screen. It computes the following parameters:
'flip_x'
a boolean parameter that determines
On Thu, 25.09.2008, 22:53, Paulo Cesar Pereira de Andrade wrote:
I am not an expert on SMI501, just worked on it, not full time,
for a bit more then one month now... I am working on it for an
alternate driver for http://www.gdium.com/
The kernel module I have, at least would probably
On Tue, 2008-09-30 at 21:30 +0200, Bernie Innocenti wrote:
Michel Dänzer wrote:
On Sun, 2008-09-28 at 18:46 +0200, Bernie Innocenti wrote:
My performance tests with X 1.3 and 1.4 had shown that turning on EXA
makes many operations slower. It's hard to tell why, but it might have to
2008/10/1 Clemens Kirchgatterer [EMAIL PROTECTED]:
Everybody: does anybody have any thought on where I should host my
calibration code?
isn't there something in tslib already?
I've found two calibration programs online. One came without a
license, making it non-free software, and the other
On Wed, 2008-10-01 at 13:56 +0200, Søren Hauberg wrote:
I've found two calibration programs online. One came without a
license, making it non-free software, and the other one had a
non-so-nice gui, where you had to move your stylus all the way up the
corners of the screen (this one I couldn't
Keith Packard wrote:
On Tue, 2008-09-30 at 17:28 +0100, Barry Scott wrote:
For example mozilla (mozembed). The -nocursor patch avoids the need to
modify
any app code at all to remove the unwanted cursors.
Have you tried the XFixes HideCursor request yet? That disables the
cursor
Hi all,
I'm not sure if it's the right list, in case it isn't feel free to point me to
correct one :)
I'm running a Slackware 12.1 on a Intel P4 3Ghz, 2Gb ram and a Intel 82865G
Integrated graphics card (integrated on a Asus P4P800-MX motherboard). Here
you are what returns lspci:
00:02.0 VGA
Christian Pössinger wrote:
Now I used the latest siliconmotion driver from the XOrg GIT and removed
the PCI function calls to access the device via Local Plus Bus of the
TQM5200 board.
I initialize the pSmi-MapBase and pSmi-FbBase fields with a mmap() call
to /dev/mem and the proper
At 10:58 AM 10/1/2008, Adam Jackson wrote:
On Tue, 2008-09-30 at 07:49 -0700, Paul White wrote:
I have a new Dell Inspiron computer with built-in Intel 82G33/G31 video.
The Intel driver apparently doesn't recognize this specific chipset and
defaults to using vesa, which doesn't support my
mutouch 1.2.0 has issues with the current X server as it does not handle
inverted axes (or handles them as inverted even when they aren't). This is
fixed now, and I have anecdotal evidence that it even works.
Peter Hutterer (6):
Check for XINPUT ABI 3.
Remove trailing whitespaces.
Hi,
Here attached are the patches against the server to separate its input
generation code in another thread.
The main difference in this second try is the hook to put hotplug
devices to work and the pthread consistency in all code.
configure.ac |8 +
dix/main.c
--
Tiago Vignatti
C3SL - Centro de Computação Científica e Software Livre
www.c3sl.ufpr.br
From 856d2e3906a9a3f1ea55249f43e1ea1310f22d2d Mon Sep 17 00:00:00 2001
From: Tiago Vignatti [EMAIL PROTECTED]
Date: Wed, 1 Oct 2008 21:13:26 -0300
Subject: [PATCH] The input-thread core file
--
Tiago Vignatti
C3SL - Centro de Computação Científica e Software Livre
www.c3sl.ufpr.br
From 6e0692f6a5757b6d838d857bdb68596a5208c6e2 Mon Sep 17 00:00:00 2001
From: Tiago Vignatti [EMAIL PROTECTED]
Date: Wed, 1 Oct 2008 21:15:15 -0300
Subject: [PATCH] X event queue mutex.
A mutex is needed
On Wed, 2008-10-01 at 21:39 -0300, Tiago Vignatti wrote:
A mutex is needed because the X event queue is a critical region. Though
the X event queue is re-entrant, we cannot guarantee the simultaneous
processing by both main and input threads.
The input queue is written so that each user
16 matches
Mail list logo
