Re: [PATCH RFC xserver] dix: Work around non-premultiplied ARGB cursor data

On 28.06.2016 18:50, Alexander E. Patrakov wrote: > 28.06.2016 13:22, Michel Dänzer пишет: >> This change checks for pixels with alpha == 0 and any non-alpha component >> != 0. If any such pixel is found, the data is assumed to be >> non-premultiplied and fixed up by multiplying the RGB components

Re: [PATCH xserver 3/3] dri2: Don't make reference to noClientException

Adam Jackson writes: > noClientException is now never filled in with a meaningful value, it's > always -1. The sole caller of this function disregards the error value > in any case. Sounds like we should just remove it from the client structure then? -- -keith signature.asc

Re: [PATCH v7 00/11] PRIME Synchronization

> Merged: > > remote: E: failed to find patch for rev > b601f96a5915a2c486b389483b291797e6fdf617. > remote: I: patch #80653 updated using rev > 1bdbc7e764ed7bf7c1ae46287dec368aa7c7e80d. > remote: E: failed to find patch for rev > f4c377953df1fe0e3196eda452acf0078e61. > remote: E: failed to

[PATCH xserver 1/3] sync: Don't do return client->noClientException

Hasn't been necessary since: commit 92ed75ac59e2d3af149cddb962efd05fc8487750 Author: Jamey Sharp Date: Mon May 10 20:22:05 2010 -0700 Eliminate boilerplate around client->noClientException. Signed-off-by: Adam Jackson --- Xext/sync.c

[PATCH xserver 3/3] dri2: Don't make reference to noClientException

noClientException is now never filled in with a meaningful value, it's always -1. The sole caller of this function disregards the error value in any case. Signed-off-by: Adam Jackson --- glx/glxdri2.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH xserver 2/3] dri3: Don't do return client->noClientException

Hasn't been necessary since: commit 92ed75ac59e2d3af149cddb962efd05fc8487750 Author: Jamey Sharp Date: Mon May 10 20:22:05 2010 -0700 Eliminate boilerplate around client->noClientException. Signed-off-by: Adam Jackson ---

Re: xf86-video-dummy: resize to exact resolution

On Thu, Jun 23, 2016 at 1:49 PM Adam Jackson wrote: > The idea has been discussed, but I don't know of anyone actually making > any effort in that direction. And honestly I'd prefer if they didn't. > Xorg so deeply assumes that you're talking to physical hardware that > making it

Re: [PATCH v7 00/11] PRIME Synchronization

On Tue, 2016-06-21 at 12:02 +1000, Dave Airlie wrote: > On 17 June 2016 at 13:06, Alex Goins wrote: > > Hello all, > > > > This patch set fixes the lack of NULL checking and the leaks in the > > blacklisting > > patches, and changes the UDL blacklist to a generic USB

Re: [PULL] hw/xwin patches

On Tue, 2016-06-28 at 14:36 +0100, Jon Turney wrote: > The following changes since commit 7397a2191f333a8632109873cc60d13ca4d550b0: > >   xwayland-input: Fake crossing to rootwin (2016-06-23 16:00:30 +1000) > > are available in the git repository at: > >  

Re: ARMSOC X11 plugin issues

Hi, So I've finally solved these issues. On Wed, Mar 23, 2016 at 10:17:05PM +0100, Maxime Ripard wrote: > Hi David, Marico, > > I've been developping a DRM/KMS driver for the Allwinner SoCs[1], with > an additional patch to allocate GPU buffers [2]. Since those SoCs also use > a Mali GPU, using

[PULL] hw/xwin patches

The following changes since commit 7397a2191f333a8632109873cc60d13ca4d550b0: xwayland-input: Fake crossing to rootwin (2016-06-23 16:00:30 +1000) are available in the git repository at: git://people.freedesktop.org/~jturney/xserver for you to fetch changes up to

Re: [PATCH xserver] xkb: add a cause to the xkb indicator update after a keymap change

On Tue, Jun 28, 2016 at 11:48:58 +1000, Peter Hutterer wrote: > Regression introduce by ac164e58870d which calls > XkbUpdateAllDeviceIndicators() with two NULL arguments. A few layers down into > the stack and we triggered a NULL-pointer dereference. In theory a NULL cause > is acceptable since

Re: [PATCH RFC xserver] dix: Work around non-premultiplied ARGB cursor data

Le 28/06/2016 à 10:22, Michel Dänzer a écrit : > From: Michel Dänzer > > Some games incorrectly use non-premultiplied ARGB cursor data, presumably > because that's what Windows uses. On some hardware (and with SWcursor), > this breaks areas of the cursor which are

[PATCH RFC xserver] dix: Work around non-premultiplied ARGB cursor data

From: Michel Dänzer Some games incorrectly use non-premultiplied ARGB cursor data, presumably because that's what Windows uses. On some hardware (and with SWcursor), this breaks areas of the cursor which are supposed to be transparent (and presumably also translucent