1. 15 Mar, 2018 1 commit
  2. 08 Mar, 2018 1 commit
    • Michel Dänzer's avatar
      Pass extents to amdgpu_scanout_do_update by value · 8af98954
      Michel Dänzer authored
      amdgpu_scanout_extents_intersect could leave the scanout damage region
      in an invalid state, triggering debugging checks in pixman:
      
      *** BUG ***
      In pixman_region_append_non_o: The expression r->x1 < r->x2 was false
      Set a breakpoint on '_pixman_log_error' to debug
      8af98954
  3. 07 Mar, 2018 1 commit
  4. 06 Mar, 2018 1 commit
    • Michel Dänzer's avatar
      Only change Set/MoveCursor hooks from what we expect · b4a28bdc
      Michel Dänzer authored
      Since xf86CursorCloseScreen runs after AMDGPUCloseScreen_KMS,
      PointPriv->spriteFuncs doesn't point to the same struct in the latter as
      in AMDGPUCursorInit_KMS. So we were restoring info->Set/MoveCursor to
      the wrong struct. Then in the next server generation,
      info->Set/MoveCursor would end up pointing to
      drmmode_sprite_set/move_cursor, resulting in an infinite loop if one of
      them was called.
      
      To avoid this, only change the Set/MoveCursor hooks if their values
      match our expectations, otherwise leave them as is. This is kind of a
      hack, but the alternative would be invasive and thus risky changes to
      the way we're wrapping CloseScreen, and it's not even clear that can
      work without changing xserver code.
      
      Fixes: 69e20839 ("Keep track of how many SW cursors are visible on
                            each screen")
      (Ported from radeon commit 504b8721b17a672caf1ed3eab087027c02458cab)
      Acked-by: default avatarAlex Deucher <alexander.deucher@amd.com>
      b4a28bdc
  5. 02 Mar, 2018 4 commits
  6. 01 Mar, 2018 1 commit
  7. 16 Feb, 2018 1 commit
  8. 15 Feb, 2018 2 commits
  9. 14 Feb, 2018 6 commits
  10. 12 Feb, 2018 1 commit
  11. 22 Jan, 2018 1 commit
  12. 27 Dec, 2017 1 commit
    • Michel Dänzer's avatar
      Keep track of how many SW cursors are visible on each screen · 69e20839
      Michel Dänzer authored
      And use this to determine when we cannot use page flipping for DRI
      clients. We previously did this based on whether the HW cursor cannot
      be used on at least one CRTC, which had at least two issues:
      
      * Even while the HW cursor cannot be used, no SW cursor may actually be
        visible (e.g. because all cursors are disabled), in which case we can
        use page flipping for DRI clients anyway
      * Even while the HW cursor can be used, there may be SW cursors visible
        from non-core pointer devices, in which case we cannot use page
        flipping for DRI clients anyway
      Reviewed-by: default avatarAlex Deucher <alexander.deucher@amd.com>
      69e20839
  13. 22 Dec, 2017 1 commit
  14. 15 Nov, 2017 1 commit
  15. 08 Nov, 2017 1 commit
  16. 01 Nov, 2017 1 commit
  17. 20 Oct, 2017 6 commits
  18. 19 Oct, 2017 1 commit
  19. 05 Oct, 2017 2 commits
  20. 08 Sep, 2017 1 commit
  21. 31 Aug, 2017 1 commit
  22. 30 Aug, 2017 4 commits