1. 02 Feb, 2021 14 commits
  2. 29 Jan, 2021 4 commits
  3. 27 Jan, 2021 1 commit
    • Julien Cristau's avatar
      compiler.h: don't define inb/outb and friends on mips · 0148a15d
      Julien Cristau authored and Adam Jackson's avatar Adam Jackson committed
      The definition relies on IOPortBase, which is only ever set in
      hw/xfree86/os-support/bsd/arm_video.c
      
      This caused build failures on linux/mips with GCC 10, due to this
      change (from https://gcc.gnu.org/gcc-10/changes.html#c):
      
      "GCC now defaults to -fno-common. As a result, global variable accesses
      are more efficient on various targets. In C, global variables with
      multiple tentative definitions now result in linker errors. With
      -fcommon such definitions are silently merged during linking."
      
      As a result anything including compiler.h would get its own definition
      of IOPortBase and the linker would error out.
      0148a15d
  4. 22 Jan, 2021 3 commits
  5. 08 Jan, 2021 1 commit
  6. 06 Jan, 2021 1 commit
  7. 05 Jan, 2021 1 commit
    • Povilas Kanapickas's avatar
      xi: Don't deliver emulated motion when there's no owner for touch end · 3ab3083c
      Povilas Kanapickas authored and Peter Hutterer's avatar Peter Hutterer committed
      Pointer-emulated touch events should only be delivered to the client
      that owns the sequence even if it's a core client that became the
      effective owner of the sequency by selecting for pointer press and
      movement.
      
      Currently the emulated events are delivered like this already (see
      TouchResourceIsOwner() check in DeliverEmulatedMotionEvent()), except in
      the case of TouchEnd, in which case the generated motion event is still
      delivered to some client that's not necessarily the owner of the touch
      sequence.
      
      We already know whether a touch sequence that is about to emulate a
      pointer event has an owner, we just need to check that. This further
      allows to simplify DeliverEmulatedMotionEvent() as it won't ever be
      called for non-owned touch events.
      
      https://bugs.freedesktop.org/show_bug.cgi?id=60394
      
      Signed-off-by: Povilas Kanapickas's avatarPovilas Kanapickas <povilas@radix.lt>
      3ab3083c
  8. 18 Dec, 2020 2 commits
  9. 17 Dec, 2020 3 commits
  10. 15 Dec, 2020 2 commits
  11. 14 Dec, 2020 3 commits
  12. 10 Dec, 2020 3 commits
    • Olivier Fourdan's avatar
      xwayland: Hold window buffer until released · f95d81e8
      Olivier Fourdan authored
      
      
      The window buffer mechanism would free the pixmap and its corresponding
      Wayland buffer as soon as window buffers are disposed.
      
      Typically when the X11 window is unrealized, the current window buffer
      is still used by the Wayland compositor and yet Xwayland will destroy
      the buffer.
      
      As a matter of fact, Xwayland should not destroy the Wayland buffer
      before the wl_buffer.release event is received.
      
      Add a reference counter to the window buffer similar to the to pixmap
      reference counter to keep the buffer around until the release callback
      is received.
      
      Increase that reference counter on the buffer which will be attached to
      the surface, and drop that reference when receiving the release callback
      notification.
      
      v2: Use a specific reference counter on the buffer rather than relying
          on the pixmap refcnt (Michel Dänzer <mdaenzer@redhat.com>)
      Signed-off-by: default avatarOlivier Fourdan <ofourdan@redhat.com>
      Reviewed-by: Michel Dänzer's avatarMichel Dänzer <mdaenzer@redhat.com>
      Acked-by: Martin Peres ...
      f95d81e8
    • Olivier Fourdan's avatar
      xwayland: Hold cursor buffer until released · 85d8eac4
      Olivier Fourdan authored
      
      
      The cursor code would destroy the buffer as soon as the cursor is
      unrealized on X11 side.
      
      Yet, the Wayland compositor may still be using the buffer as long as a
      released callback has not been received.
      
      Increase the reference counter on the pixmap to hold a reference on the
      pixmap when attaching it to the surface and use the new pixmap release
      callback mechanism to release that reference when the buffer is
      released.
      Signed-off-by: default avatarOlivier Fourdan <ofourdan@redhat.com>
      Acked-by: Martin Roukala's avatarMartin Peres <martin.peres@mupuf.org>
      Reviewed-by: Michel Dänzer's avatarMichel Dänzer <mdaenzer@redhat.com>
      85d8eac4
    • Olivier Fourdan's avatar
      xwayland: Factorize common cursor code · 79afbd60
      Olivier Fourdan authored
      
      
      The seat and tablet cursor functions are very similar, factorize the
      commonalities to simplify the code and reduce the copy/paste.
      Signed-off-by: default avatarOlivier Fourdan <ofourdan@redhat.com>
      Reviewed-by: Michel Dänzer's avatarMichel Dänzer <mdaenzer@redhat.com>
      79afbd60
  13. 08 Dec, 2020 2 commits