1. 30 8月, 2012 1 次提交
    • F
      gma500: Consider CRTC initially active. · 4a68a74b
      Forest Bond 提交于
      [this one ideally should make 3.6 - it fixes the very annoying mode setting bug]
      
      This causes the pipe to be forced off prior to initial mode set, which
      roughly mirrors the behavior of the i915 driver.  It fixes initial mode
      setting on my Intel DN2800MT (Cedarview) board.  Without it, mode
      setting triggers an out-of-range error from the monitor for most modes,
      but only on initial configuration (i.e. they can be configured
      successfully from userspace after that).
      Signed-off-by: NForest Bond <forest.bond@rapidrollout.com>
      Signed-off-by: NAlan Cox <alan@linux.intel.com>
      Cc: stable <stable@vger.kernel.org>
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      4a68a74b
  2. 20 7月, 2012 1 次提交
  3. 22 5月, 2012 1 次提交
  4. 12 5月, 2012 2 次提交
  5. 10 3月, 2012 5 次提交
  6. 20 12月, 2011 4 次提交
  7. 16 11月, 2011 1 次提交
    • A
      gma500: Add Poulsbo support · 89c78134
      Alan Cox 提交于
      This provides the specific code for Poulsbo, some of which is also used for
      the later chipsets. We support the GTT, the 2D engine (for console), and
      the display setup/management. We do not support 3D or the video overlays.
      
      In theory enough public info is available to do the video overlay work
      but that represents a large task.
      
      Framebuffer X will run nicely with this but do *NOT* use the VESA X
      server at the same time as KMS. With a Dell mini 10 things like Xfce4 are
      nice and usable even when compositing as the CPU has a good path to the
      memory.
      Signed-off-by: NAlan Cox <alan@linux.intel.com>
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      89c78134
  8. 27 8月, 2011 1 次提交
  9. 25 7月, 2011 1 次提交
  10. 16 7月, 2011 1 次提交
  11. 05 7月, 2011 10 次提交
  12. 29 6月, 2011 1 次提交
  13. 18 5月, 2011 1 次提交
    • A
      gma500: finish off the fault handler · 7ed2911c
      Alan Cox 提交于
      GEM wants to mmap the object through the GTT (which avoids aliasing) so we
      need to put the object into the GTT before we provide the fault mapping for
      it.
      
      While we are at it update the pin interface so that it digs dev out of the
      GEM object itself. This provides a rather cleaner API and call environment.
      Fix th refcount/on-off confusion in the pin API.
      
      At this point we get a bit further with modetest but if we write to the
      new GEM mapping we hang solid and as yet I don't know why.
      Signed-off-by: NAlan Cox <alan@linux.intel.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      7ed2911c
  14. 26 4月, 2011 5 次提交
  15. 06 4月, 2011 4 次提交
  16. 24 2月, 2011 1 次提交
    • A
      staging: gma500: Intel GMA500 staging driver · 0867b421
      Alan Cox 提交于
      This is an initial staging driver for the GMA500. It's been stripped out
      of the PVR drivers and crunched together from various bits of code and
      different kernels.
      
      Currently it's unaccelerated but still pretty snappy even compositing with
      the frame buffer X server.
      
      Lots of work is needed to rework the ttm and bo interfaces from being
      ripped out and then 2D acceleration wants putting back for framebuffer and
      somehow eventually via DRM.
      
      There is no support for the parts without open source userspace (video
      accelerators, 3D) as per kernel policy.
      Signed-off-by: NAlan Cox <alan@linux.intel.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      0867b421