1. 24 Nov, 2008 3 commits
  2. 13 Nov, 2008 2 commits
  3. 04 Nov, 2008 1 commit
    • Egbert Eich's avatar
      DDX/RandR: When positioning outputs assume width/height = 0 if no modes exist. · 9a874a71
      Egbert Eich authored
      When a user specifies the position of an output for which no modes exist
      (for whatever reason) assume that the width and height of this output
      is 0. The result will be the same as if this output isn't taken into
      consideration at all and thus should be sane. It will prevent a segfault
      when trying to determine the width and height of a non-existent mode.
      9a874a71
  4. 08 Oct, 2008 1 commit
  5. 31 Aug, 2008 1 commit
  6. 25 Aug, 2008 2 commits
  7. 03 Jul, 2008 2 commits
  8. 30 Jun, 2008 1 commit
  9. 12 Jun, 2008 1 commit
  10. 20 May, 2008 1 commit
  11. 19 May, 2008 2 commits
  12. 16 May, 2008 4 commits
  13. 17 Mar, 2008 2 commits
    • Jesse Barnes's avatar
      Cleanup logic in xf86PrepareOutputs · afd74286
      Jesse Barnes authored
      Should have done this in the first place.  Since we're checking for the absence
      of the get_crtc callback in the first place, we'll short circuit the later call
      and disable the output, so the ugly "continue" block is unnecesary.
      afd74286
    • Jesse Barnes's avatar
      Make xf86SetDesiredModes aware of current output configuration · ba85caac
      Jesse Barnes authored
      By adding a new output callback, ->get_crtc, xf86SetDesiredModes is able to
      avoid turning off outputs & CRTCs if the current output<->CRTC mappings are the
      same as the desired configuration.  This helps avoid flickering displays at
      startup time, which speeds things up a little and looks better.
      ba85caac
  14. 14 Mar, 2008 1 commit
  15. 12 Mar, 2008 1 commit
  16. 07 Mar, 2008 1 commit
  17. 04 Mar, 2008 1 commit
    • Adam Jackson's avatar
      Make xf86InitialConfiguration slightly smarter. · 27e7dacb
      Adam Jackson authored
      Old heuristic was to find the first monitor that expressed a preference,
      then attempt to get all other monitors to agree.  This doesn't work
      particularly well when the two sets of modes don't precisely intersect,
      you get overlapping-but-not-identical output geometry and things go wrong.
      
      New heuristic is:
      - Exact user preference, if given
      - Exact output preference, if the same for all outputs
      - Best (largest) mode of modes common to all outputs:
        - with the same aspect ratio as all outputs (may be NULL)
        - with 4:3 aspect ratio
      - Then the old heuristic to try to get something lit
      
      Note that it is simply not doable to have a reliable initial output guess if
      you insist on trying to clone all outputs together.  It's far too easy to
      end up with displays that simply don't have modes in common.  We need to
      switch to right-of placement someday, once we're not limited to CRTC size
      limits and we have working multi-GPU in RANDR.
      27e7dacb
  18. 03 Mar, 2008 1 commit
  19. 26 Feb, 2008 1 commit
  20. 05 Feb, 2008 2 commits
    • liuhong's avatar
      validate mode clock for probed modes · d3c36fe7
      liuhong authored
      Some modes claimed in monitor EDID data may not be supported by
      the monitor. So also validating the max clock for probed modes.
      d3c36fe7
    • liuhong's avatar
      fix max clock unit · 4b5b6e7b
      liuhong authored
      max clock from EDID data is in MHz, while we need KHz to validate modes.
      4b5b6e7b
  21. 28 Dec, 2007 1 commit
  22. 04 Dec, 2007 2 commits
  23. 27 Nov, 2007 1 commit
  24. 23 Nov, 2007 3 commits
  25. 19 Nov, 2007 1 commit
  26. 18 Nov, 2007 1 commit