1. 22 9月, 2011 1 次提交
  2. 05 8月, 2011 1 次提交
  3. 04 8月, 2011 1 次提交
  4. 14 7月, 2011 3 次提交
  5. 12 7月, 2011 1 次提交
  6. 09 7月, 2011 1 次提交
  7. 08 7月, 2011 1 次提交
  8. 30 6月, 2011 2 次提交
  9. 29 6月, 2011 1 次提交
    • B
      drm/i915: forcewake fix after reset · 25732821
      Ben Widawsky 提交于
      The failure is as follows:
      
      1. Userspace gets forcewake lock, lock count >=1
      2. GPU hang/reset occurs (forcewake bit is reset)
      3. count is now incorrect
      
      The failure can only occur when using the forcewake userspace lock.
      
      This has the unfortunate consequence of messing up the driver as well as
      userspace, unless userspace closes the debugfs file, the kernel will
      never end up waking the GT since the refcount will be > 1.
      
      The solution is to try to recover the correct forcewake state based on
      the refcount. There is a period of time where userspace reads/writes may
      occur after the reset, before the GT has been forcewaked. The interface
      was never designed to be a perfect solution for userspace reads/writes,
      and the kernel portion is fixed by this patch.
      Suggested-by: NChris Wilson <chris@chris-wilson.co.uk>
      Signed-off-by: NBen Widawsky <ben@bwidawsk.net>
      Signed-off-by: NKeith Packard <keithp@keithp.com>
      25732821
  10. 18 5月, 2011 2 次提交
  11. 16 5月, 2011 1 次提交
  12. 14 5月, 2011 4 次提交
  13. 11 5月, 2011 1 次提交
  14. 07 3月, 2011 1 次提交
  15. 06 3月, 2011 1 次提交
  16. 22 2月, 2011 1 次提交
  17. 10 2月, 2011 1 次提交
  18. 07 2月, 2011 2 次提交
    • D
      drm: rework PCI/platform driver interface. · 8410ea3b
      Dave Airlie 提交于
      This abstracts the pci/platform interface out a step further,
      we can go further but this is far enough for now to allow USB
      to be plugged in.
      
      The drivers now just call the init code directly for their
      device type.
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      8410ea3b
    • D
      drm: dumb scanout create/mmap for intel/radeon (v3) · ff72145b
      Dave Airlie 提交于
      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: NDave Airlie <airlied@redhat.com>
      ff72145b
  19. 02 2月, 2011 1 次提交
  20. 01 2月, 2011 1 次提交
  21. 26 1月, 2011 1 次提交
  22. 25 1月, 2011 1 次提交
  23. 23 1月, 2011 1 次提交
    • C
      drm/i915: Recognise non-VGA display devices · 934f992c
      Chris Wilson 提交于
      Starting with SandyBridge (though possible with earlier hacked BIOSes),
      the BIOS may initialise the IGFX as secondary to a discrete GPU. Prior,
      it would simply disable the integrated GPU. So we adjust our PCI class
      mask to match any DISPLAY_CLASS device.
      
      In such a configuration, the IGFX is not a primary VGA controller and
      so should not take part in VGA arbitration, and the error return from
      vga_client_register() is expected.
      Signed-off-by: NChris Wilson <chris@chris-wilson.co.uk>
      Cc: stable@kernel.org
      934f992c
  24. 19 1月, 2011 1 次提交
  25. 14 1月, 2011 1 次提交
  26. 12 1月, 2011 3 次提交
  27. 05 1月, 2011 1 次提交
  28. 17 12月, 2010 1 次提交
    • M
      drm/i915: Add support for precise vblank timestamping (v2) · 0af7e4df
      Mario Kleiner 提交于
      v2: Change IS_IRONLAKE to IS_GEN5 to adapt to 2.6.37
      
      This patch adds new functions for use by the drm core:
      
      .get_vblank_timestamp() provides a precise timestamp
      for the end of the most recent (or current) vblank
      interval of a given crtc, as needed for the DRI2
      implementation of the OML_sync_control extension.
      It is a thin wrapper around the drm function
      drm_calc_vbltimestamp_from_scanoutpos() which does
      almost all the work.
      
      .get_scanout_position() provides the current horizontal
      and vertical video scanout position and "in vblank"
      status of a given crtc, as needed by the drm for use by
      drm_calc_vbltimestamp_from_scanoutpos().
      
      The patch modifies the pageflip completion routine
      to use these precise vblank timestamps as the timestamps
      for pageflip completion events.
      
      This code has been only tested on a HP-Mini Netbook with
      Atom processor and Intel 945GME gpu. The codepath for
      (IS_G4X(dev) || IS_GEN5(dev) || IS_GEN6(dev)) gpu's
      has not been tested so far due to lack of hardware.
      Signed-off-by: NMario Kleiner <mario.kleiner@tuebingen.mpg.de>
      Acked-by: NJesse Barnes <jbarnes@virtuousgeek.org>
      Signed-off-by: NChris Wilson <chris@chris-wilson.co.uk>
      0af7e4df
  29. 15 12月, 2010 1 次提交
  30. 10 12月, 2010 1 次提交