1. 19 6月, 2009 1 次提交
  2. 12 6月, 2009 1 次提交
  3. 04 6月, 2009 1 次提交
  4. 03 4月, 2009 2 次提交
  5. 29 3月, 2009 2 次提交
    • M
      drm: detect hdmi monitor by hdmi identifier (v3) · f23c20c8
      Ma Ling 提交于
      Sometime we need to communicate with HDMI monitor by sending audio or video
      info frame, so we have to know monitor type. However if user utilize HDMI-DVI adapter to connect DVI monitor, hardware detection will incorrectly show the monitor is HDMI. HDMI spec tell us that any device containing IEEE registration Identifier will be treated as HDMI device.  The patch intends to detect HDMI monitor by this rule.
      Signed-off-by: NMa Ling <ling.ma@intel.com>
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      f23c20c8
    • M
      drm: read EDID extensions from monitor · 167f3a04
      Ma Ling 提交于
      Usually drm read basic EDID, that is enough for us, but since igital display
      were introduced i.e. HDMI monitor, sometime we need to interact with monitor by
      EDID extension information,
      
      EDID extensions include audio/video data block, speaker allocation and vendor specific data blocks.
      
      This patch intends to read EDID extensions from digital monitor for users.
      Signed-off-by: NMa Ling <ling.ma@intel.com>
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      167f3a04
  6. 25 2月, 2009 2 次提交
  7. 22 1月, 2009 1 次提交
  8. 29 12月, 2008 2 次提交
    • D
      drm: fix useless gcc unused variable warning · f890607b
      Dave Airlie 提交于
      the calling function doesn't call this function unless one of the two
      states that sets the value is true.
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      f890607b
    • D
      DRM: add mode setting support · f453ba04
      Dave Airlie 提交于
      Add mode setting support to the DRM layer.
      
      This is a fairly big chunk of work that allows DRM drivers to provide
      full output control and configuration capabilities to userspace.  It was
      motivated by several factors:
        - the fb layer's APIs aren't suited for anything but simple
          configurations
        - coordination between the fb layer, DRM layer, and various userspace
          drivers is poor to non-existent (radeonfb excepted)
        - user level mode setting drivers makes displaying panic & oops
          messages more difficult
        - suspend/resume of graphics state is possible in many more
          configurations with kernel level support
      
      This commit just adds the core DRM part of the mode setting APIs.
      Driver specific commits using these new structure and APIs will follow.
      
      Co-authors: Jesse Barnes <jbarnes@virtuousgeek.org>, Jakob Bornecrantz <jakob@tungstengraphics.com>
      Contributors: Alan Hourihane <alanh@tungstengraphics.com>, Maarten Maathuis <madman2003@gmail.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>
      f453ba04