Re: [PATCH v2] protocol: Extend wl_touch with touchpoint shape event

Hi, Some questions below.. On Wed, Apr 6, 2016 at 11:52 PM, Peter Hutterer wrote: > On Wed, Apr 06, 2016 at 10:17:35AM -0700, Dennis Kempin wrote: > > On Tue, Apr 5, 2016 at 5:26 PM, Peter Hutterer > wrote: > > > On Tue, Apr 05, 2016 at 01:09:31PM -0700, Dennis Kempin wrote: > > >> [...] > > >>

Re: [RFC libinput] Add dial input device support

ch of further buttons.. so buttonset sounds like a good generalization for those too. regards Andreas Pokorny ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel

Re: [libinput] How I get extra touch events using libinput?

Hi, On Wed, Jan 6, 2016 at 8:30 AM, Peter Hutterer wrote: > CC-ing Andreas this time, forgot about it in my original reply, sorry about > that. > > On Wed, Jan 06, 2016 at 03:35:49PM +0900, 강정현 wrote: > > In Andreas Pokorny patch, only support part of standard linux MT >

Re: [PATCH libinput v9 0/2] add orientation, size and pressure of touch

Hi, On Tue, Nov 24, 2015 at 1:41 AM, Peter Hutterer wrote: > On Mon, Nov 23, 2015 at 07:58:28PM +0100, Andreas Pokorny wrote: > [...] > > measured values on the e4.5 jumped a lot further. I need a more accurate > > method for that. In the second round I will probably

Re: [PATCH libinput v9 0/2] add orientation, size and pressure of touch

Hi, one more thing.. On Mon, Nov 23, 2015 at 7:58 PM, Andreas Pokorny < andreas.poko...@canonical.com> wrote: > [...] > > On Mon, Nov 23, 2015 at 5:19 AM, Peter Hutterer > wrote: > >> On Fri, Nov 13, 2015 at 08:46:42AM +0100, Andreas Pokorny wrote: >> > Hi

Re: [PATCH libinput v9 0/2] add orientation, size and pressure of touch

method for that. In the second round I will probably try to verify the result with a finger-paint application. On Mon, Nov 23, 2015 at 5:19 AM, Peter Hutterer wrote: > On Fri, Nov 13, 2015 at 08:46:42AM +0100, Andreas Pokorny wrote: > > Hi, > > This version contains several

[PATCH libinput v9 1/2] libinput: add orientation and size of touch point and pressure to the API

. Signed-off-by: Andreas Pokorny --- doc/Makefile.am| 2 + doc/page-hierarchy.dox | 1 + doc/svg/touchscreen-touch-event-properties.svg | 347 + doc/touch-event-properties.dox | 66 + src/evdev.c

[PATCH libinput v9 0/2] add orientation, size and pressure of touch

Hi, This version contains several rewordings and documentation additions from Peter that I missed in the last update, within the first patch of the series, while the second patch contains no changes compared to v8. regards Andreas Andreas Pokorny (2): libinput: add orientation and size of

[PATCH libinput v9 2/2] extend tools to print and display touch event properties

event-gui draws the touch contact as two concentric ellipses that indicate contact pressure through oppacity. Signed-off-by: Andreas Pokorny --- tools/event-debug.c | 29 - tools/event-gui.c | 38 +- 2 files changed, 61

[PATCH libinput 2/2] extend tools to print and display touch event properties

event-gui draws the touch contact as two concentric ellipses that indicate contact pressure through oppacity. Signed-off-by: Andreas Pokorny --- tools/event-debug.c | 29 - tools/event-gui.c | 38 +- 2 files changed, 61

[PATCH libinput 1/2] libinput: add orientation and size of touch point and pressure to the API

. Signed-off-by: Andreas Pokorny --- doc/Makefile.am| 2 + doc/page-hierarchy.dox | 1 + doc/svg/touchscreen-touch-event-properties.svg | 347 + doc/touch-event-properties.dox | 42 +++ src/evdev.c

