1. 11 9月, 2009 3 次提交
  2. 25 8月, 2009 1 次提交
  3. 19 8月, 2009 1 次提交
    • J
      drm: clarify scaling property names · 53bd8389
      Jesse Barnes 提交于
      Now that we're using the scaling property in the Intel driver I noticed
      that the names were a bit confusing.  I've corrected them according to
      our discussion on IRC and the mailing list, though I've left out
      potential new additions for a new scaling property with an integer (or
      two) for the scaling factor.  None of the drivers implement that today,
      but if someone wants to do it, I think it could be done with the
      addition of a single new type and a new property to describe the
      scaling factor in the X and Y directions.
      Signed-off-by: NJesse Barnes <jbarnes@virtuousgeek.org>
      Acked-by: NAlex Deucher <alexdeucher@gmail.com>
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      53bd8389
  4. 04 8月, 2009 1 次提交
  5. 30 7月, 2009 1 次提交
  6. 14 7月, 2009 1 次提交
  7. 10 7月, 2009 1 次提交
  8. 02 7月, 2009 1 次提交
  9. 23 6月, 2009 2 次提交
  10. 19 6月, 2009 1 次提交
  11. 11 6月, 2009 1 次提交
  12. 10 6月, 2009 1 次提交
  13. 05 6月, 2009 2 次提交
  14. 04 6月, 2009 2 次提交
  15. 23 5月, 2009 1 次提交
  16. 15 5月, 2009 1 次提交
    • J
      drm/i915: ignore LVDS on intel graphics systems that lie about having it · 425d244c
      Jarod Wilson 提交于
      There are a number of small form factor desktop systems with Intel mobile
      graphics chips that lie and say they have an LVDS. With kernel mode-setting,
      this becomes a problem, and makes native resolution boot go haywire -- for
      example, my Dell Studio Hybrid, hooked to a 1920x1080 display claims to
      have a 1024x768 LVDS, and the resulting graphical boot on the 1920x1080
      display uses only the top left 1024x768, and auto-configured X will end
      up only 1024x768 as well. With this change, graphical boot and X
      both do 1920x1080 as expected.
      
      Note that we're simply embracing and extending the early bail-out code
      in place for the Mac Mini here. The xorg intel driver uses pci subsystem
      device and vendor id for matching, while we're using dmi lookups here.
      The MSI addition is courtesy of and tested by Bill Nottingham.
      Signed-off-by: NJarod Wilson <jarod@redhat.com>
      Tested-by: NBill Nottingham <notting@redhat.com>
      Signed-off-by: NEric Anholt <eric@anholt.net>
      425d244c
  17. 28 3月, 2009 1 次提交
  18. 20 2月, 2009 1 次提交
  19. 08 2月, 2009 1 次提交
  20. 03 2月, 2009 1 次提交
  21. 30 1月, 2009 1 次提交
  22. 22 1月, 2009 1 次提交
  23. 16 1月, 2009 1 次提交
  24. 29 12月, 2008 1 次提交
    • J
      DRM: i915: add mode setting support · 79e53945
      Jesse Barnes 提交于
      This commit adds i915 driver support for the DRM mode setting APIs.
      Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
      supported.  HDMI, DisplayPort and additional SDVO output support will
      follow.
      
      Support for the mode setting code is controlled by the new 'modeset'
      module option.  A new config option, CONFIG_DRM_I915_KMS controls the
      default behavior, and whether a PCI ID list is built into the module for
      use by user level module utilities.
      
      Note that if mode setting is enabled, user level drivers that access
      display registers directly or that don't use the kernel graphics memory
      manager will likely corrupt kernel graphics memory, disrupt output
      configuration (possibly leading to hangs and/or blank displays), and
      prevent panic/oops messages from appearing.  So use caution when
      enabling this code; be sure your user level code supports the new
      interfaces.
      
      A new SysRq key, 'g', provides emergency support for switching back to
      the kernel's framebuffer console; which is useful for testing.
      
      Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
      Signed-off-by: NJesse Barnes <jbarnes@virtuousgeek.org>
      Signed-off-by: NEric Anholt <eric@anholt.net>
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      79e53945