1. 19 6月, 2008 10 次提交
  2. 13 6月, 2008 2 次提交
  3. 23 5月, 2008 1 次提交
  4. 07 5月, 2008 4 次提交
  5. 30 4月, 2008 1 次提交
  6. 29 4月, 2008 1 次提交
  7. 26 4月, 2008 7 次提交
  8. 20 4月, 2008 1 次提交
    • G
      DRM: remove unused dev_class · 56d110e8
      Greg Kroah-Hartman 提交于
      The struct class_device *dev_class is not used in the struct drm_head
      structure at all, so remove it as class_device is being removed entirely
      from the kernel.
      
      
      Cc: David Airlie <airlied@linux.ie>
      Cc: Tony Jones <tonyj@suse.de>
      Cc: Kay Sievers <kay.sievers@vrfy.org>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      56d110e8
  9. 07 4月, 2008 1 次提交
  10. 30 3月, 2008 4 次提交
  11. 29 3月, 2008 1 次提交
  12. 17 3月, 2008 4 次提交
    • D
      drm/ati_pcigart: fix the PCIGART to use drm_pci to allocate GART table. · b05c2385
      Dave Airlie 提交于
      This fixes a problem on 64-bit with 4GB with ATI RS690 chipsets. It
      makes sure the pcigart table is allocated in coherent memory for DMA operations.
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      b05c2385
    • A
      drm/radeon: fixup RV550 chip family · 16d3be46
      Alex Deucher 提交于
      This fixes up the RV550 chips which are based on RV515, not RV530.
      It also adds another RS690 PCI ID.
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      16d3be46
    • T
      drm/via: attempt again to stabilise the AGP DMA command submission. · f0fb6d77
      Thomas Hellstrom 提交于
      It's worth remembering that all new bright ideas on how to make this command reader work properly and according to docs will probably fail :( Bring in some old code.
      
      Also allow a larger SG-DMA download stride, and remove unnecessary waits for
      command regulators pauses.
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      f0fb6d77
    • M
      drm: Fix race that can lockup the kernel · 9df5808c
      Mike Isely 提交于
      The i915_vblank_swap() function schedules an automatic buffer swap
      upon receipt of the vertical sync interrupt.  Such an operation is
      lengthy so it can't be allowed to happen in normal interrupt context,
      thus the DRM implements this by scheduling the work in a kernel
      softirq-scheduled tasklet.  In order for the buffer swap to work
      safely, the DRM's central lock must be taken, via a call to
      drm_lock_take() located in drivers/char/drm/drm_irq.c within the
      function drm_locked_tasklet_func().  The lock-taking logic uses a
      non-interrupt-blocking spinlock to implement the manipulations needed
      to take the lock.  This semantic would be safe if all attempts to use
      the spinlock only happen from process context.  However this buffer
      swap happens from softirq context which is really a form of interrupt
      context.  Thus we have an unsafe situation, in that
      drm_locked_tasklet_func() can block on a spinlock already taken by a
      thread in process context which will never get scheduled again because
      of the blocked softirq tasklet.  This wedges the kernel hard.
      
      To trigger this bug, run a dual-head cloned mode configuration which
      uses the i915 drm, then execute an opengl application which
      synchronizes buffer swaps against the vertical sync interrupt.  In my
      testing, a lockup always results after running anywhere from 5 minutes
      to an hour and a half.  I believe dual-head is needed to really
      trigger the problem because then the vertical sync interrupt handling
      is no longer predictable (due to being interrupt-sourced from two
      different heads running at different speeds).  This raises the
      probability of the tasklet trying to run while the userspace DRI is
      doing things to the GPU (and manipulating the DRM lock).
      
      The fix is to change the relevant spinlock semantics to be the
      interrupt-blocking form.  After this change I am no longer able to
      trigger the lockup; the longest test run so far was 20 hours (test
      stopped after that point).
      
      Note: I have examined the places where this spinlock is being
      employed; all are reasonably short bounded sequences and should be
      suitable for interrupts being blocked without impacting overall kernel
      interrupt response latency.
      Signed-off-by: NMike Isely <isely@pobox.com>
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      9df5808c
  13. 23 2月, 2008 1 次提交
  14. 20 2月, 2008 2 次提交