1. 21 Jun, 2017 3 commits
  2. 22 Apr, 2017 3 commits
  3. 21 Apr, 2017 3 commits
  4. 20 Apr, 2017 3 commits
  5. 03 Apr, 2017 1 commit
  6. 30 Mar, 2017 1 commit
  7. 15 Mar, 2017 2 commits
  8. 13 Mar, 2017 3 commits
  9. 11 Mar, 2017 1 commit
  10. 09 Mar, 2017 2 commits
    • Sven Joachim's avatar
      Document the cherry-pick · c6494a85
      Sven Joachim authored
      c6494a85
    • Lyude's avatar
      Consider CRTCs disabled when DPMS is off · 64792216
      Lyude authored
      It turns out there's a difference in X between a CRTC being "disabled"
      and simply having it's DPMS turned off. This is problematic though,
      because if DPMS is turned off you can't really use the CRTC as a normal
      CRTC anyway since page flipping and vblanks will be non-functional. As a
      result, we've been considering DPMS-on CRTCs as enabled and attempt to
      perform pageflips, vblank waits, etc. on them which inevitably fails. and
      usually breaks the display the first time any of the CRTCs have their
      DPMS turned on.
      
      This was a problem that didn't really show itself until kernel 4.10 when
      atomic modesetting was added which caused nouveau to stop trying to
      fulfill pageflips and vblank waits on disabled CRTCs. I'm not sure how
      pageflipping disabled CRTCs ever worked in the first place, but since
      not doing so is the proper behavior anyway I haven't investigated any
      further.
      
      So, copy the ms_crtc_on() function from the modesetting driver and add
      it here as drmmode_crtc_on(), then use that in all of the places where
      we should be checking for both DPMS off and disabled CRTCs.
      
      This fixes issues with the X ceasing to function (usually) after the
      first time a CRTC has it's DPMS turned on. Reproduction recipe:
      
      - Load up gnome-shell on a machine
      - Wait for the display to timeout from inactivity and turn itself off
      - Shake the cursor or press something on the keyboard. Chances are the
        monitor will come back on, but the display remains black until the
        next time the X server is restarted.
      Signed-off-by: 's avatarLyude <lyude@redhat.com>
      Reviewed-by: 's avatarAdam Jackson <ajax@redhat.com>
      (cherry picked from commit 92408393)
      64792216
  11. 07 Mar, 2017 2 commits
    • Lyude's avatar
      Bump version to 1.0.14 · b71de83b
      Lyude authored
      Signed-off-by: 's avatarLyude <lyude@redhat.com>
      b71de83b
    • Lyude's avatar
      Consider CRTCs disabled when DPMS is off · 92408393
      Lyude authored
      It turns out there's a difference in X between a CRTC being "disabled"
      and simply having it's DPMS turned off. This is problematic though,
      because if DPMS is turned off you can't really use the CRTC as a normal
      CRTC anyway since page flipping and vblanks will be non-functional. As a
      result, we've been considering DPMS-on CRTCs as enabled and attempt to
      perform pageflips, vblank waits, etc. on them which inevitably fails. and
      usually breaks the display the first time any of the CRTCs have their
      DPMS turned on.
      
      This was a problem that didn't really show itself until kernel 4.10 when
      atomic modesetting was added which caused nouveau to stop trying to
      fulfill pageflips and vblank waits on disabled CRTCs. I'm not sure how
      pageflipping disabled CRTCs ever worked in the first place, but since
      not doing so is the proper behavior anyway I haven't investigated any
      further.
      
      So, copy the ms_crtc_on() function from the modesetting driver and add
      it here as drmmode_crtc_on(), then use that in all of the places where
      we should be checking for both DPMS off and disabled CRTCs.
      
      This fixes issues with the X ceasing to function (usually) after the
      first time a CRTC has it's DPMS turned on. Reproduction recipe:
      
      - Load up gnome-shell on a machine
      - Wait for the display to timeout from inactivity and turn itself off
      - Shake the cursor or press something on the keyboard. Chances are the
        monitor will come back on, but the display remains black until the
        next time the X server is restarted.
      Signed-off-by: 's avatarLyude <lyude@redhat.com>
      Reviewed-by: 's avatarAdam Jackson <ajax@redhat.com>
      92408393
  12. 28 Oct, 2016 7 commits
  13. 24 Sep, 2016 1 commit
  14. 23 Sep, 2016 3 commits
  15. 20 Sep, 2016 1 commit
    • Ilia Mirkin's avatar
      Bump version to 1.0.13 · e6479845
      Ilia Mirkin authored
       - Fixes for reverse prime offload
       - ABI 23 support for Xorg 1.19
      
      Signed-off-by: Ilia Mirkin <imirkin@alum.mit.edu
      e6479845
  16. 19 Jul, 2016 2 commits
  17. 27 Jun, 2016 1 commit
    • Hans de Goede's avatar
      Properly cleanup fb for reverse-prime-offload · 12f77348
      Hans de Goede authored
      drmmode_set_scanout_pixmap(pix) adds drmmod->fb_id through a call
      to drmmode_xf86crtc_resize(), but on a subsequent
      drmmode_set_scanout_pixmap(NULL) it would not remove the fb.
      
      This keeps the crtc marked as busy, which causes the dgpu to not
      being able to runtime suspend, after an output attached to the dgpu
      has been used once. Which causes burning through an additional 10W
      of power and the laptop to run quite hot.
      
      This commit adds the missing remove fb call, allowing the dgpu to runtime
      suspend after an external monitor has been plugged into the laptop.
      Signed-off-by: 's avatarHans de Goede <hdegoede@redhat.com>
      Signed-off-by: 's avatarBen Skeggs <bskeggs@redhat.com>
      12f77348
  18. 04 Jun, 2016 1 commit