1. 19 Sep, 2018 2 commits
  2. 09 Aug, 2018 1 commit
  3. 02 Aug, 2018 2 commits
  4. 27 Jun, 2018 1 commit
  5. 11 Jun, 2018 1 commit
  6. 14 May, 2018 1 commit
  7. 10 May, 2018 1 commit
  8. 24 Apr, 2018 3 commits
    • Adam Jackson's avatar
      xserver 1.20 RC5 · c6ab2102
      Adam Jackson authored
      Signed-off-by: Adam Jackson's avatarAdam Jackson <ajax@redhat.com>
      c6ab2102
    • Lyude Paul's avatar
      xwayland: Add glamor egl_backend for EGLStreams · 54ac0971
      Lyude Paul authored
      This adds initial support for displaying Xwayland applications through
      the use of EGLStreams and nvidia's custom wayland protocol by adding
      another egl_backend driver. This also adds some additional egl_backend
      hooks that are required to make things work properly.
      
      EGLStreams work a lot differently then the traditional way of handling
      buffers with wayland. Unfortunately, there are also a LOT of various
      pitfalls baked into it's design that need to be explained.
      
      This has a very large and unfortunate implication: direct rendering is,
      for the time being at least, impossible to do through EGLStreams. The
      main reason being that the EGLStream spec mandates that we lose the
      entire color buffer contents with each eglSwapBuffers(), which goes
      against X's requirement of not losing data with pixmaps.  no way to use
      an allocated EGLSurface as the storage for glamor rendering like we do
      with GBM, we have to rely on blitting each pixmap to it's respective
      EGLSurface producer each frame. In order to pull this off, we add two
      different additional egl_backend hooks that GBM opts out of
      implementing:
      
      - egl_backend.allow_commits for holding off displaying any EGLStream
        backed pixmaps until the point where it's stream is completely
        initialized and ready for use
      - egl_backend.post_damage for blitting the content of the EGLStream
        surface producer before Xwayland actually damages and commits the
        wl_surface to the screen.
      
      The other big pitfall here is that using nvidia's wayland-eglstreams
      helper library is also not possible for the most part. All of it's API
      for creating and destroying streams rely on being able to perform a
      roundtrip in order to bring each stream to completion since the wayland
      compositor must perform it's job of connecting a consumer to each
      EGLstream. Because Xwayland has to potentially handle both responding to
      the wayland compositor and it's own X clients, the situation of the
      wayland compositor being one of our X clients must be considered. If we
      perform a roundtrip with the Wayland compositor, it's possible that the
      wayland compositor might currently be connected to us as an X client and
      thus hang while both Xwayland and the wayland compositor await responses
      from eachother. To avoid this, we work directly with the wayland
      protocol and use wl_display_sync() events along with release() events to
      set up and destroy EGLStreams asynchronously alongside handling X
      clients.
      
      Additionally, since setting up EGLStreams is not an atomic operation we
      have to take into consideration the fact that an EGLStream can
      potentially be created in response to a window resize, then immediately
      deleted due to another pending window resize in the same X client's
      pending reqests before Xwayland hits the part of it's event loop where
      we read from the wayland compositor. To make this even more painful, we
      also have to take into consideration that since EGLStreams are not
      atomic that it's possible we could delete wayland resources for an
      EGLStream before the compositor even finishes using them and thus run
      into errors. So, we use quite a bit of tracking logic to keep EGLStream
      objects alive until we know the compositor isn't using them (even if
      this means the stream outlives the pixmap it backed).
      
      While the default backend for glamor remains GBM, this patch exists for
      users who have had to deal with the reprecussion of their GPU
      manufacturers ignoring the advice of upstream and the standardization of
      GBM across most major GPU manufacturers. It is not intended to be a
      final solution to the GBM debate, but merely a baindaid so our users
      don't have to suffer from the consequences of companies avoiding working
      upstream. New drivers are strongly encouraged not to use this as a
      backend, and use GBM like everyone else. We even spit this out as an
      error from Xwayland when using the eglstream backend.
      Signed-off-by: Lyude Paul's avatarLyude Paul <lyude@redhat.com>
      Acked-by: Daniel Stone's avatarDaniel Stone <daniels@collabora.com>
      Reviewed-by: Adam Jackson's avatarAdam Jackson <ajax@redhat.com>
      54ac0971
    • Lyude Paul's avatar
      xwayland: Add xwayland-config.h · 994f7810
      Lyude Paul authored
      Just a small autogenerated header that will soon contain more then just
      one macro.
      Signed-off-by: Lyude Paul's avatarLyude Paul <lyude@redhat.com>
      Reviewed-by: Daniel Stone's avatarDaniel Stone <daniels@collabora.com>
      Reviewed-by: Adam Jackson's avatarAdam Jackson <ajax@redhat.com>
      994f7810
  9. 12 Apr, 2018 1 commit
  10. 10 Apr, 2018 1 commit
  11. 05 Apr, 2018 1 commit
  12. 02 Apr, 2018 1 commit
  13. 28 Mar, 2018 2 commits
  14. 27 Mar, 2018 1 commit
  15. 21 Mar, 2018 2 commits
  16. 05 Mar, 2018 7 commits
  17. 28 Feb, 2018 1 commit
  18. 27 Feb, 2018 2 commits
    • Keith Packard's avatar
      Add RandR leases with modesetting driver support [v6] · e4e34476
      Keith Packard authored
      This adds support for RandR CRTC/Output leases through the modesetting
      driver, creating a lease using new kernel infrastructure and returning
      that to a client through an fd which will have access to only those
      resources.
      
      v2:	Restore CRTC mode when leases terminate
      
      	When a lease terminates for a crtc we have saved data for, go
      	ahead and restore the saved mode.
      
      v3:	Report RR_Rotate_0 rotations for leased crtcs.
      
      	Ignore leased CRTCs when selecting screen size.
      
      	Stop leasing encoders, the kernel doesn't do that anymore.
      
      	Turn off crtc->enabled while leased so that modesetting
      	ignores them.
      
      	Check lease status before calling any driver mode functions
      
      	When starting a lease, mark leased CRTCs as disabled and hide
      	their cursors. Also, check to see if there are other
      	non-leased CRTCs which are driving leased Outputs and mark
      	them as disabled as well. Sometimes an application will lease
      	an idle crtc instead of the one already associated with the
      	leased output.
      
      	When terminating a lease, reset any CRTCs which are driving
      	outputs that are no longer leased so that they start working
      	again.
      
      	This required splitting the DIX level lease termination code
      	into two pieces, one to remove the lease from the system
      	(RRLeaseTerminated) and a new function that frees the lease
      	data structure (RRLeaseFree).
      
      v4:	Report RR_Rotate_0 rotation for leased crtcs.
      
      v5: Terminate all leases on server reset.
      
      	Leases hang around after the associated client exits so that
      	the client doesn't need to occupy an X server client slot and
      	consume a file descriptor once it has gotten the output
      	resources necessary.
      
      	Any leases still hanging around when the X server resets or
      	shuts down need to be cleaned up by calling the kernel to
      	terminate the lease and freeing any DIX structures.
      
      	Note that we cannot simply use the existing
      	drmmode_terminate_lease function on each lease as that wants
      	to also reset the video mode, and during server shut down that
      
         modesetting: Validate leases on VT enter
      
      	The kernel doesn't allow any master ioctls to run when another
      	VT is active, including simple things like listing the active
      	leases. To deal with that, we check the list of leases
      	whenever the X server VT is activated.
      
         xfree86: hide disabled cursors when resetting after lease termination
      
      	The lessee may well have played with cursors and left one
      	active on our screen. Just tell the kernel to turn it off.
      
      v6:	Add meson build infrastructure
      
      [Also bumped libdrm requirement - ajax]
      Signed-off-by: Keith Packard's avatarKeith Packard <keithp@keithp.com>
      Reviewed-by: Adam Jackson's avatarAdam Jackson <ajax@redhat.com>
      e4e34476
    • Keith Packard's avatar
      xf86-video-modesetting: Record non-desktop kernel property at PreInit time · b91c787c
      Keith Packard authored
      Save any value of the kernel non-desktop property in the xf86Output
      structure to avoid non-desktop outputs in the default configuration.
      
      [Also bump randrproto requirement to a version that defines
      RR_PROPERTY_NON_DESKTOP - ajax]
      Signed-off-by: Keith Packard's avatarKeith Packard <keithp@keithp.com>
      Reviewed-by: Adam Jackson's avatarAdam Jackson <ajax@nwnk.net>
      b91c787c
  19. 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
  20. 02 Feb, 2018 1 commit
  21. 01 Feb, 2018 1 commit
  22. 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
  23. 16 Jan, 2018 1 commit
  24. 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
  25. 06 Nov, 2017 1 commit
  26. 20 Sep, 2017 1 commit