1. 09 Nov, 2020 1 commit
  2. 25 Aug, 2020 1 commit
  3. 29 Mar, 2020 1 commit
  4. 14 Jan, 2020 1 commit
  5. 13 Jan, 2020 1 commit
  6. 22 Nov, 2019 2 commits
  7. 05 Nov, 2019 1 commit
    • Marvin Schmidt's avatar
      build: glx: Lower gl version to work with libglvnd · a57729d3
      Marvin Schmidt authored and Aaron Plattner's avatar Aaron Plattner committed
      When using mesa with libglvnd support, mesa will no longer install the
      gl, glx, egl pkg-config files but instead let libglvnd provide them.
      libglvnd maintainers decided to change the versioning as it was
      mesa-specific previously. Now the libraries have versions of the API
      they expose[1].
      This causes problems when building the X server:
        checking for glproto >= 1.4.17 gl >= 9.2.0... no
        configure: error: Package requirements (glproto >= 1.4.17 gl >= 9.2.0) were not met:
        Requested 'gl >= 9.2.0' but version of gl is 1.2
      Lower the version requirement to 1.2 to allow building against libglvnd
      provided libraries
      [1] https://github.com/NVIDIA/libglvnd/commit/0dfaea2bcb7cdcc785f95e244223bd004a2d7fba
      (cherry picked from commit e6ef2b12)
  8. 29 Oct, 2019 3 commits
  9. 30 May, 2019 1 commit
  10. 25 Feb, 2019 1 commit
  11. 20 Feb, 2019 1 commit
  12. 25 Oct, 2018 1 commit
  13. 15 Oct, 2018 1 commit
  14. 07 Aug, 2018 1 commit
  15. 01 Aug, 2018 1 commit
  16. 10 May, 2018 1 commit
  17. 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>
    • Lyude Paul's avatar
      xwayland: Add glamor egl_backend for EGLStreams · 54ac0971
      Lyude Paul authored and Adam Jackson's avatar Adam Jackson committed
      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
      - 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
      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>
    • Lyude Paul's avatar
      xwayland: Add xwayland-config.h · 994f7810
      Lyude Paul authored and Adam Jackson's avatar Adam Jackson committed
      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>
  18. 12 Apr, 2018 1 commit
  19. 10 Apr, 2018 1 commit
  20. 05 Apr, 2018 1 commit
  21. 02 Apr, 2018 1 commit
  22. 28 Mar, 2018 2 commits
  23. 27 Mar, 2018 1 commit
  24. 21 Mar, 2018 2 commits
  25. 05 Mar, 2018 7 commits
  26. 28 Feb, 2018 1 commit
  27. 27 Feb, 2018 1 commit
    • Keith Packard's avatar
      Add RandR leases with modesetting driver support [v6] · e4e34476
      Keith Packard authored and Adam Jackson's avatar Adam Jackson committed
      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
      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
      	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>