1. 11 Oct, 2019 1 commit
  2. 19 Mar, 2019 1 commit
  3. 06 Mar, 2019 1 commit
  4. 20 Sep, 2018 1 commit
  5. 14 Sep, 2018 1 commit
  6. 24 Aug, 2018 1 commit
  7. 18 Jul, 2018 1 commit
  8. 10 Jul, 2018 1 commit
  9. 06 Jul, 2018 1 commit
  10. 18 Apr, 2018 1 commit
  11. 15 Mar, 2018 1 commit
  12. 02 Mar, 2018 1 commit
  13. 01 Mar, 2018 1 commit
  14. 22 Jan, 2018 1 commit
  15. 05 Oct, 2017 1 commit
  16. 08 Sep, 2017 1 commit
  17. 31 Aug, 2017 1 commit
  18. 22 Aug, 2017 1 commit
    • Martin Peres's avatar
      modesetting: re-set the crtc's mode when link-status goes BAD · 0de05767
      Martin Peres authored
      Despite all the careful planning of the kernel, a link may become
      insufficient to handle the currently-set mode. At this point, the
      kernel should mark this particular configuration as being broken
      and potentially prune the mode before setting the offending connector's
      link-status to BAD and send the userspace a hotplug event. This may
      happen right after a modeset or later on.
      
      Upon receiving a hot-plug event, we iterate through the connectors to
      re-apply the currently-set mode on all the connectors that have a
      link-status property set to BAD. The kernel may be able to get the
      link to work by dropping to using a lower link bpp (with the same
      display bpp). However, the modeset may fail if the kernel has pruned
      the mode, so to make users aware of this problem a warning is outputed
      in the logs to warn about having a potentially-black display.
      
      This patch does not modify the current behaviour of always propagating
      the events to the randr clients. This allows desktop environments to
      re-probe the connectors and select a new resolution based on the new
      (currated) mode list if a mode disapeared. This behaviour is expected in
      order to pass the Display Port compliance tests.
      
      (Ported from xserver commit bcee1b76aa0db8525b491485e90b8740763d7de6)
      
      [ Michel: Bump libdrm dependency to >= 2.4.78 for
        DRM_MODE_LINK_STATUS_BAD ]
      (Ported from radeon commit 0472a605e0ec8fec1892bbc3a84698b7ef9c5296)
      Acked-by: Harry Wentland's avatarHarry Wentland <harry.wentland@amd.com>
      Reviewed-by: default avatarAlex Deucher <alexander.deucher@amd.com>
      0de05767
  19. 27 Jul, 2017 1 commit
  20. 24 May, 2017 1 commit
  21. 23 Mar, 2017 1 commit
  22. 16 Mar, 2017 1 commit
  23. 07 Mar, 2017 2 commits
  24. 28 Nov, 2016 1 commit
  25. 21 Nov, 2016 2 commits
  26. 17 Nov, 2016 1 commit
  27. 02 Nov, 2016 1 commit
  28. 25 Oct, 2016 1 commit
  29. 20 Sep, 2016 1 commit
  30. 16 Sep, 2016 1 commit
    • Michel Dänzer's avatar
      Fix handling of configure option --with-xorg-conf-dir · aa8a3fa2
      Michel Dänzer authored
      There were two problems:
      
      I accidentally changed the variable name in the AC_ARG_WITH stanza from
      configdir to xorgconfigdir, so specifying --with-xorg-conf-dir wouldn't
      work correctly. Fix this back to configdir.
      
      If neither --with-xorg-conf-dir nor --prefix is specified on the command
      line, the $prefix variable doesn't contain "/usr/local" (the default
      prefix) yet at this point but "NONE". So make install would attempt to
      install 10-amdgpu.conf in ${DESTDIR}NONE/share/X11/xorg.conf.d/ . Fix
      this by leaving ${prefix} verbatim in the default value, to be resolved
      by make.
      
      Also print the configdir value along with the values of other similar
      configuration variables.
      Reported-by: Timo Aaltonen's avatarTimo Aaltonen <tjaalton@debian.org>
      Reviewed-by: Julien Cristau's avatarJulien Cristau <jcristau@debian.org>
      aa8a3fa2
  31. 14 Sep, 2016 1 commit
    • Michel Dänzer's avatar
      Use --with-xorg-conf-dir=$prefix/share/X11/xorg.conf.d by default · cd3acb75
      Michel Dänzer authored
      We were using the result of `pkg-config --variable=sysconfigdir
      xorg-server` before, which may not be inside $prefix, so make install
      might fail for 10-amdgpu.conf .
      
      Fixes make distcheck in that case, and possibly also 10-amdgpu.conf
      seemingly missing from some distribution packages.
      
      This matches what some (though not all) input drivers are doing for their
      xorg.conf.d snippets.
      cd3acb75
  32. 11 Apr, 2016 1 commit
  33. 07 Apr, 2016 1 commit
  34. 25 Mar, 2016 3 commits
  35. 20 Nov, 2015 2 commits