Re: [PATCH] present: Cancel the copy on unflip when aborting a pending flip

On 16.02.2015 20:51, Chris Wilson wrote: > If we handle a vblank notification and perform a copy whilst a flip is > still pending, we mark the pending flip for abort. After marking the > next flip completion for abortion, we then proceed to copy the requested > region into the restored Window

Re: [PATCH 1/3] present: Requery pending flips with the right sync_flip mode

On 08.02.2015 18:47, Chris Wilson wrote: > When verifying whether a pending flip is still valid, we need to pass > down the orignal sync_flip mode (e.g. if the driver only supports sync > flips, verifying a async flip will falsely fail). > > Signed-off-by: Chris Wilson

Re: [PATCH v2 xf86-input-libinput] Split mixed pointer/keyboard devices into two separate X devices

Hi, On 19-11-15 00:42, Peter Hutterer wrote: The server struggles with devices that are both, the protocol (especially XI2) requires a fairly strict separation of pointer vs keyboard devices. Though the server has a couple of hacks to route events correctly, mixed devices still experience bugs

Re: [PATCH] composite: Don't bother copying the pixmap for ForgetGravity windows (v3)

Adam Jackson writes: > I think this still needs to address what I wrote in paragraph 2 here: > > http://lists.freedesktop.org/archives/xorg-devel/2015-May/046376.html Yeah, I was just looking at the implementation and not the architecture... -- -keith signature.asc

Re: [PATCH xserver 1/5] glamor: Handle GL_OUT_OF_MEMORY when allocating texture images.

Pekka Paalanen writes: > On Wed, 18 Nov 2015 09:57:02 -0800 > Eric Anholt wrote: > >> Keith Packard writes: >> >> > Eric Anholt writes: >> > >> >> I think it's a safe enough assumption that we're not generating non-OOM

Direct hardware bashing modules (int10 et al) and recent hardware

Hi all, Inspired by a comment about using inline assembly in xserver, I did a quick through the codebase. It seems that most of the use-cases are related to the int10 module. To make things even more interesting - when using the Sun/Oracle compiler many additional functions will end up exported

Re: Direct hardware bashing modules (int10 et al) and recent hardware

On Thu, 2015-11-19 at 12:07 +, Emil Velikov wrote: > It seems that most of the use-cases are related to the int10 module. > To make things even more interesting - when using the Sun/Oracle > compiler many additional functions will end up exported relative to > gcc built xserver. That should

Re: [PATCH] composite: Don't bother copying the pixmap for ForgetGravity windows (v3)

On Wed, 2015-11-18 at 21:43 -0800, Keith Packard wrote: > "Jasper St. Pierre" writes: > > > +static Bool > > +needsPixmapCopy(WindowPtr pWin) > > +{ > > +WindowPtr pChild; > > + > > +if (pWin->bitGravity != ForgetGravity) > > +return TRUE; > > + > > +

Re: Direct hardware bashing modules (int10 et al) and recent hardware

On 20.11.2015 00:06, Adam Jackson wrote: > On Thu, 2015-11-19 at 12:07 +, Emil Velikov wrote: > >> fbdevhw, ramdac and extensions - dga, tslib. How people feel about >> those ? > > Removing fbdevhw would break mga and r128 and a few others on non-x86. Not to mention xf86-video-fbdev. --

[PATCH xf86-input-libinput] Replace the "fd" option when enabling dependent devices

The server uses pInfo->major/minor to detect if another device is using the same path for a logind-controlled fd. If so, it reuses that device's pInfo->fd and sets the "fd" option to that value. That pInfo->fd is the libinput epollfd though, not the actual device fd. This doesn't matter for us,

Re: [PATCH xlib] Add support for a display-specific error handler

Am 16.11.2015 um 21:57 schrieb Jasper St. Pierre: > Now do this: > > static void Foo() > { > Request1(); > Request2(); > } > > static void Bar() > { > Request1(); > Request3(); > } > > static void Thing(int x) > { > SetErrorHandler(); > if (x == 0) > Foo(); >

[PATCHv3] build: Fix systemd-daemon compile/linker flags

* Dont add systemd to REQUIRED_LIBS (this lead to build failure when libsystemd is available but libsystemd-daemon is not) * Only use systemd compile and linker flags where needed (libxtrans) * Try libsystemd (>= 210) first so it's used instead of the libsystemd-daemon wrapper that might also

[PATCH] xnest: Fix needless build dependency on xcb-util-keysyms

This was added in: commit 43014795087a0a8774dd9687f5967329b15f06a2 Author: Olivier Fourdan Date: Mon Jan 5 16:44:22 2015 +0100 Synchronize capslock in Xnest and Xephyr Which is fine if you're building both, but if you don't happen to have