1. 10 Nov, 2021 1 commit
  2. 09 Nov, 2021 1 commit
  3. 13 Oct, 2021 1 commit
  4. 11 Oct, 2021 1 commit
  5. 04 Oct, 2021 1 commit
    • Alexander Richardson's avatar
      tests: allow cross-compiling the tests · 78f654ed
      Alexander Richardson authored
      I am trying to cross-compile from macOS for FreeBSD and this is currently
      failing since the tests attempt to build a native binary that links
      against the wayland-client and wayland-server libraries for the FreeBSD
      system. I believe we should be building them for the target system and
      not the current host (especially since there is no way to build
      wayland-client and wayland-server for macOS, but I do want to check that
      the files build correctly for FreeBSD).
      Signed-off-by: Alexander Richardson's avatarAlex Richardson <Alexander.Richardson@cl.cam.ac.uk>
      Reviewed-by: Simon Ser's avatarSimon Ser <contact@emersion.fr>
  6. 19 Sep, 2021 1 commit
  7. 15 Sep, 2021 1 commit
  8. 13 Sep, 2021 1 commit
    • Peter Hutterer's avatar
      pointer-gestures: add hold gestures · 824cea61
      Peter Hutterer authored and Simon Ser's avatar Simon Ser committed
      Hold gestures merely denote "there are fingers on the touchpad but they are
      not moving". As touchpad touches are generally fully abstracted, a client
      cannot currently know when a user is interacting with the touchpad without
      moving - no motion events will be sent in this case.
      The two use-cases here are:
      - hold-to-interact: where a hold gesture is active for some time
        a menu could pop up, or some object is selected, etc.
      - hold-to-cancel: where e.g. kinetic scrolling is currently active, the start
        of a hold gesture can be used to stop the scroll
      Since hold gestures by definition do not have movement, there is no need for
      an "update" stage in the gesture.
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
  9. 09 Sep, 2021 1 commit
  10. 01 Sep, 2021 4 commits
  11. 28 Aug, 2021 1 commit
  12. 06 Aug, 2021 2 commits
    • Simon Ser's avatar
      readme: fix unformatted label references · 7dffa6f3
      Simon Ser authored
      The newlines prevent the labels from being properly formatted.
      Additionally, the second label reference has a typo (extra "s").
      Signed-off-by: Simon Ser's avatarSimon Ser <contact@emersion.fr>
    • Xaver Hugl's avatar
      staging/drm-lease: DRM lease protocol support · aa3df408
      Xaver Hugl authored and Simon Ser's avatar Simon Ser committed
      DRM leasing is a feature which allows the DRM master to "lease" a subset
      of its DRM resources to another DRM master via drmModeCreateLease, which
      returns a file descriptor for the new DRM master. We use this protocol
      to negotiate the terms of the lease and transfer this file descriptor to
      In less DRM-specific terms: this protocol allows Wayland compositors to
      give over their GPU resources (like displays) to a Wayland client to
      exclusively control.
      The primary use-case for this is Virtual Reality headsets, which via the
      non-desktop DRM property are generally not used as desktop displays by
      Wayland compositors, and for latency reasons (among others) are most
      useful to games et al if they have direct control over the DRM resources
      associated with it. Basically, these are peripherals which are of no use
      to the compositor and may be of use to a client, but since they are tied
      up in DRM we need to use DRM leasing to get them into client's hands.
  13. 04 Aug, 2021 4 commits
  14. 27 Jul, 2021 1 commit
  15. 21 Jul, 2021 1 commit
    • Daniel Stone's avatar
      xdg-shell: Make xdg_surface fail when surface has role · 11fecf08
      Daniel Stone authored
      It is illegal for a surface to have more than one role. The only thing
      which can be done with an xdg_surface (apart from destroying it) is to
      assign the surface a role with the get_toplevel, get_popup, etc
      On Mutter, calling get_xdg_surface on a surface which already has an
      assigned role generates the 'role' protocol error. Weston will not send
      an error, however it may later abort on a failed assert during cleanup.
      wlroots allows this case, and only sends the role error when assigning
      an explicit role through creating a toplevel or popup.
      On the grounds that it makes no sense to create an xdg_surface for a
      wl_surface which already has a role, make it explicitly illegal.
      cf. weston!559, weston!627
      Signed-off-by: Daniel Stone's avatarDaniel Stone <daniels@collabora.com>
  16. 01 Jul, 2021 1 commit
  17. 25 Jun, 2021 1 commit
    • Simon Ser's avatar
      readme: mention the DCO · 353ffc65
      Simon Ser authored
      We haven't mentionned the DCO anywhere, yet we were requiring all
      contributions to have a Signed-off-by line to accept it.
      Add a reference to the DCO in our README's "development procedure"
      Signed-off-by: Simon Ser's avatarSimon Ser <contact@emersion.fr>
  18. 23 Jun, 2021 1 commit
  19. 07 Jun, 2021 2 commits
  20. 03 Jun, 2021 1 commit
  21. 18 May, 2021 1 commit
    • Simon Ser's avatar
      members: add GitLab usernames · b4ecb55e
      Simon Ser authored
      Add GitLab usernames for all members, so that they can easily be
      mentionned in merge requests or issues.
      The only missing username is for Alan Griffiths, I don't think they
      have a GitLab account at the moment.
      Signed-off-by: Simon Ser's avatarSimon Ser <contact@emersion.fr>
  22. 30 Apr, 2021 4 commits
  23. 14 Apr, 2021 2 commits
    • Jonas Ådahl's avatar
      Replace `unstable` with `staging` · 5381e39b
      Jonas Ådahl authored and Simon Ser's avatar Simon Ser committed
      Time has told us that the effort going from `unstable` to `stable` is
      enough of a burdon meaning very few protocols are ever declared stable.
      To mitigate this, and thus avoid having protocols being "stuck" being
      "unstable" indefinitely, replace the "unstable" -> "stable" procedure
      with a "staging" -> "stable" procedure, where declaring a protocol
      stable does not involve any changes to any implementations.
      The only side effect of this is that version numbers are to forever be
      part of all interface names and protocol XML files.
      Closes: #30
      Signed-off-by: Jonas Ådahl's avatarJonas Ådahl <jadahl@gmail.com>
      Reviewed-by: Simon Ser's avatarSimon Ser <contact@emersion.fr>
    • Simon Ser's avatar
      xdg-foreign: add error enums · b1670b4d
      Simon Ser authored
      The protocol states that the client must provide xdg_toplevel surfaces,
      but doesn't specify protocol error values that can be sent by the
      Signed-off-by: Simon Ser's avatarSimon Ser <contact@emersion.fr>
  24. 13 Apr, 2021 1 commit
    • Peter Hutterer's avatar
      pointer-gestures: correct description of pinch · 17bef0ed
      Peter Hutterer authored
      This is being picky, but "pinch/spread" is the physical gesture, zoom and
      rotate is the effect that clients provide in response to that gesture.
      Let's use pinch only here since spread is more ambiguous in english, as anyone
      who's ever had butter on their bread would know.
      Also, everything else is referring to it as pinch anyway, so zoom/rotate here
      is the odd one out.
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
  25. 05 Apr, 2021 1 commit
  26. 31 Mar, 2021 2 commits
    • Simon Ser's avatar
      linux-dmabuf: clarify what mixed valid/INVALID modifiers mean · 3683a5eb
      Simon Ser authored
      This commit makes it clear that compositors can send valid modifiers and
      DRM_FORMAT_MOD_INVALID for a given format. This means that the compositor
      supports both implicit and explicit modifiers. See the warning further
      > Warning: It should be an error if the format/modifier pair was not
      > advertised with the modifier event. This is not enforced yet because
      > some implementations always accept DRM_FORMAT_MOD_INVALID. Also
      > version 2 of this protocol does not have the modifier event.
      Xwayland already requires compositors to send DRM_FORMAT_MOD_INVALID
      for importing buffers with an implicit modifier [1].
      In a future protocol version, it would be nice to make it a protocol
      error (or at least a soft failure) to use any format/modifier pair that
      wasn't advertised. A use-case for this is Vulkan compositors: the Vulkan
      DMA-BUF extensions require an explicit modifier and cannot import
      buffers which have an implicit modifier.
      [1]: https://gitlab.freedesktop.org/xorg/xserver/-/blob/6c51818a0f55282cbe5a870f58ca82ca45ee472d/hw/xwayland/xwayland-glamor-gbm.c#L328
      Signed-off-by: Simon Ser's avatarSimon Ser <contact@emersion.fr>
    • Jonas Ådahl's avatar
      ci: Make the FDO_UPSTREAM_REPO variable global · 42da2294
      Jonas Ådahl authored
      ci-fairy doesn't know how to to look at $CI_MERGE_REQUEST_PROJECT_PATH
      right now, so if we don't manually set $FDO_UPSTREAM_REPO, ci-fairy will
      (without verbose logging turned on) silently fall back on the source
      repository project path for finding the branch point. This might fail if
      the owner of the source repository hasn't updated the `master` branch of
      their fork.
      Related: freedesktop/ci-templates#32
      Signed-off-by: Jonas Ådahl's avatarJonas Ådahl <jadahl@gmail.com>
  27. 26 Mar, 2021 1 commit