1. 15 Oct, 2019 1 commit
  2. 25 Sep, 2019 1 commit
  3. 20 Sep, 2019 1 commit
  4. 18 Jul, 2019 1 commit
  5. 25 Jun, 2019 1 commit
  6. 14 Jun, 2019 3 commits
  7. 09 May, 2019 1 commit
  8. 24 Apr, 2019 1 commit
  9. 19 Mar, 2019 1 commit
  10. 15 Mar, 2019 1 commit
    • Dave Airlie's avatar
      modesetting: add tile property support · 4407c78b
      Dave Airlie authored
      This adds tiling support to the driver, it retrieves the tile info from
      the kernel and translates it into the server format and exposes the
      property.
      
      (Ported from xserver commits 8fb8bbb3062f1a06621ab7030a9e89d5e8367b35
       and 6abdb54a11dac4e8854ff94ecdcb90a14321ab31)
      (Ported from amdgpu commit 6ee857726166f495abcd68e4ff60e3a09593d079)
      Reviewed-by: default avatarAlex Deucher <alexander.deucher@amd.com>
      4407c78b
  11. 14 Mar, 2019 1 commit
  12. 08 Mar, 2019 1 commit
  13. 06 Mar, 2019 1 commit
  14. 04 Mar, 2019 1 commit
  15. 01 Mar, 2019 1 commit
  16. 11 Feb, 2019 1 commit
    • Michel Dänzer's avatar
      Keep waiting for a pending flip if drm_handle_event returns 0 · 15697ee2
      Michel Dänzer authored
      drm_wait_pending_flip stopped waiting if drm_handle_event returned 0,
      but that might have processed only some unrelated DRM events. As long as
      the flip is pending, we have to keep waiting for its completion event.
      
      Noticed while working on the previous fix.
      
      (Ported from amdgpu commit 9045fb310f88780e250e60b80431ca153330e61b)
      15697ee2
  17. 28 Jan, 2019 6 commits
    • Michel Dänzer's avatar
      Call drmHandleEvent again if it was interrupted by a signal · 227123de
      Michel Dänzer authored
      drmHandleEvent can be interrupted by a signal in read(), in which case
      it doesn't process any events but returns -1, which
      drm_handle_event propagated to its callers. This could cause the
      following failure cascade:
      
      1. drm_wait_pending_flip stopped waiting for a pending flip.
      2. Its caller cleared drmmode_crtc->flip_pending before the flip
         completed.
      3. Another flip was attempted but got an unexpected EBUSY error because
         the previous flip was still pending.
      4. TearFree was disabled due to the error.
      
      The solution is to call drmHandleEvent if it was interrupted by a
      signal. We can do that in drm_handle_event, because when that is called,
      either it is known that there are events ready to be processed, or the
      caller has to wait for events to arrive anyway.
      
      Bugzilla: https://bugs.freedesktop.org/109364
      (Ported from amdgpu commit 3ff2cc225f6bc08364ee007fa54e9d0150adaf11)
      227123de
    • Michel Dänzer's avatar
      Only update drmmode_crtc->flip_pending after actually submitting a flip · 1bfdccf7
      Michel Dänzer authored
      And only clear it if it matches the framebuffer of the completed flip
      being processed.
      
      Fixes
      
       (WW) RADEON(0): flip queue failed: Device or resource busy
       (WW) RADEON(0): Page flip failed: Device or resource busy
       (EE) RADEON(0): present flip failed
      
      due to clobbering drmmode_crtc->flip_pending.
      
      Reproducer: Enable TearFree, run warzone2100 fullscreen, toggle
      Vertical sync on/off under Video Options. Discovered while investigating
      https://bugs.freedesktop.org/109364 .
      
      (Ported from amdgpu commit e72a02ba1d35743fefd939458b9d8cddce86e7f5)
      1bfdccf7
    • Michel Dänzer's avatar
      Don't allow TearFree scanout flips to complete in the same vblank period · dcd35272
      Michel Dänzer authored
      We were using a relative target of 0, meaning "complete the flip ASAP".
      This could result in the flip sometimes, but not always completing in
      the same vertical blank period where the corresponding drawing occurred,
      potentially causing judder artifacts with applications updating their
      window contents synchronized to the display refresh. A good way to test
      this is the vsynctester.com site in a windowed browser, where the judder
      results in the large "VSYNC" text intermittently appearing red or cyan
      instead of the expected gray.
      
      To avoid this, use a relative target MSC of 1, meaning that if a
      vertical blank period is in progress, the flip will only complete in the
      next one.
      
      Reported by Julian Tempel and Brandon Wright in
      https://bugs.freedesktop.org/106175 .
      
      (Ported from amdgpu commit a1b479c7d0066c481af920f297d6af9009dda11e)
      dcd35272
    • Michel Dänzer's avatar
      glamor: Avoid glamor_create_pixmap for pixmaps backing windows · 27470308
      Michel Dänzer authored
      If the compositing manager uses direct rendering (as is usually the case
      these days), the storage of a pixmap allocated by glamor_create_pixmap
      needs to be reallocated for sharing it with the compositing manager.
      Instead, allocate pixmap storage which can be shared directly.
      
      (Ported from amdgpu commit bf326f2ea19daa6c8da23d6788ff301ae70b8e69)
      27470308
    • Michel Dänzer's avatar
      dri2: Flush in dri2_create_buffer2 after calling glamor_set_pixmap_bo · 6d1dfe25
      Michel Dänzer authored
      To make sure the client can't use the shared pixmap storage for direct
      rendering first, which could produce garbage.
      
      Bugzilla: https://bugs.freedesktop.org/109235
      (Ported from amdgpu commit ebd32b1c07208f8dbe853e089f5e4b7c6a7a658a)
      6d1dfe25
    • Michel Dänzer's avatar
      dri3: Flush if necessary in dri3_fd_from_pixmap · 77d7abf4
      Michel Dänzer authored
      To make sure the client can't use the shared pixmap storage for direct
      rendering first, which could produce garbage.
      
      Bugzilla: https://bugs.freedesktop.org/109235
      (Ported from amdgpu commit d168532ee739f7e33a2798051e64ba445dd3859f)
      77d7abf4
  18. 09 Jan, 2019 2 commits
  19. 28 Dec, 2018 12 commits
  20. 20 Dec, 2018 1 commit
    • Michel Dänzer's avatar
      Detect and fix up non-premultiplied cursor data · 0c40a76d
      Michel Dänzer authored
      X server >= 1.18 already has code for this, but handle it with older X
      servers as well.
      
      (Ported from amdgpu commits ad6dfb0124860cf67730bde85867f81d9258c84d &
       426f9a49655f01863cf4d898f525e5f95984e0c4)
      0c40a76d
  21. 18 Dec, 2018 1 commit
    • Mario Kleiner's avatar
      Fix crash when page flipping in multi-X-Screen/Zaphod mode · 0058fd2e
      Mario Kleiner authored
      radeon_do_pageflip() indexed the flipdata->fb[] array
      indexing over config->num_crtc, but the flip completion
      routines, e.g., drmmode_flip_handler(), index that array
      via the crtc hw id from drmmode_get_crtc_id(crtc).
      
      This is mismatched and causes indexing into the wrong
      array slot at flip completion -> Server crash.
      
      Always use drmmode_get_crtc_id(crtc) for indexing into
      the array to fix this.
      
      Tested on a dual-X-Screen setup with one video output
      assigned to each X-Screen, page-flipping an OpenGL app
      on either of both X-Screens. This used to crash when
      flipping on X-Screen 1, now it doesn't anymore.
      
      Fixes: 740f0850 "Store FB for each CRTC in drmmode_flipdata_rec"
      Reviewed-by: Michel Dänzer's avatarMichel Dänzer <michel.daenzer@amd.com>
      Signed-off-by: default avatarMario Kleiner <mario.kleiner.de@gmail.com>
      0058fd2e