Commits on Source (8)
-
-
-
Let's not give people any excuse for this spelling.
-
Some drivers (e.g. AMD GFX8-) don't support explicit format modifiers. On these drivers, gbm_bo_create_with_modifiers() will fail. This results in "Error getting buffer" in the logs later on with all X11 windows staying invisible. Fallback to the modifier-less API gbm_bo_create() in that case. Signed-off-by:
Simon Ser <contact@emersion.fr>
-
Olivier Fourdan authored
Since commit 204f10c2, we notify XRandR clients that the randr configuration has changes as soon as an new output is created. Yet, this might be premature, considering that at that point, we are still to receive the wl_output and xdg-output events that will most likely change the setup. So instead of calling RRTellChanged() from xwl_output_create(), wait until we get to call apply_output_change(), which occurs after the done events from both xdg-output and wl_output are received. Signed-off-by:
Olivier Fourdan <ofourdan@redhat.com> Reviewed-by:
Michel Dänzer <mdaenzer@redhat.com>
-
Olivier Fourdan authored
Currently, Xwayland assigns sequential output names for XRandR. When an output is hotplugged, a new name is assigned sequentially (XWAYLAND0, XWAYLAND1, etc.). This is a problem because if a monitor is unplugged and plugged again, it will get a new name each time. Luckily, xdg-output provides us with a name for the outputs. Even though the protocol states that the name is not a reflection of the underlying DRM connector name, it is to remain consistent across sessions with the same hardware and software configuration. So we could use the xdg-output name for the XRandR reported name for the output. Doing so is a bit tricky though, because the output name is set at creation and is not supposed to change. The xdg-output event that provides us with the name will come at a later time. So we just allocate a default fixed size for the output name at creation and just replace the default output name with the xdg-output name when that is known. Also, historically, some X11 clients were expecting output names in Xwayland to be named XWAYLAND<x> and used that to check whether they were running on Xwayland. Those clients should now use the Xwayland X11 extension which is designed specifically for that purpose. Signed-off-by:
Olivier Fourdan <ofourdan@redhat.com> Closes: #1353 See-also: !954 Reviewed-by:
Michel Dänzer <mdaenzer@redhat.com>
-
Olivier Fourdan authored
With the wl_output protocol, the actual bind to the interface is done in xwl_output_create(). Pass the version number from the registry so we can bind to the minimum version. Signed-off-by:
Olivier Fourdan <ofourdan@redhat.com> Reviewed-by:
Michel Dänzer <mdaenzer@redhat.com>
-
Olivier Fourdan authored
If wl_output provides us with an output name, use that as well. If we have both xdg_output.name and wl_output.name (from version >= 4), prefer the latter. Signed-off-by:
Olivier Fourdan <ofourdan@redhat.com>#> See-also: wayland/wayland-protocols!189 Reviewed-by:
Michel Dänzer <mdaenzer@redhat.com>
Showing
- hw/xwayland/xwayland-glamor-gbm.c 2 additions, 3 deletionshw/xwayland/xwayland-glamor-gbm.c
- hw/xwayland/xwayland-glamor.c 2 additions, 2 deletionshw/xwayland/xwayland-glamor.c
- hw/xwayland/xwayland-output.c 49 additions, 7 deletionshw/xwayland/xwayland-output.c
- hw/xwayland/xwayland-output.h 2 additions, 1 deletionhw/xwayland/xwayland-output.h
- hw/xwayland/xwayland-screen.c 2 additions, 2 deletionshw/xwayland/xwayland-screen.c
- hw/xwayland/xwayland-window.c 1 addition, 1 deletionhw/xwayland/xwayland-window.c
- hw/xwayland/xwayland.c 5 additions, 5 deletionshw/xwayland/xwayland.c