1. 10 8月, 2010 1 次提交
  2. 18 5月, 2010 1 次提交
    • D
      drm_edid: There should be 6 Standard Timings · 96525a2f
      Dan Carpenter 提交于
      Smatch complained that we initialize 6 elements in add_detailed_modes()
      but the timings[] array is declared with 5 elements.  Adam Jackson
      verified that 6 is the correct number of timings.
      
      On Mon, May 10, 2010 at 12:08:24PM -0400, Adam Jackson wrote:
      > > >                 struct std_timing timings[5];
      > > >                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
      >
      > This decl is wrong, should be 6.  From the 1.4 spec:
      >
      > "Six additional Standard Timings may be listed as a display descriptor
      > (tag #FAh)."
      >
      > The 1.3 spec is a little less explicit about it, but does show 6
      > standard timing codes in the 0xFA detailed subblock, terminated by 0x0A
      > in the 18th byte.  I don't have the docs for 1.2 or earlier, but we're
      > paranoid enough about not adding broken timings that we should be fine.
      
      This patch is basically a clean up, because timings[] is declared inside
      a union and increasing the number of elements here doesn't change the
      overall size of the union.
      Signed-off-by: NDan Carpenter <error27@gmail.com>
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      96525a2f
  3. 06 4月, 2010 1 次提交
  4. 09 2月, 2010 1 次提交
  5. 04 12月, 2009 2 次提交
  6. 24 6月, 2009 1 次提交
  7. 19 6月, 2009 1 次提交
  8. 11 3月, 2009 1 次提交
  9. 25 2月, 2009 1 次提交
  10. 29 12月, 2008 1 次提交
    • 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