Hi,
I want to test the touch interface of the device.
Can anybody could help me out how to generate the touch events using
XInput 2
Thanks,
Mugu
___
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info:
On 02/ 4/11 01:43 AM, Erkki Seppälä wrote:
From: Ander Conselvan de Oliveira ander.conselvan-de-olive...@nokia.com
property_return was free'd before and in the case the conditional is
true, the call to XcmsGetProperty failed which means that
property_return wasn't set so there is no need to
On 02/ 4/11 01:43 AM, Erkki Seppälä wrote:
Properly handle the return value of XGetWindowProperty by considering
if after the loop as well.
Using freed pointer prop_ret
There were numerous things wrong in how this function interacted with
XGetWindowProperty.
None of the local variables
Hello,
Here is the pull request for the two remaining fixes based on static
analysis results. Thanks for reviewing!
8
The following changes since commit 50f4107811249806718a100f9d34f996c58e5e25:
Alan Coopersmith (1):
Xrm.c: ReadInFile: refactor fstat error handling
are
On Fre, 2011-01-21 at 10:15 +0100, Michel Dänzer wrote:
From: Michel Dänzer daen...@vmware.com
RandR doesn't seem to deal with pseudocolour at all, so without this the
pseudocolour palette never gets loaded to the hardware.
v2: Move logic into xf86_crtc_supports_gamma().
Anyone? Should
On Thu, Jan 27, 2011 at 10:32:06 +0100, Julien Cristau wrote:
This series fixes regressions introduced in my previous glx patchset.
The first two fix wrong checks, and patch 3 relaxes a few checks to
work around incorrect lengths sent by mesa (I sent patches to fix those
to the mesa list).
Hi,
On Tue, Feb 08, 2011 at 02:04:11PM -0800, Rick Stockton wrote:
I was wondering about an idea- and rather than stumble around (for
weeks) on my own, I want to ask you WAY SMARTER guys about it:
As you already know, I'm planning to bring some decent support for
additional mouse buttons
On Wed, Feb 09, 2011 at 10:00:07AM +0200, mugunthan wrote:
I want to test the touch interface of the device.
Can anybody could help me out how to generate the touch events using
XInput 2
http://cgit.freedesktop.org/~whot/evtest
signature.asc
Description: Digital signature
Hi,
Thanks a lot for your information.
I downloaded the event tester. But it says you can check the output from
the device .
But I want to generate some events which could be sent to the device.
For example
I need to generate the touch event and see how the device responds. The
touch event
Hi,
On Wed, Feb 09, 2011 at 02:49:26PM +0200, mugunthan wrote:
Thanks a lot for your information.
I downloaded the event tester. But it says you can check the output from
the device .
But I want to generate some events which could be sent to the device.
For example
I need to generate
Hi ,
I already have the hardware. So I would like to test on that .
So I was wondering how to do that.
Thanks,
Mugu
On Wed, 2011-02-09 at 13:30 +, ext Daniel Stone wrote:
evtest-create-device.xsl
___
xorg-devel@lists.x.org: X.Org development
On Wed, Feb 09, 2011 at 04:30:54PM +0200, mugunthan wrote:
I already have the hardware. So I would like to test on that .
So I was wondering how to do that.
I have no idea what you're actually asking. If you have hardware which
you want to test on, then use the hardware. The text file I
I got it ... thanks a lot for your inputs ... I have just one more
question
when I m running the evtest for a device .like this
==
Input driver version is 1.0.1
Input device ID: bus 0x11 vendor 0x2 product 0x7 version 0x1b1
Input device name: SynPS/2
On Wed, Feb 09, 2011 at 05:17:20PM +0200, mugunthan wrote:
I got it ... thanks a lot for your inputs ... I have just one more
question
when I m running the evtest for a device .like this
==
[...]
===
how
From: Pauli Nieminen ext-pauli.niemi...@nokia.com
Original patch has NULL pointer deference bug which I have fixed locally with
following patch.
---
hw/xfree86/dri2/dri2.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/hw/xfree86/dri2/dri2.c
- It turns out that part of the problem was actually on the driver side.
- The performance loss is not worth the small visual improvement.
- This should ensure low latency at low throughput.
- Performance loss seems less than 10% instead of the previous 33%.
Signed-off-by: Maarten Maathuis
On Wed, Feb 9, 2011 at 9:09 PM, Maarten Maathuis madman2...@gmail.com wrote:
- It turns out that part of the problem was actually on the driver side.
- The performance loss is not worth the small visual improvement.
- This should ensure low latency at low throughput.
- Performance loss seems
On Wed, 09 Feb 2011 10:48:24 +0100, Michel Dänzer mic...@daenzer.net wrote:
Anyone? Should the server abort in this case instead? It certainly can't
work properly as it is.
Sure looks like any driver that supports the gamma function would
completely fall over in pseudo color mode. Have you
On Tue, Feb 08, 2011 at 10:18:47AM -0600, Donnie Berkholz wrote:
On 15:04 Thu 03 Feb , Alan Coopersmith wrote:
Sure, but remember that GSoC projects are supposed to be equivalent to a
full-time job for 3 months, so it would have to be a bit more than just
fixing the documentation for a
Protocol includes all the feedback from before, client library should be
just about trivially correct. Would like to merge these before the weekend.
- ajax
___
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
v3: Review fixes:
- INT16 not CARD16 for coordinates
- BadDevice not BadMatch
Reviewed-by: Peter Hutterer peter.hutte...@who-t.net
Signed-off-by: Adam Jackson a...@redhat.com
---
COPYING|1 +
fixesproto.txt | 92 +--
xfixesproto.h
Ignore this one, it doesn't handle multiple devices.
On Feb 9, 2011, at 6:08 PM, Adam Jackson wrote:
Signed-off-by: Adam Jackson a...@redhat.com
---
configure.ac|2 +-
include/X11/extensions/Xfixes.h | 14 +++
src/Cursor.c| 48
On Mon, Feb 07, 2011 at 06:21:31PM +0100, carl...@gnome.org wrote:
From: Carlos Garnacho carl...@gnome.org
The previous XKB info was being returned instead of the current
one, producing inconsistent results between the latest events
and the modifiers/group returned by this call.
On Tue, Feb 08, 2011 at 12:00:43PM +0100, Simon Thum wrote:
diff --git a/src/synaptics.c b/src/synaptics.c
index 88bd024..b571d36 100644
--- a/src/synaptics.c
+++ b/src/synaptics.c
@@ -387,18 +387,19 @@ calculate_edge_widths(SynapticsPrivate *priv, int
*l, int *r, int *t, int *b)
*
Refacturing for simpler double-use in the next patch. No functional changes.
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
xkb/ddxLoad.c | 55 +++
1 files changed, 39 insertions(+), 16 deletions(-)
diff --git a/xkb/ddxLoad.c
We really need symbols, compat and types for a sensible keymap.
Try this in your xorg.conf.d snippets for all keyboards:
Option XkbLayout us
Option XkbVariant nodeadkeys
us(nodeadkeys) doesn't exist so xkbcomp provides everything but the symbols
map. We say we want everything but
On 02/ 9/11 12:28 AM, Erkki Seppala wrote:
The following changes since commit 50f4107811249806718a100f9d34f996c58e5e25:
Alan Coopersmith (1):
Xrm.c: ReadInFile: refactor fstat error handling
are available in the git repository at:
git://gitorious.org/erkkise/libx11-fixes.git
On Mit, 2011-02-09 at 12:43 -0800, Keith Packard wrote:
On Wed, 09 Feb 2011 10:48:24 +0100, Michel Dänzer mic...@daenzer.net wrote:
Anyone? Should the server abort in this case instead? It certainly can't
work properly as it is.
Sure looks like any driver that supports the gamma
On 02/09/2011 11:30 PM, ext Peter Hutterer wrote:
On Tue, Feb 08, 2011 at 11:10:07AM +0200, Ander Conselvan de Oliveira wrote:
The following patches fix points to uninitialised bytes errors
reported by valgrind when running Xorg. The four patches are quite
similar so maybe they should be
Easy enough to accept the syntax documented in the man page, so accept
the -I flag with or without a space between -I and the directory argument.
https://bugs.freedesktop.org/show_bug.cgi?id=34117
Signed-off-by: Alan Coopersmith alan.coopersm...@oracle.com
---
setxkbmap.c | 11 ++-
1
30 matches
Mail list logo
