1. 14 Feb, 2018 2 commits
    • Adam Jackson's avatar
      glx: Use vnd layer for dispatch (v4) · d8ec33fe
      Adam Jackson authored
      The big change here is MakeCurrent and context tag tracking. We now
      delegate context tags entirely to the vnd layer, and simply store a
      pointer to the context state as the tag data. If a context is deleted
      while it's current, we allocate a fake ID for the context and move the
      context state there, so the tag data still points to a real context. As
      a result we can stop trying so hard to detach the client from contexts
      at disconnect time and just let resource destruction handle it.
      
      Since vnd handles all the MakeCurrent protocol now, our request handlers
      for it can just be return BadImplementation. We also remove a bunch of
      LEGAL_NEW_RESOURCE, because now by the time we're called vnd has already
      allocated its tracking resource on that XID.
      
      v2: Update to match v2 of the vnd import, and remove more redundant work
      like request length checks.
      
      v3: Add/remove the XID map from the vendor private thunk, not the
      backend. (Kyle Brenneman)
      
      v4: Fix deletion of ghost contexts (Kyle Brenneman)
      Signed-off-by: Adam Jackson's avatarAdam Jackson <ajax@redhat.com>
      d8ec33fe
    • Alexander Volkov's avatar
      Xephyr: Require xcb-shm version 1.9.3 or newer · 8510f542
      Alexander Volkov authored
      It's needed for FD-passing.
      Signed-off-by: Alexander Volkov's avatarAlexander Volkov <a.volkov@rusbitech.ru>
      Reviewed-by: Adam Jackson's avatarAdam Jackson <ajax@redhat.com>
      8510f542
  2. 02 Feb, 2018 1 commit
  3. 01 Feb, 2018 1 commit
  4. 24 Jan, 2018 1 commit
    • Olivier Fourdan's avatar
      xwayland: Add optional xdg-output support · da8de2a7
      Olivier Fourdan authored
      The xdg-output protocol aims at describing outputs in way which is
      more in line with the concept of an output on desktop oriented systems.
      
      For now it just features the position and logical size which describe
      the output position and size in the global compositor space.
      
      This is however much useful for Xwayland to advertise the output size
      and position to X11 clients which need this to configure their surfaces
      in the global compositor space as the compositor may apply a different
      scale from what is advertised by the output scaling property (to achieve
      fractional scaling, for example).
      
      This was added in wayland-protocols 1.10.
      Reviewed-by: Adam Jackson's avatarAdam Jackson <ajax@redhat.com>
      Signed-off-by: default avatarOlivier Fourdan <ofourdan@redhat.com>
      da8de2a7
  5. 16 Jan, 2018 1 commit
  6. 08 Jan, 2018 1 commit
    • Helmut Grohne's avatar
      build: guess availability of monotonic clock for cross compilation · c601c8fa
      Helmut Grohne authored
      When cross compiling, the value of MONOTONIC_CLOCK would be "cross
      compiling", because AC_RUN_IFELSE doesn't work. However when enabling
      wayland, a monotonic clock is required and configure aborts.
      
      We change detection of CLOCK_MONOTONIC to degrade it gracefully from a
      run check to a declaration check in case of cross compilation based on
      the assumption that most systems will have a monotonic clock and those
      that don't won't be able to run Xwayland anyway. The trade-off
      essentially is either "always fail cross compilation" or "produce an
      unusable Xwayland for unusual platform" and this commit switches to the
      latter.
      Signed-off-by: default avatarHelmut Grohne <helmut@subdivi.de>
      Bug-Debian: https://bugs.debian.org/882531Reviewed-by: Adam Jackson's avatarAdam Jackson <ajax@redhat.com>
      c601c8fa
  7. 06 Nov, 2017 1 commit
  8. 20 Sep, 2017 1 commit
  9. 13 Sep, 2017 1 commit
  10. 22 Aug, 2017 3 commits
  11. 01 Aug, 2017 1 commit
  12. 27 Jun, 2017 1 commit
  13. 02 Jun, 2017 1 commit
  14. 03 May, 2017 1 commit
    • Adam Jackson's avatar
      xfree86: Silence a new glibc warning · d732c365
      Adam Jackson authored
      glibc would like to stop declaring major()/minor() macros in
      <sys/types.h> because that header gets included absolutely everywhere
      and unix device major/minor is perhaps usually not what's expected. Fair
      enough. If one includes <sys/sysmacros.h> as well then glibc knows we
      meant it and doesn't warn, so do that if it exists.
      Signed-off-by: Adam Jackson's avatarAdam Jackson <ajax@redhat.com>
      d732c365
  15. 28 Apr, 2017 1 commit
  16. 25 Apr, 2017 1 commit
  17. 21 Apr, 2017 2 commits
  18. 23 Mar, 2017 3 commits
  19. 07 Mar, 2017 1 commit
  20. 01 Mar, 2017 4 commits
  21. 28 Feb, 2017 2 commits
  22. 23 Feb, 2017 1 commit
  23. 16 Feb, 2017 1 commit
  24. 08 Feb, 2017 1 commit
  25. 25 Jan, 2017 1 commit
  26. 19 Jan, 2017 2 commits
  27. 12 Jan, 2017 1 commit
  28. 30 Nov, 2016 1 commit
  29. 18 Nov, 2016 1 commit