1. 20 2月, 2009 1 次提交
  2. 22 1月, 2009 1 次提交
    • J
      drm: create mode_config idr lock · ad2563c2
      Jesse Barnes 提交于
      Create a separate mode_config IDR lock for simplicity.  The core DRM
      config structures (connector, mode, etc. lists) are still protected by
      the mode_config mutex, but the CRTC IDR (used for the various identifier
      IDs) is now protected by the mode_config idr_mutex.  Simplifies the
      locking a bit and removes a warning.
      
      All objects are protected by the config mutex, we may in the future,
      split the object further to have reference counts.
      Signed-off-by: NJesse Barnes <jbarnes@virtuousgeek.org>
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      ad2563c2
  3. 08 1月, 2009 1 次提交
  4. 29 12月, 2008 3 次提交
    • K
      drm: drop DRM_IOCTL_MODE_REPLACEFB, add+remove works just as well. · 0c7c2664
      Kristian H�gsberg 提交于
      The replace fb ioctl replaces the backing buffer object for a modesetting
      framebuffer object.  This can be acheived by just creating a new
      framebuffer backed by the new buffer object, setting that for the crtcs
      in question and then removing the old framebuffer object.
      Signed-off-by: NKristian Hogsberg <krh@redhat.com>
      Acked-by: NJakob Bornecrantz <jakob@vmware.com>
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      0c7c2664
    • J
      drm: sanitise drm modesetting API + remove unused hotplug · e0c8463a
      Jakob Bornecrantz 提交于
      The initially merged modesetting API has some uglies in it, this
      cleans up the struct members and ioctl ordering for initial submission.
      
      It also removes the unneeded hotplug infrastructure.
      
      airlied:- I've pulled this patch in from git modesetting-gem tree.
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      e0c8463a
    • 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