On 06.07.2016 19:44, Adam Jackson wrote:
> I've merged some fixes back from master to the 1.18 branch, and plan to
> release 1.18.4 in the next few days. Give a shout if there's anything
> wrong on the branch, or if there's any other changes that should be
> picked up.
>
> - ajax
>
There is a c
We currently censor images from dix's GetImage, but not from
ShmGetImage. This is a method to bypass XACE, creating a potential
leak. We should censor in both methods.
Signed-off-by: Andrew Eikum
---
Xext/shm.c | 17 +
1 file changed, 17 insertions(+)
diff --git a/Xext/shm.c b/X
Hi,
On 06-07-16 19:44, Adam Jackson wrote:
I've merged some fixes back from master to the 1.18 branch, and plan to
release 1.18.4 in the next few days. Give a shout if there's anything
wrong on the branch, or if there's any other changes that should be
picked up.
I'm not sure the "modesetting:
I've merged some fixes back from master to the 1.18 branch, and plan to
release 1.18.4 in the next few days. Give a shout if there's anything
wrong on the branch, or if there's any other changes that should be
picked up.
- ajax
___
xorg-devel@lists.x.org
Hi all,
Currently the modesetting driver sets a cap flag claiming that it can
be an offload source, yet using DRI_PRIME=1 with the modesetting driver
being the driver for slave nvidia gpu, does not work unless the master
gpu driver (intel) has dri3 enabled, at which point the whole xserver
no lon
On Tue, 2016-07-05 at 15:28 +0100, Jose Abreu wrote:
> - First: My driver only supports 24 bpp (I mean real 24
> bits, not 24 packed in 32 bits). Is there a way to specify to X
> (or specify in the driver itself) to use 24bpp **only** in the
> new driver that I created?
Kind of. The argument
Am 05.07.2016 19:07, schrieb Adam Jackson:
> Useless as an XVideo implementation with zero adaptors might be, it's
> apparently a thing in the wild. Catch this case and bail out of xv init
> if it happens.
>
> Signed-off-by: Adam Jackson
> ---
> hw/kdrive/ephyr/ephyrvideo.c | 2 +-
> 1 file ch
Hi Adam,
> > That mechanism would probably not work as is with O-R windows for a
> > couple of reasons:
>
> Your descriptions here seem to assume the inability to fix the
> compositor, which to me seems... insane?
No, I did not assume this, but I find focus management in X11 to be quite
compli