aboutsummaryrefslogtreecommitdiff
path: root/include
AgeCommit message (Collapse)Author
2019-02-05xdg-shell: destroy child popups on unmapemersion
It doesn't make sense to keep popups opened when unmapped. We also need to do so in wlr_xdg_popup_destroy so that popups are destroyed in the correct order.
2019-02-04Allow cursor render surface to be used as fbVincent Vanlaer
In order for a surface to be used as a cursor plane framebuffer, it appears that requiring the buffer to be linear is sufficient. GBM_BO_USE_SCANOUT is added in case GBM_BO_USE_LINEAR isn't sufficient on untested hardware. Fixes #1323 Removed wlr_drm_plane.cursor_bo as it does not serve any purpose anymore. Relevant analysis (taken from the PR description): While trying to implement a fix for #1323, I found that when exporting the rendered surface into a DMA-BUF and reimporting it with `GBM_BO_USE_CURSOR`, the resulting object does not appear to be valid. After some digging (turning on drm-kms debugging and switching to legacy mode), I managed to extract the following error: ``` [drm:__setplane_check.isra.1 [drm]] Invalid pixel format AR24 little-endian (0x34325241), modifier 0x100000000000001 ``` The format itself refers to ARGB8888 which is the same format as `renderer->gbm_format` used in master to create the cursor bo. However, using `gbm_bo_create` with `GBM_BO_USE_CURSOR` results in a modifier of 0. A modifier of zero represents a linear buffer while the modifier of the surface that is rendered to is `I915_FORMAT_MOD_X_TILED` (see https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/include/uapi/drm/drm_fourcc.h?h=v4.20.6#n263). In order to fix this mismatch in modifier, I added the `GBM_BO_USE_LINEAR` to the render surface and everything started to work just fine. I wondered however, whether the export and import is really necessary. I then decided to test if the back buffer of the render surface works as well, and at least on my hardware (Intel HD 530 and Intel UHD 620) it does. This is the patch in this PR and this requires no exporting and importing. I have to note that I cheated in order to import DMA_BUFs into a cursor bo when doing the first tests, since on import the Intel drivers check that the cursor is 64x64. This is strange since cursor sizes other than 64x64 have been around for quite some time now (https://lists.freedesktop.org/archives/mesa-commit/2014-June/050268.html). Removing this check made everything work fine. I later (while writing this PR) found out that `__DRI_IMAGE_USE_CURSOR` (to which `GBM_BO_USE_CURSOR` translates) has been deprecated in mesa (https://gitlab.freedesktop.org/mesa/mesa/blob/master/include/GL/internal/dri_interface.h#L1296), which makes me wonder what the usecase of `GBM_BO_USE_CURSOR` is. The reason we never encountered this is that when specifying `GBM_BO_USE_WRITE`, a dumb buffer is created trough DRM and the usage flag never reaches the Intel driver directly. The relevant code is in https://gitlab.freedesktop.org/mesa/mesa/blob/master/src/gbm/backends/dri/gbm_dri.c#L1011-1089 . From this it seems that as long as the size, format and modifiers are right, any surface can be used as a cursor.
2019-01-30relative-pointer-v1: time is in usec, not msecemersion
2019-01-30rootston: only allow one drag icon per seatemersion
2019-01-30seat: don't send motion if pointer hasn't movedemersion
2019-01-29Require libdrm >= 2.4.95emersion
2019-01-29Merge pull request #1509 from emersion/gbm-fmt-mismatchDrew DeVault
backend/drm: fix GBM format mismatch
2019-01-29backend/drm: fix GBM format mismatchemersion
We create the EGL config with GBM_FORMAT_ARGB8888, but then initialize GBM BOs with GBM_FORMAT_XRGB8888. This mismatch confuses Mesa. Instead, we can always use GBM_FORMAT_ARGB8888, and use DRM_FORMAT_XRGB8888 when calling drmModeAddFB2. Fixes https://github.com/swaywm/wlroots/issues/1438
2019-01-28Implement the pointer-gestures-unstable-v1 protocolGreg V
This protocol relays touchpad gesture events produced by libinput to supporting clients (e.g. Evince, Eye of GNOME).
2019-01-26pointer: add a frame eventemersion
Frame events group logically connected pointer events. It makes sense to make the backend responsible for sending frame events, since once the events are split (ie. once the frame events are stripped) it's not easy to figure out which events belongs to which frame again. This is also how Weston handles frame events. Fixes https://github.com/swaywm/wlroots/issues/1468
2019-01-24data-device: keep track of wlr_data_offer in wlr_seat listsemersion
2019-01-24data-device: add wlr_data_offer.typeemersion
2019-01-24data-device: unexport wlr_seat_client_send_selectionemersion
2019-01-24data-device: remove data_source_send_offeremersion
2019-01-24data-device: make sources inert, rename cancel to destroyemersion
2019-01-24data-device, primary-selection: add request_set_selectionemersion
This makes compositors able to block and/or customize set_selection requests coming from clients. For instance, it's possible for a compositor to disable rich selection content (by removing all MIME types except text/plain). This commit implements the design proposed in [1]. Two new events are added to wlr_seat: request_set_selection and request_set_primary_selection. Compositors need to listen to these events and either destroy the source or effectively set the selection. Fixes https://github.com/swaywm/wlroots/issues/1138 [1]: https://github.com/swaywm/wlroots/issues/1367#issuecomment-442403454
2019-01-21primary-selection: add a serial argumentemersion
The serial needs to be bumped when X11 clients set the selection, otherwise some Wayland clients (e.g. GTK) will overwrite it when they gain focus.
2019-01-21Fix indentation in various filesemersion
2019-01-20Add wlr_x11_output_set_titleJente Hidskes
2019-01-20wlr/backend/x11.h: add documentationJente Hidskes
Copied from wlr/backend/wayland.h and modified accordingly.
2019-01-20Merge pull request #1476 from emersion/fullscreen-shellDrew DeVault
fullscreen-shell-v1: initial protocol implementation
2019-01-19Add noop.h to include/wlr/backend/meson.buildRyan Dwyer
2019-01-17Introduce noop backendRyan Dwyer
The noop backend is similar to headless, but it doesn't contain a renderer. It can be used as a place to stash views for when there's no physical outputs connected.
2019-01-13Remove wlr_xdg_surface_send_close.Connor E
2019-01-10Add wlr_wl_output_set_titleDrew DeVault
2019-01-10Update Wayland backend to xdg-shell stableDrew DeVault
2019-01-06Merge pull request #1423 from emersion/data-controlDrew DeVault
Implement data-control-unstable-v1
2019-01-06relative-pointer-v1: move pointer iteration in wlrootsemersion
This makes sure we always send events to the right client.
2019-01-06fullscreen-shell-v1: initial protocol implementationemersion
2019-01-04Merge pull request #1432 from ForTheReallys/relative-pointersemersion
Relative pointers
2019-01-02Finish addressing @emersion's commentsAlex Maese
2018-12-30data-control-v1: update to latest protocol proposalemersion
2018-12-30data-control-v1: initial protocol implementationemersion
2018-12-22Protect against redefining MESA_EGL_NO_X11_HEADERSJente Hidskes
2018-12-21Standardize the wlr_box input paramatersTimidger
Fixes #1094
2018-12-21Add a listener for when the pointer gets destroyedAlex Maese
2018-12-21Address more of @emersion's commentsAlex Maese
2018-12-21Add unaccelerated pointer values to wlr_event_pointer_motion eventsAlex Maese
2018-12-21Address @emersion's commentsAlex Maese
2018-12-21Remove pointer resource from relative pointerAlex Maese
2018-12-21Removed relative pointers from wlr_seatAlex Maese
2018-12-21Remove wl_client from wlr_relative_pointer_v1Alex Maese
2018-12-21Add wlr_relative_pointer_v1.h to meson.buildAlex Maese
2018-12-21relative_pointer: implementation and code fixesrandom human
In particular, modified public creator and destructor function names, added a display destroy listener, safely extract user data from resources, send correct time (in usecs) in rootston, etc.
2018-12-21relative_pointer: send frame event to pointer for Xwaylandrandom human
2018-12-21relative_pointer: code formatting fixesrandom human
2018-12-21relative_pointer: implement protocol eventsrandom human
Implement zwp_relative_pointer_v1.relative_motion event, along with some glue code in wlr_seat_pointer and rootston.
2018-12-21relative_pointer: implement protocol requestsrandom human
Flesh out the details of the structs, signals, callback functions, and so on. weston-resizer silently works at this point (no events sent).
2018-12-21relative_pointer: create skeleton and buildrandom human
Add protocol, header and type files to build. Create skeleton structs, creator and destroyer, and define implementations.
2018-12-16backend/drm: don't insert duplicate custom modes, fix refresh rateemersion