On Mon, Nov 12, 2018 at 11:55:18AM -0800, Alan Coopersmith wrote:
> Signed-off-by: Alan Coopersmith
Reviewed-by: Peter Hutterer
> ---
>
> v2: Moved to README.md and reduced whitespace in front of URLs so that
> gitlab renders them as links instead of code fragements - see
> https://gi
These QXL patches were both reviewed and ACKed by Frediano, but
apparently neither of us has commit rights to the xf86-video-qxl
repository. I'm not sure if this is since the move to gitlab or if we
never had commit rights to this repository. In any case, it looks like
we'll need an Xorg developer
The QXL driver names its outputs starting at 0 (e.g. Virtual-0,
Virtual-1, etc). This code was presumably copy/pasted from a different
driver, and is not necessary for the QXL driver. Other drivers simply
use the kernel connector_type_id which starts at 1. For example, the
modesetting driver change
The xrandr output name used by the QXL driver is based on the drm
connector type, but the names do not match the kernel names (see
/drivers/gpu/drm/drm_connector.c) or the modesetting driver names (see
hw/xfree86/drivers/modesetting/drmmode_display.c). Making these more
consistent will require less
Signed-off-by: Alan Coopersmith
---
v2: Moved to README.md and reduced whitespace in front of URLs so that
gitlab renders them as links instead of code fragements - see
https://gitlab.freedesktop.org/alanc/xcursorgen for formatted view
Restored link to Submitting Patches page so tha
Thanks - I've pushed all four patches to git master now:
https://gitlab.freedesktop.org/xorg/app/xlsatoms/commits/master
--
-Alan Coopersmith- alan.coopersm...@oracle.com
Oracle Solaris Engineering - https://blogs.oracle.com/alanc
__
The screensaver can regularly move its window to random offsets. It should
use the ConfigureWindow function instead of calling the Screen's MoveWindow
directly. Some MoveWindow implementations, such as compMoveWindow, rely on
Screen's ConfigNotify being called first as it happens in ConfigureWindow
Hi,
On Sat, 2018-11-10 at 13:12 -0800, Alan Coopersmith wrote:
> They were defined as empty strings on all platforms except for the
> long unsupported Cray systems which needed to use bitfields to define
> any type smaller than 64-bits.
>
> Signed-off-by: Alan Coopersmith
>
Thanks, Alan.
Revi