Re: [RFC wayland 1/2] client: Introduce 'proxy wrapper' concept

On Mon, Jun 29, 2015 at 3:37 PM, Giulio Camuffo wrote: > 2015-06-29 14:30 GMT+03:00 Jonas Ådahl : > > Arnaud Vrac discovered an issue in the libwayland client API causing > > race conditions when doing round trips using the wl_display object using > > non-default proxy queues. > > > > The problem

[PATCH libinput 8/9] touchpad: default to a 69x50mm sized touchpad

The previous approach of using the axis ranges and approximating parameters based on the x/y axis range clutters up the code and is generally unreliable. If we look at Synaptics touchpads, the resolution ranges from 42 to 130 while the axes stay the same axis range. Other touchpads likely have a si

[PATCH libinput 6/9] udev: add ALPS firmware detection and size properties

Signed-off-by: Peter Hutterer --- udev/90-libinput-model-quirks.hwdb | 4 udev/libinput-model-quirks.c | 20 2 files changed, 24 insertions(+) diff --git a/udev/90-libinput-model-quirks.hwdb b/udev/90-libinput-model-quirks.hwdb index 3bfffbb..69e28ae 100644 ---

[PATCH libinput 4/9] evdev: use LIBINPUT_ATTR_SIZE_HINT for resolutions

Touchpads, notably Elantech, ALPS and bcm5974 don't provide x/y resolution until recent generations. Add a new property, LIBINPUT_ATTR_SIZE_HINT, that provides size information to libinput. Note that this property *does not* override true resolution values, it is only used when the resolution is mi

[PATCH libinput 5/9] udev: add Elantech touchpad firmware detection

Only firmware v4 (and probably whatever comes in the future) have resolution set, for the first couple of touchpads we need size hints. Add a callout that looks at the properties on the touchpad and decides the firmware version. The udev/hwdb is two-stage: the callout sets LIBINPUT_MODEL_FIRMWARE_

[PATCH libinput 7/9] udev: add size hint for apple touchpads

Signed-off-by: Peter Hutterer --- udev/90-libinput-model-quirks.hwdb | 1 + 1 file changed, 1 insertion(+) diff --git a/udev/90-libinput-model-quirks.hwdb b/udev/90-libinput-model-quirks.hwdb index 69e28ae..fd075e0 100644 --- a/udev/90-libinput-model-quirks.hwdb +++ b/udev/90-libinput-model-qui

[PATCH libinput 9/9] touchpad: drop fake resolution handling

Now that we have all devices init a fixed resolution we don't need code to handle custom cases anymore. Signed-off-by: Peter Hutterer --- src/evdev-mt-touchpad-buttons.c | 65 ++--- src/evdev-mt-touchpad.c | 30 +-- 2 files changed, 23

[PATCH libinput 3/9] util: add a helper function to parse a "WIDTHxHEIGHT" property

Signed-off-by: Peter Hutterer --- src/libinput-util.c | 30 ++ src/libinput-util.h | 2 ++ test/misc.c | 47 +++ 3 files changed, 79 insertions(+) diff --git a/src/libinput-util.c b/src/libinput-util.c index 3a9c8db

[RFC libinput 0/9] touchpad: force resolutions for all touchpads

Not all touchpads provide x/y axis resolution. some of them (apple touchpads) we fix up in the systemd hwdb but others are harder to detect or fix in a generic manner. so we set a fake resolution (1 unit/mm), but that's just to avoid divide-by-zero. the touchpad code handles physical distances wh

[PATCH libinput 1/9] udev: make sure the udev callout path is valid for a test run

udev requires callout binaries to sit in /lib/udev or otherwise provide an absolute path. The test suite should work without installing everything first, so create two rule files - one to install, one with the path to the $builddir/test Signed-off-by: Peter Hutterer --- configure.ac

[PATCH libinput 2/9] evdev: simplify setting a fake resolution

