This project is mirrored from https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git. Pull mirroring updated .
  1. 01 Nov, 2011 1 commit
  2. 31 Mar, 2011 1 commit
  3. 07 Feb, 2011 1 commit
    • Dave Airlie's avatar
      drm: dumb scanout create/mmap for intel/radeon (v3) · ff72145b
      Dave Airlie authored
      
      
      This is just an idea that might or might not be a good idea,
      it basically adds two ioctls to create a dumb and map a dumb buffer
      suitable for scanout. The handle can be passed to the KMS ioctls to create
      a framebuffer.
      
      It looks to me like it would be useful in the following cases:
      a) in development drivers - we can always provide a shadowfb fallback.
      b) libkms users - we can clean up libkms a lot and avoid linking
      to libdrm_*.
      c) plymouth via libkms is a lot easier.
      
      Userspace bits would be just calls + mmaps. We could probably
      mark these handles somehow as not being suitable for acceleartion
      so as top stop people who are dumber than dumb.
      
      Signed-off-by: default avatarDave Airlie <airlied@redhat.com>
      ff72145b
  4. 21 Jul, 2010 1 commit
    • Ben Skeggs's avatar
      drm: add "auto" dithering method · 92897b5c
      Ben Skeggs authored
      
      
      There's no convenient/reliable way for drivers to both obey the dithering
      mode property, and to be able to attempt to provide a good default in all
      cases.
      
      This commit adds an "auto" method to the property which drivers can default
      to if they wish, whilst still allowing the user to override the choice as
      they do now.
      
      Signed-off-by: default avatarBen Skeggs <bskeggs@redhat.com>
      Signed-off-by: default avatarDave Airlie <airlied@redhat.com>
      92897b5c
  5. 01 Feb, 2010 1 commit
  6. 08 Jan, 2010 1 commit
  7. 03 Dec, 2009 2 commits
  8. 18 Nov, 2009 1 commit
  9. 19 Aug, 2009 1 commit
    • Jesse Barnes's avatar
      drm: clarify scaling property names · 53bd8389
      Jesse Barnes authored
      
      
      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: default avatarJesse Barnes <jbarnes@virtuousgeek.org>
      Acked-by: default avatarAlex Deucher <alexdeucher@gmail.com>
      Signed-off-by: default avatarDave Airlie <airlied@redhat.com>
      53bd8389
  10. 04 Aug, 2009 2 commits
  11. 26 Mar, 2009 1 commit
  12. 29 Dec, 2008 2 commits
    • Jakob Bornecrantz's avatar
      drm: sanitise drm modesetting API + remove unused hotplug · e0c8463a
      Jakob Bornecrantz authored
      
      
      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: default avatarDave Airlie <airlied@redhat.com>
      e0c8463a
    • Dave Airlie's avatar
      DRM: add mode setting support · f453ba04
      Dave Airlie authored
      
      
      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: default avatarJesse Barnes <jbarnes@virtuousgeek.org>
      Signed-off-by: default avatarEric Anholt <eric@anholt.net>
      Signed-off-by: default avatarDave Airlie <airlied@redhat.com>
      f453ba04