[PATCH libinput v8 0/2] add orientation, size and and pressure of touch

Hi, This version of the series deals released or not yet pressed touch contacts in event-gui. Additionally the code that was supposed to scale diameters on devices when horizontal and vertical axes have a different resolution was revised. regards Andreas Andreas Pokorny (2): libinput: add

Re: Weston 1.8.0: touch input using evdev not working

Hi, Could you send the contents of the files /sys/devices/virtual/input/input0/event0/{capabilities/*,properties}? Those show the information interpreted by the builtin rules in udevadm. But Benjamin might be right, upgrading to systemd-221 might fix your problem already. regards Andreas ​ ___

Re: [PATCH] libinput device capability modification regarding combo input devices

s to also indicate whether the device, i.e. it might be interesting to know whether the device is a full keyboard or just offers a few buttons.. So yes I aggree with that. Right now we do the evdev based device detection in parallel to what udevd and libinput do.. regards Andreas Pokorny _

[PATCH v2 libinput] Fix premature flushing of evdev event on mx4 touchscreen

The mx4 touchscreen driver emits BTN_TOUCH and BTN_TOOL_FINGER key events on a new contact. Prior to this patch only the BTN_TOUCH event was filtered out. Now the whole range of BTN_ events for tool types and certain builtin multi finger gestures are marked as non-key type. Signed-off-by: Andreas

Re: [PATCH libinput] Fix premature flushing of evdev event on mx4 touchscreen

Hi, On Mon, Sep 7, 2015 at 3:51 AM, Peter Hutterer wrote: > [...] > > + { {0}, EV_KEY, BTN_TOUCH, 0}, > > + { {0}, EV_KEY, BTN_TOOL_FINGER, 0}, > > + { {0}, EV_SYN, SYN_REPORT, 0} > > + }; > > I'm wondering - wouldn't it be worth to add this device as a s

[PATCH libinput] Fix premature flushing of evdev event on mx4 touchscreen

v5 of the touch property extenion patches. Signed-off-by: Andreas Pokorny --- src/evdev.c | 10 ++--- test/touch.c | 125 +++ 2 files changed, 130 insertions(+), 5 deletions(-) diff --git a/src/evdev.c b/src/evdev.c index 04df275

[PATCH libinput 2/2] extend tools to print and display touch event properties

event-gui draws the touch contact as two concentric ellipses that indicate contact pressure through oppacity. Signed-off-by: Andreas Pokorny --- tools/event-debug.c | 30 -- tools/event-gui.c | 30 -- 2 files changed, 56 insertions(+), 4

[PATCH libinput 1/2] libinput: add orientation and size of touch point and pressure to the API

. Signed-off-by: Andreas Pokorny --- doc/Makefile.am| 2 + doc/page-hierarchy.dox | 1 + doc/svg/touchscreen-touch-event-properties.svg | 347 + doc/touch-event-properties.dox | 42 +++ src/evdev.c

[PATCH libinput v7 0/2] add orientation, size and pressure of touch

n data for those properties we might want to change that. Andreas Pokorny (2): libinput: add orientation and size of touch point and pressure to the API extend tools to print and display touch event properties doc/Makefile.am| 2 + doc/page-hie

[PATCH libinput] fix gcc warning on unused return value

Signed-off-by: Andreas Pokorny --- test/litest.c | 8 +--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/test/litest.c b/test/litest.c index 29e764b..38e313e 100644 --- a/test/litest.c +++ b/test/litest.c @@ -932,13 +932,15 @@ merge_events(const int *orig, const int

Re: [PATCH libinput] Note that libinput_unref() really destroys everything

Hi, To some degree this does not sound like a bug. At least for resources that are not presented to the user as being ref counted. But I would have expected that libinput_path_add_device would increase the ref count of the libinput_context and similar for seats. So as long as the device is not unre

Re: [PATCH libinput] libinput: add orientation and size of touch point and pressure to the API

Hi, Just a heads up on the problem I experience that I thought would be related to what you described. On Wed, Sep 2, 2015 at 12:50 PM, Andreas Pokorny < andreas.poko...@canonical.com> wrote: > [...] > On Tue, Sep 1, 2015 at 8:30 AM, Peter Hutterer > wrote: > >> [...] &g

Re: [PATCH libinput] libinput: add orientation and size of touch point and pressure to the API

Hi, On Tue, Sep 1, 2015 at 8:30 AM, Peter Hutterer wrote: > [...] > but first up, I have to ask: how did you test this, do you have an > implementation higher up in the stack that makes use of this? The API looks > generally ok now, but once I started testing it it didn't turn out too > well. >

[PATCH libinput] quirk for mtk kernels

Signed-off-by: Andreas Pokorny --- src/evdev.c | 10 ++ 1 file changed, 10 insertions(+) diff --git a/src/evdev.c b/src/evdev.c index 29303f8..1373e6f 100644 --- a/src/evdev.c +++ b/src/evdev.c @@ -1886,6 +1886,16 @@ evdev_check_min_max(struct evdev_device *device, unsigned int code

[PATCH libinput] RFC on quirk handling in libinput

broken drivers (next to fixing the kernel vendor)? If adding an entry to the hwdb would help - how do I get to the strings that identify the device? regards, Andreas Andreas Pokorny (1): quirk for mtk kernels src/evdev.c | 10 ++ 1 file changed, 10 insertions(+) -- 2.1.4

[PATCH libinput] libinput: add orientation and size of touch point and pressure to the API

. Signed-off-by: Andreas Pokorny --- doc/Makefile.am| 2 + doc/page-hierarchy.dox | 1 + doc/svg/touchscreen-touch-event-properties.svg | 347 + doc/touch-event-properties.dox | 42 +++ src/evdev.c

[PATCH libinput] libinput: add orientation and size of touch point and pressure to the API

. Signed-off-by: Andreas Pokorny --- doc/Makefile.am| 2 + doc/page-hierarchy.dox | 1 + doc/svg/touchscreen-touch-event-properties.svg | 347 + doc/touch-event-properties.dox | 42 +++ src/evdev.c

Re: [PATCH libinput 2/2] enable -Wall -Werror for CFLAGS

:38 +0200 > > Andreas Pokorny wrote: > > > > > Just a small change in test is necessary to enable -Wall -Werror. > > > > > > Signed-off-by: Andreas Pokorny > > > --- > > > configure.ac | 4 ++-- > > > test/litest.c | 8 ++-- >

[PATCH libinput] libinput: litest shall only emit auto assign events when replaced

With this change auto assign events will be skipped if no replacement value is provided. This behavior is practical when emitting mt events, as those only contain the axis values that changed. Signed-off-by: Andreas Pokorny --- test/litest.c | 8 1 file changed, 4 insertions(+), 4

[PATCH libinput 2/2] enable -Wall -Werror for CFLAGS

Just a small change in test is necessary to enable -Wall -Werror. Signed-off-by: Andreas Pokorny --- configure.ac | 4 ++-- test/litest.c | 8 ++-- 2 files changed, 8 insertions(+), 4 deletions(-) diff --git a/configure.ac b/configure.ac index 885cb39..b7597f0 100644 --- a/configure.ac

[PATCH libinput 1/2] test: fix gcc warning about missing prototypes

Signed-off-by: Andreas Pokorny --- test/litest.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/test/litest.c b/test/litest.c index 8fc7bca..29e764b 100644 --- a/test/litest.c +++ b/test/litest.c @@ -44,6 +44,8 @@ #include #include #include +#include +#include #include

[PATCH libinput] doc: inverse event type restriction of x and y accessors

Signed-off-by: Andreas Pokorny --- src/libinput.h | 12 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/src/libinput.h b/src/libinput.h index f2b77b3..88b3c05 100644 --- a/src/libinput.h +++ b/src/libinput.h @@ -894,7 +894,8 @@ libinput_event_touch_get_seat_slot(struct

[PATCH libinput] doc: ellipse instead of ellipsis

Signed-off-by: Andreas Pokorny --- doc/touchpads.dox | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/touchpads.dox b/doc/touchpads.dox index fa509bc..401f16a 100644 --- a/doc/touchpads.dox +++ b/doc/touchpads.dox @@ -71,7 +71,7 @@ touches, others support 5 touches

Re: [PATCH libinput v5 5/5] libinput: add orientation and size of touch point and pressure to the API

Hi, On Wed, Jul 8, 2015 at 1:03 AM, Peter Hutterer wrote: > > +double > > +evdev_device_transform_touch_point_to_mm(struct evdev_device *device, > > + int32_t axis_value, > > + double axis_angle) > > oh dear. I just spent

[PATCH libinput v5 5/5] libinput: add orientation and size of touch point and pressure to the API

supported by multi-touch drivers, so zero as a default value is used if the information is missing. This change also correctly bumps the ABI version to 0.20.0 and adds the new libinput symbols there. Signed-off-by: Andreas Pokorny --- src/evdev.c| 192

[PATCH libinput 5/5] libinput: add orientation and size of touch point and pressure to the API

supported by multi-touch drivers, so zero as a default value is used if the information is missing. Signed-off-by: Andreas Pokorny --- src/evdev.c| 192 +--- src/evdev.h| 24 ++ src/libinput-private.h | 10 ++- src/libinput.c

[PATCH libinput 3/5] litest: add nexus4 style touch screen without orientation

This device provides a circular touch point size and and hence lacks orientation. It will be used to test default value handling. Signed-off-by: Andreas Pokorny --- test/Makefile.am | 1 + test/litest-nexus4-touch-screen.c | 99 +++ test

[PATCH libinput 2/5] litest: add a generic multitouch screen

Adds a device with various touch related axes and respective device features to litest. Signed-off-by: Andreas Pokorny --- test/Makefile.am | 1 + test/litest-touch-screen.c | 105 + test/litest.c | 2 + test/litest.h

[PATCH libinput v4 0/5] add touch pointer properties

t set' - behavior. So I could remove some now unnecessary parts like the tracking of available slot properties. Andreas Pokorny (5): litest: add axis_replacement from tablet branch litest: add a generic multitouch screen litest: add nexus4 style touch screen without orientation litest: floa

Re: [PATCH libinput v3 5/5] libinput: add orientation and size of touch point and pressure to the API

Hi, On Thu, Jun 25, 2015 at 8:03 AM, Peter Hutterer wrote: > [...] > > - break; > > - case ABS_MT_TRACKING_ID: > > + } else if(e->code == ABS_MT_TRACKING_ID) { > > if (device->pending_event != EVDEV_NONE && > > device->pending_event != EVDEV_AB

[PATCH libinput v3 1/5] litest: add axis_replacement from tablet branch

This change adds strict axis_replacemnt and litest_touch_move_extended and litest_touch_down_extended to simulate changes to other axes during touch down and move events. Signed-off-by: Andreas Pokorny --- test/litest.c | 95 +++ test

[PATCH libinput v3 0/5] add touch point properties to libinput_event_touch

Hi, Here is the third version. I added major / minor scaling for cases when x_absinfo.resolution does not match y_absinfo.resolution, and fixed the compilation errors that sneaked in last time. regards Andreas Andreas Pokorny (5): litest: add axis_replacement from tablet branch litest: add

[PATCH libinput v3 5/5] libinput: add orientation and size of touch point and pressure to the API

supported by multi touch drivers, hence default values are provided if the information is missing. Signed-off-by: Andreas Pokorny --- src/evdev.c| 243 +++-- src/evdev.h| 37 src/libinput-private.h | 12 ++- src/libinput.c

[PATCH libinput v3 2/5] litest: add a generic multitouch screen

Adds a device with various touch related axes and respective device features to litest. Signed-off-by: Andreas Pokorny --- test/Makefile.am | 1 + test/litest-touch-screen.c | 135 + test/litest.c | 2 + test/litest.h

[PATCH libinput v3 3/5] litest: add nexus4 style touch screen without orientation

This device provides a circular touch point size and and hence lacks orientation. It will be used to test default value handling. Signed-off-by: Andreas Pokorny --- test/Makefile.am | 1 + test/litest-nexus4-touch-screen.c | 116 ++ test

[PATCH libinput v3 4/5] litest: floating point comparison macros

Adds the macros ck_assert_double_{eq,ne,lt,gt,le,ge} to compare double values using a fixed tolerance value. The tolerance value is picked based on the range of values to be expected by the libinput API. Signed-off-by: Andreas Pokorny --- test/litest-selftest.c | 66

Re: [PATCH libinput v2 5/5] libinput: add orientation and size of touch point and pressure to the API

Hi, On Mon, Jun 22, 2015 at 3:37 AM, Peter Hutterer wrote: > On Fri, Jun 19, 2015 at 03:24:38PM +0200, Andreas Pokorny wrote: > > + * */ > > + if (orientation_info) { > > + if (orientation_info->maximum == 1 && > > +

[PATCH libinput v2 1/5] add axis_replacement from tablet branch

The optional axis_replacement provides additional replacement values for touch down and touch move litest functions. Signed-off-by: Andreas Pokorny --- test/litest.c | 59 --- test/litest.h | 16 2 files changed, 64

[PATCH libinput v2 3/5] litest: add mako style touch screen without orientation

This device provides a circular touch point size and and hence lacks orientation. It will be used to test default value handling. --- test/Makefile.am | 1 + test/litest-nexus4-touch-screen.c | 98 +++ test/litest.c | 2 +

[PATCH libinput v2 2/5] litest: add a generic multitouch screen

Adds a device with various touch related axes and respective device features to litest. And additional routines to simulate pressure orientation and touch major/minor changes. Signed-off-by: Andreas Pokorny --- test/Makefile.am | 1 + test/litest-touch-screen.c | 104

[PATCH libinput v2 0/5] add touch point properties to libinput_event_touch

/InputReader.cpp Andreas Pokorny (5): add axis_replacement from tablet branch litest: add a generic multitouch screen litest: add mako style touch screen without orientation litest: floating point comparison macros libinput: add orientation and size of touch point and pressure to the

[PATCH libinput v2 4/5] litest: floating point comparison macros

Adds the macros ck_assert_double_{eq,ne,lt,gt,le,ge} to compare double values using a fixed tolerance value. The tolerance value is picked based on the range of values to be expected by the libinput API. Signed-off-by: Andreas Pokorny --- test/litest-selftest.c | 66

[PATCH libinput v2 5/5] libinput: add orientation and size of touch point and pressure to the API

supported by multi touch drivers, hence default values are provided if the information is missing. Signed-off-by: Andreas Pokorny --- src/evdev.c| 158 ++-- src/evdev.h| 37 ++ src/libinput-private.h | 12 ++- src/libinput.c

Re: [PATCH 1/7] litest: add a generic multitouch screen

Hi, On Thu, Jun 11, 2015 at 8:04 AM, Peter Hutterer wrote: > [...] > > +static struct input_absinfo absinfo[] = { > > + { ABS_X, 0, 1500, 0, 0, 0 }, > > + { ABS_Y, 0, 2500, 0, 0, 0 }, > > out of interest: is his from a real touchscreen? no resolution? > Yes and not an exception. I haven

[PATCH 4/7] litest: float comparision

--- test/litest.h | 7 +++ 1 file changed, 7 insertions(+) diff --git a/test/litest.h b/test/litest.h index 3a08b6a..0d39dd3 100644 --- a/test/litest.h +++ b/test/litest.h @@ -428,4 +428,11 @@ void litest_semi_mt_touch_up(struct litest_device *d, #define ck_assert_notnull(ptr) ck_assert_ptr_

[PATCH 7/7] evdev: track which touch point properties are available

This change adds flags to track which property of a touch point is set. With that reasonable default values can be provided when an information is not available. --- src/evdev.c| 29 - src/evdev.h| 10 ++ src/libinput.c | 4 test/touch.c | 42 +++

[PATCH 6/7] litest: add mako style touch screen without orientation

This device provides a circular touch point size and and hence lacks orientation. It will be used to test default value handling. --- test/Makefile.am| 1 + test/litest-mako-touch-screen.c | 93 + test/litest.c | 2 + test

[PATCH 2/7] libinput: add orientation and size of touch point and pressure to the API

This change adds four new properties to touch events. These properties are directly forwarded from the evdev interface. --- src/evdev.c| 81 -- src/evdev.h| 4 +++ src/libinput-private.h | 12 ++-- src/libinput.c

[PATCH 1/7] litest: add a generic multitouch screen

Adds a device with various touch related axes and respective device features to litest. And additional routines to simulate pressure orientation and touch major/minor changes. --- test/Makefile.am | 1 + test/litest-touch-screen.c | 100 + te

[PATCH 3/7] evdev: move scale_axis to evdev.h header

To be used inside pressure and orientation access functions of libinput.c --- src/evdev.c | 11 ++- src/evdev.h | 7 +++ 2 files changed, 9 insertions(+), 9 deletions(-) diff --git a/src/evdev.c b/src/evdev.c index af507d6..6f68554 100644 --- a/src/evdev.c +++ b/src/evdev.c @@ -224,1

[PATCH 5/7] evdev: Normalize orientation and pressure values

Pressure values will be mapped into the range [0;1] while orientation will be mapped to [-1;1] (or ]-1;1] or [0;1] depending on the how the underlying device configures the axis value ranges). --- src/evdev.c| 6 ++ src/evdev.h| 1 + src/libinput.c | 14 -- src/libinput.h

[PATCH 0/7] libinput: add touch point properties to libinput_event_touch

] respectively. I am not entirely shure whether touch major/minor need transformation or scaling in some sense based on the calibration matrix? In the current version those two are just provided the way they were read from the device. regards, Andreas Andreas Pokorny (7): litest: add a generic

Re: [PATCH weston 0/6] ivi-shell proposal

Hi, Overall I like that genivi is now a lot more accessible/visible from the outside. I understand the necessity of dealing with layers on a lower level to make use of the efficient blending of display controllers. But that logic should be only implemented within the compositor. Clients should not

Re: surface buffer cardinality and outputs

sonably work for non occluded text. But the idea is not that far away from video frames. [1]: http://www.valvesoftware.com/publications/2007/SIGGRAPH2007_AlphaTestedMagnification.pdf Then wayland would still be raster protocol, and would not need resize (or transformation caused

Re: surface buffer cardinality and outputs

Hi, 2013/3/23 Jerome Glisse : >> How would you transmit transformations that are not representable >> by a matrix? Nothing says we are limited to matrices, that is also >> just a special case. Or would you introduce that limitation in the >> protocol? > > What kind of transformation are not repres

Re: State of Wayland, 2012-04-08

extensions to get wayland running with hardware acceleration. regards Andreas Pokorny ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel

Re: SGX driver support (yay!)

Hi, 2011/8/3 Christopher Friedt : > SGX just release binary drivers for OMAP3 with support for the > EGL_KHR_Image_Pixmap extension [1]. I assume that OMAP4 drivers are on > their way. > What kind of native pixmap types are supported now? Can this be used for sharing textures/buffer across proce

Re: Wayland in N900

Hi Esa, 2010/12/17 : > On 12/17, Esa Törmikoski wrote: > [...] >> Doomed right in the start :( Need to find some other topic for >> thesis work then if this is impossible.. > > Ask Nokia to implement EGLImage sharing across processes? > > I assume the driver is closed? The kernel part is open an