Re: Screen corrupted every 215th pixel

On Monday 03 January 2011 22:13:23 Oldřich Jedlička wrote: Hi all, I have a really strange problem. I have every 215th column (in pixels) corrupted - when I draw two vertical lines with 214 pixels in between in Gimp and move the window on the desktop to the specific position, I don't see

Re: Screen corrupted every 215th pixel

On Tuesday 04 January 2011 21:25:35 Oldřich Jedlička wrote: On Monday 03 January 2011 22:13:23 Oldřich Jedlička wrote: Hi all, I have a really strange problem. I have every 215th column (in pixels) corrupted - when I draw two vertical lines with 214 pixels in between in Gimp and move

Screen corrupted every 215th pixel

Hi all, I have a really strange problem. I have every 215th column (in pixels) corrupted - when I draw two vertical lines with 214 pixels in between in Gimp and move the window on the desktop to the specific position, I don't see any line (the column is filled with the background color). I see

Re: Make EVDEV a driver which is acutally useful

On Monday 30 August 2010 10:14:10 ManDay wrote: I'm deperately trying to solve a real world problem that is. Many applications do not have such sophisticated methods to use input devices (in my case: GIMP). If X/evdev gave me the option to arbitrarily remapw anything to anything (or just

Re: Make EVDEV a driver which is acutally useful

can handle. Oldřich. Unless by mouse you mean motion. On 08/30/2010 09:10 PM, Oldřich Jedlička wrote: On Monday 30 August 2010 10:14:10 ManDay wrote: I'm deperately trying to solve a real world problem that is. Many applications do not have such sophisticated methods to use input

Re: Problem with mouse input freeze

Hi Peter, On Tuesday 12 of January 2010 at 03:12:15, Peter Hutterer wrote: On Fri, Jan 08, 2010 at 09:08:52PM +0100, Oldřich Jedlička wrote: Dne Pá 8. ledna 2010 07:04:34 Peter Hutterer napsal(a): On Thu, Jan 07, 2010 at 10:13:24PM +0100, Oldřich Jedlička wrote: can I assume you only

Re: Typo in recent xf86-video-ati commit (ATOM: Upstream parser updates)

Hi Alex, On Wednesday 20 of January 2010 at 15:20:14, Alex Deucher wrote: 2010/1/20 Oldřich Jedlička oldium@seznam.cz: Hi Alex, I've just found that there are new commits in xf86-video-ati and one is suspicious to me - ATOM: Upstream parser updates. It contains lines

Typo in recent xf86-video-ati commit (ATOM: Upstream parser updates)

Hi Alex, I've just found that there are new commits in xf86-video-ati and one is suspicious to me - ATOM: Upstream parser updates. It contains lines: pParserTempData-DestData32=GetDestination[pParserTempData-ParametersType.Destination](pParserTempData);

[PATCH v3] Allow driver to call DeleteInputDeviceRequest during UnInit

. The devices can reorder any time during freeing. No device will be double-freed - if the removing failed for any reason; some implementations of DeleteInputDeviceRequest don't free the devices already. Signed-off-by: Oldřich Jedlička oldium@seznam.cz --- dix/devices.c | 44

Re: [PATCH v2] Allow driver to call DeleteInputDeviceRequest during UnInit

Hi Peter, Simon, On Friday 15 of January 2010 at 10:40:02, Simon Thum wrote: Oldřich Jedlička wrote: When the input driver (like xf86-input-wacom) removes it's devices during a call to UnInit, the CloseDownDevices() cannot handle it. The next variable can become a pointer to freed memory

[PATCH v2] Allow driver to call DeleteInputDeviceRequest during UnInit

. The devices can reorder any time during freeing. No device will be double-freed - if the removing failed for any reason; some implementations of DeleteInputDeviceRequest don't free the devices already. Signed-off-by: Oldřich Jedlička oldium@seznam.cz --- dix/devices.c | 42

[PATCH] Allow driver to call DeleteInputDeviceRequest during UnInit

that is currently being freed. Signed-off-by: Oldřich Jedlička oldium@seznam.cz --- dix/devices.c | 18 +- 1 files changed, 13 insertions(+), 5 deletions(-) diff --git a/dix/devices.c b/dix/devices.c index 245a95b..e4bd908 100644 --- a/dix/devices.c +++ b/dix/devices.c @@ -884,7

Re: Problem with mouse input freeze

Dne Pá 8. ledna 2010 07:04:34 Peter Hutterer napsal(a): On Thu, Jan 07, 2010 at 10:13:24PM +0100, Oldřich Jedlička wrote: can I assume you only have one master device and you aren't playing around with MPX? what's the output of xinput --list --short? is the pad a floating slave

Re: Problem with mouse input freeze

Hi Peter, Dne čtvrtek 07 Leden 2010 07:09:21 Peter Hutterer napsal(a): On Wed, Jan 06, 2010 at 09:00:55PM +0100, Oldřich Jedlička wrote: Hi list and Peter, this is a continuation from linuxwacom-devel mailing list - the full thread (few messages actually) can be found here http

Problem with mouse input freeze

Hi list and Peter, this is a continuation from linuxwacom-devel mailing list - the full thread (few messages actually) can be found here http://sourceforge.net/mailarchive/message.php?msg_name=201001022352.48459.oldium.pro%40seznam.cz So let's start from the beginning. I had a problem: when

Re: Problem with mouse input freeze

Hi Peter, Dne čtvrtek 07 Leden 2010 07:09:21 Peter Hutterer napsal(a): On Wed, Jan 06, 2010 at 09:00:55PM +0100, Oldřich Jedlička wrote: Hi list and Peter, this is a continuation from linuxwacom-devel mailing list - the full thread (few messages actually) can be found here http