Re: [PATCH xf86-input-libinput] Add tablet pad support

On Fri, Apr 22, 2016 at 11:01:03AM -0700, Jason Gerecke wrote: > On Thu, Apr 21, 2016 at 10:25 PM, Peter Hutterer > wrote: > > On Fri, Apr 22, 2016 at 12:07:27PM +1000, Peter Hutterer wrote: > >> > Also, on a somewhat-related note: I'm noticing that having > >> >

Re: [PATCH xproto v2] Don't let XFD_SETSIZE exceed FD_SETSIZE

On Mon, Apr 25, 2016 at 17:12:08 +0100, James Clarke wrote: > This fixes 2c94cdb453bc641246cc8b9a876da9799bee1ce7 on the Hurd, as FD_SETSIZE > is only 256, and so anyone using XFD_SETSIZE to iterate over the contents of > an fd_set will overrun the array. > > Signed-off-by: James Clarke

Re: [PATCH xwayland] xwayland-shm: fortify fallocate against EINTR

On Mon, 2016-04-25 at 16:10 +0300, Pekka Paalanen wrote: > In the mean time, Marek's patch gets my > Reviewed-by: Pekka Paalanen > because it is an improvement for many (most?) systems. Yeah, looks good to me. remote: I: patch #83402 updated using rev

Re: [PATCH xserver] configure.ac: Keep environment CFLAGS when testing

On Mon, 2016-04-25 at 15:31 +0100, Emil Velikov wrote: > On 23 March 2016 at 04:47, Alexandre Courbot wrote: > > > > DRI2 detection could fail if configure is invoked with a sysroot passed > > as CFLAGS. Ideally configure should invoke gcc with the sysroot argument > >

[PATCH xproto v2] Don't let XFD_SETSIZE exceed FD_SETSIZE

This fixes 2c94cdb453bc641246cc8b9a876da9799bee1ce7 on the Hurd, as FD_SETSIZE is only 256, and so anyone using XFD_SETSIZE to iterate over the contents of an fd_set will overrun the array. Signed-off-by: James Clarke --- Changes since v1: * Added Signed-off-by * Added

[PATCH] Don't let XFD_SETSIZE exceed FD_SETSIZE

This fixes 2c94cdb453bc641246cc8b9a876da9799bee1ce7 on the Hurd, as FD_SETSIZE is only 256, and so anyone using XFD_SETSIZE to iterate over the contents of an fd_set will overrun the array. --- Xpoll.h.in | 11 +++ 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/Xpoll.h.in

Re: [PATCH xserver v3] xfree86: Immediately handle failure to set HW cursor

Friendly ping - does this patch look good now? On Thu, Apr 7, 2016 at 3:48 PM, Alexandre Courbot wrote: > There is currently no reliable way to report failure to set a HW > cursor. Still such failures can happen if e.g. the MODE_CURSOR DRM > ioctl fails (which currently

Re: [PATCH xf86-input-libinput] Add tablet pad support

On Thu, Apr 21, 2016 at 10:25 PM, Peter Hutterer wrote: > On Fri, Apr 22, 2016 at 12:07:27PM +1000, Peter Hutterer wrote: >> > Also, on a somewhat-related note: I'm noticing that having >> > xf86-input-libinput and xf86-input-wacom installed alongside each >> > other

Re: [PATCH xf86-input-libinput] Add tablet pad support

On Thu, Apr 21, 2016 at 10:25 PM, Peter Hutterer wrote: > On Fri, Apr 22, 2016 at 12:07:27PM +1000, Peter Hutterer wrote: >> > Also, on a somewhat-related note: I'm noticing that having >> > xf86-input-libinput and xf86-input-wacom installed alongside each >> > other

Re: [PATCH xserver] configure.ac: Keep environment CFLAGS when testing

On 23 March 2016 at 04:47, Alexandre Courbot wrote: > DRI2 detection could fail if configure is invoked with a sysroot passed > as CFLAGS. Ideally configure should invoke gcc with the sysroot argument > passed to the configure script, but for some reason this is not done by >

Re: [PATCH xwayland] xwayland-shm: fortify fallocate against EINTR

On Mon, Apr 25, 2016 at 02:40:31PM +0200, Marek Chalupa wrote: > > On 04/25/16 12:20, Pekka Paalanen wrote: > > On Mon, 25 Apr 2016 11:33:00 +0200 > > Marek Chalupa wrote: > > > >> If posix_fallocate or ftruncate is interrupted by signal > >> while working, we return -1 as

Re: [xserver-xorg][PATCH 1/1] xwayland: ftruncate if posix_fallocate fails

On Mon, 25 Apr 2016 15:47:09 +0300 Ian Ray wrote: > On a slow system that is configured with SMART_SCHEDULE_POSSIBLE, large > posix_fallocate() requests may be interrupted by the SmartScheduleTimer > (SIGALRM) continuously. Fallback to ftruncate if posix_fallocate fails. > >

[xserver-xorg][PATCH 1/1] xwayland: ftruncate if posix_fallocate fails

On a slow system that is configured with SMART_SCHEDULE_POSSIBLE, large posix_fallocate() requests may be interrupted by the SmartScheduleTimer (SIGALRM) continuously. Fallback to ftruncate if posix_fallocate fails. Signed-off-by: Ian Ray --- hw/xwayland/xwayland-shm.c | 9

Re: [PATCH xwayland] xwayland-shm: fortify fallocate against EINTR

On Mon, 25 Apr 2016 15:56:58 +0300 Ian Ray wrote: > On Mon, Apr 25, 2016 at 02:40:31PM +0200, Marek Chalupa wrote: > > > > On 04/25/16 12:20, Pekka Paalanen wrote: > > > On Mon, 25 Apr 2016 11:33:00 +0200 > > > Marek Chalupa wrote: > > > > > >> If

Re: [PATCH xwayland] xwayland-shm: fortify fallocate against EINTR

On 04/25/16 12:20, Pekka Paalanen wrote: > On Mon, 25 Apr 2016 11:33:00 +0200 > Marek Chalupa wrote: > >> If posix_fallocate or ftruncate is interrupted by signal >> while working, we return -1 as fd and the allocation process >> returns BadAlloc error. That causes xwayland

Re: [PATCH] libpciaccess/vgaarb: add function to get default vga device and it's decodes.

On Sun, Apr 24, 2016 at 05:17:48PM +0200, Julien Cristau wrote: > On Thu, Apr 21, 2016 at 15:22:36 +0200, Stefan Dirsch wrote: > > > From: Egbert Eich > > > > Reenable default device when shutting down VGA arbitration. > >

Re: [PATCH xwayland] xwayland-shm: fortify fallocate against EINTR

On Mon, 25 Apr 2016 11:33:00 +0200 Marek Chalupa wrote: > If posix_fallocate or ftruncate is interrupted by signal > while working, we return -1 as fd and the allocation process > returns BadAlloc error. That causes xwayland clients to abort > with 'BadAlloc (insufficient

[PATCH xwayland] xwayland-shm: fortify fallocate against EINTR

If posix_fallocate or ftruncate is interrupted by signal while working, we return -1 as fd and the allocation process returns BadAlloc error. That causes xwayland clients to abort with 'BadAlloc (insufficient resources for operation)' even when there's a lot of resources available. Fix it by