1. 23 Mar, 2017 1 commit
  2. 27 Jul, 2016 1 commit
  3. 04 May, 2016 1 commit
  4. 28 Mar, 2016 1 commit
  5. 09 Mar, 2016 1 commit
    • Michel Dänzer's avatar
      xfree86: Re-set current cursor after RandR 1.2 CRTC configuration change · b04767c8
      Michel Dänzer authored
      Add xf86CursorResetCursor, which allows switching between HW and SW
      cursor depending on the current state.
      
      Call it from xf86DisableUnusedFunctions, which is called after any CRTC
      configuration change such as setting a mode or disabling a CRTC. This
      makes sure that SW cursor is used e.g. while a transform is in use on
      any CRTC or while there are active PRIME output slaves, and enables HW
      cursor again once none of those conditions are true anymore.
      Reviewed-by: Keith Packard's avatarKeith Packard <keithp@keithp.com>
      b04767c8
  6. 27 Apr, 2015 2 commits
  7. 21 Apr, 2015 1 commit
  8. 31 Mar, 2015 1 commit
  9. 12 Nov, 2014 1 commit
  10. 23 Jan, 2014 1 commit
  11. 12 Jan, 2014 1 commit
  12. 07 Jan, 2014 1 commit
    • Damien Lespiau's avatar
      xfree86: Use the TMDS maximum frequency to prune modes · d6c8d750
      Damien Lespiau authored
      Instead of only relying on the Range section, we can do better on
      HDMI to find out what is the max dot clock the monitor supports. The
      HDMI CEA vendor block adds a TMDS max freq we can use.
      
      This makes X not prune 4k resolutions on HDMI.
      
      v2: Replace X_INFO by X_PROBED in the message that prints the max
          TMDS frequency (Chris Wilson)
      
      Reviewed-by: Chris Wilson <chris at chris-wilson.co.uk>
      Signed-off-by: default avatarDamien Lespiau <damien.lespiau@intel.com>
      d6c8d750
  13. 14 Nov, 2013 1 commit
  14. 01 Nov, 2013 1 commit
  15. 05 May, 2013 1 commit
  16. 30 Apr, 2013 1 commit
    • Dave Airlie's avatar
      xf86crtc: don't use scrn->display for gpu screens · 16077b81
      Dave Airlie authored
      scrn->display is a property of the main screen really, and we don't
      want to have the GPU screens use it for anything when picking modes
      or a front buffer size.
      
      This fixes a bug where when you plugged a display link device, it
      would try and allocate a screen the same size as the current running
      one (3360x1050 in this case), which was too big for the device. Avoid
      doing this and just pick sizes based on whats plugged into this device.
      Reviewed-by: Keith Packard's avatarKeith Packard <keithp@keithp.com>
      Signed-off-by: default avatarDave Airlie <airlied@redhat.com>
      16077b81
  17. 29 Apr, 2013 1 commit
  18. 26 Mar, 2013 1 commit
  19. 01 Mar, 2013 2 commits
  20. 09 Jan, 2013 1 commit
  21. 28 Nov, 2012 1 commit
  22. 19 Sep, 2012 1 commit
  23. 04 Sep, 2012 1 commit
  24. 15 Aug, 2012 1 commit
  25. 06 Aug, 2012 2 commits
  26. 11 Jul, 2012 1 commit
    • Maarten Lankhorst's avatar
      xfree86: Strip dangling pointers from desiredMode · deb08658
      Maarten Lankhorst authored
      Based on the original patch by Chris Wilson, which was a better fix than mine.
      
      We stash a copy of the desiredMode on the crtc so that we can restore it
      after a vt switch. This copy is a simple memcpy and so also stashes a
      references to the pointers contained within the desiredMode. Those
      pointers are freed the next time the outputs are probed and mode list
      rebuilt, resulting in us chasing those dangling pointers on the next
      mode switch.
      
      ==22787== Invalid read of size 1
      ==22787==    at 0x40293C2: __GI_strlen (in
      /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
      ==22787==    by 0x668F875: strdup (strdup.c:42)
      ==22787==    by 0x5DBA00: XNFstrdup (utils.c:1124)
      ==22787==    by 0x4D72ED: xf86DuplicateMode (xf86Modes.c:209)
      ==22787==    by 0x4CA848: xf86CrtcSetModeTransform (xf86Crtc.c:276)
      ==22787==    by 0x4D05B4: xf86SetDesiredModes (xf86Crtc.c:2677)
      ==22787==    by 0xA7479D0: sna_create_screen_resources
      (sna_driver.c:220)
      ==22787==    by 0x4CB914: xf86CrtcCreateScreenResources (xf86Crtc.c:725)
      ==22787==    by 0x425498: main (main.c:216)
      ==22787==  Address 0x72c60e0 is 0 bytes inside a block of size 9 free'd
      ==22787==    at 0x4027AAE: free (in
      /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
      ==22787==    by 0x4A547E: xf86DeleteMode (xf86Mode.c:1984)
      ==22787==    by 0x4CD84F: xf86ProbeOutputModes (xf86Crtc.c:1578)
      ==22787==    by 0x4DC405: xf86RandR12GetInfo12 (xf86RandR12.c:1537)
      ==22787==    by 0x518119: RRGetInfo (rrinfo.c:202)
      ==22787==    by 0x51D997: rrGetScreenResources (rrscreen.c:335)
      ==22787==    by 0x51E0D0: ProcRRGetScreenResources (rrscreen.c:475)
      ==22787==    by 0x513852: ProcRRDispatch (randr.c:493)
      ==22787==    by 0x4346DB: Dispatch (dispatch.c:439)
      ==22787==    by 0x4256E4: main (main.c:287)
      Signed-off-by: default avatarMaarten Lankhorst <maarten.lankhorst@canonical.com>
      Reported-by: zkabelac's avatarZdenek Kabelac <zdenek.kabelac@gmail.com>
      Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=36108Reviewed-by: Chris Wilson's avatarChris Wilson <chris@chris-wilson.co.uk>
      Signed-off-by: Keith Packard's avatarKeith Packard <keithp@keithp.com>
      deb08658
  27. 07 Jul, 2012 5 commits
  28. 06 Jul, 2012 1 commit
  29. 05 Jun, 2012 1 commit
  30. 21 May, 2012 1 commit
  31. 06 Apr, 2012 1 commit
  32. 21 Mar, 2012 1 commit
    • Keith Packard's avatar
      Introduce a consistent coding style · 9838b703
      Keith Packard authored
      This is strictly the application of the script 'x-indent-all.sh'
      from util/modular. Compared to the patch that Daniel posted in
      January, I've added a few indent flags:
      
      	-bap
      	-psl
      	-T PrivatePtr
      	-T pmWait
      	-T _XFUNCPROTOBEGIN
      	-T _XFUNCPROTOEND
      	-T _X_EXPORT
      
      The typedefs were needed to make the output of sdksyms.sh match the
      previous output, otherwise, the code is formatted badly enough that
      sdksyms.sh generates incorrect output.
      
      The generated code was compared with the previous version and found to
      be essentially identical -- "assert" line numbers and BUILD_TIME were
      the only differences found.
      
      The comparison was done with this script:
      
      dir1=$1
      dir2=$2
      
      for dir in $dir1 $dir2; do
      	(cd $dir && find . -name '*.o' | while read file; do
      		dir=`dirname $file`
      		base=`basename $file .o`
      		dump=$dir/$base.dump
      		objdump -d $file > $dump
      	done)
      done
      
      find $dir1 -name '*.dump' | while read dump; do
      	otherdump=`echo $dump | sed "s;$dir1;$dir2;"`
      	diff -u $dump $otherdump
      done
      Signed-off-by: Keith Packard's avatarKeith Packard <keithp@keithp.com>
      Acked-by: Daniel Stone's avatarDaniel Stone <daniel@fooishbar.org>
      Acked-by: Alan Coopersmith's avatarAlan Coopersmith <alan.coopersmith@oracle.com>
      9838b703
  33. 23 Nov, 2011 1 commit