The only two callers passed in the fake resolution anyway, so we don't need extra parameters here. We don't allow devices with only x or y resolution set, either both or none. And we can use libevdev_set_abs_resolution() rather than handling absinfo structs. Signed-off-by: Peter Hutterer --- src

[PATCH] xwayland: Always free reply from xcb_get_property_reply()

Signed-off-by: Bryce Harrington --- xwayland/selection.c | 10 +++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/xwayland/selection.c b/xwayland/selection.c index 572a0b5..451b915 100644 --- a/xwayland/selection.c +++ b/xwayland/selection.c @@ -119,8 +119,9 @@ weston_wm_get

Re: [PATCH libinput 1/5] util: allow list_remove() on a NULL node

On Tue, Jun 30, 2015 at 02:22:34PM +0200, Hans de Goede wrote: > Hi Peter, > > On 29-06-15 05:49, Peter Hutterer wrote: > >Don't require a list_init() on a node before we can call list_remove on it, > >it > >clutters up the code for little benefit. > > > >Signed-off-by: Peter Hutterer > >--- > >

Re: [PATCH 06/10] compositor-drm: Handle more than two output crtcs per card

On Fri, Jun 26, 2015 at 01:34:42PM -0500, Derek Foreman wrote: > On 21/06/15 02:25 PM, Mario Kleiner wrote: > > Allow proper handling of output->pipe > 1 to support > > triple-head graphics cards etc. by using the "high-crtc" > > support introduced in Linux 2.6.39 and libdrm 2.4.25 > > around May 2

Re: [PATCH 04/10] compositor-drm: Allow weston_output_mode_switch_to_native() to work.

On Mon, Jun 22, 2015 at 10:08:04AM -0500, Derek Foreman wrote: > Reviewed-By: Derek Foreman Thanks, pushed: To ssh://git.freedesktop.org/git/wayland/weston 872797c..8081704 master -> master > On 21/06/15 02:25 PM, Mario Kleiner wrote: > > Initialize output->native_mode with the initially

Re: [PATCH 02/10] compositor-drm: Fix refresh rate selection in drm_output_switch_mode

On Sun, Jun 21, 2015 at 09:25:09PM +0200, Mario Kleiner wrote: > The matching logic in choose_mode() compared refresh rate > of a drm_mode candidate mode expressed in Hz against the > requested refresh rate of the target weston_mode expressed > in milliHz, so the match always failed and the logic a

Re: [PATCH 01/10] desktop-shell: Allow multiple active fullscreen windows on multi-display setup.

On Sun, Jun 21, 2015 at 09:25:08PM +0200, Mario Kleiner wrote: > Desktop shell demoted all fullscreen shell surfaces on all active > outputs of a multi-display setup whenever any shell surface was > activated anywhere. This made it impossible to have multiple > fullscreen windows on separate output

Re: [PATCH 06/10] compositor-drm: Handle more than two output crtcs per card

On Mon, Jun 29, 2015 at 2:06 PM, Mario Kleiner wrote: > > The bits are not a bit mask where a specific bit position corresponds to a > specific pipe, but those bits encode a 5 bits wide pipe number between 0 > and (2^5)-1 ie. 0-31. The comment in the code snippet you show about bits > 1-6 is a bi

Re: [PATCH libinput 1/5] util: allow list_remove() on a NULL node

On Tue, Jun 30, 2015 at 5:22 AM, Hans de Goede wrote: > > + if (elm->next == NULL && elm->prev == NULL) >> + return; >> + >> elm->prev->next = elm->next; >> elm->next->prev = elm->prev; >> elm->next = NULL; >> >> > I do not think this is a good idea, mo

Re: [PATCH libinput 1/5] util: allow list_remove() on a NULL node

Hi Peter, On 29-06-15 05:49, Peter Hutterer wrote: Don't require a list_init() on a node before we can call list_remove on it, it clutters up the code for little benefit. Signed-off-by: Peter Hutterer --- src/libinput-util.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/src/libinpu