1. 25 7月, 2007 2 次提交
  2. 24 7月, 2007 2 次提交
    • A
      sh: Fix Dreamcast DMA issues. · eb695dbf
      Adrian McMenamin 提交于
      The current SH DMA API is somewhat broken, not correctly matching
      virtual channel to the correct SH DMAC. This wasn't noticeable when
      using g2 DMA for the sound driver - one channel 0 is as good as any
      other! - but caused the pvr2 driver to fail.
      
      This patch fixes the pvr2 problem and consequently fixes the sound
      driver to ensure it continues to function.
      
      Signed-off by: Adrian McMenamin <adrian@mcmen.demon.co.uk>
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      eb695dbf
    • P
      sh: Add kmap_coherent()/kunmap_coherent() interface for SH-4. · 8cf1a743
      Paul Mundt 提交于
      This wires up kmap_coherent() and kunmap_coherent() on SH-4, and
      moves away from the p3map_mutex and reserved P3 space, opting to
      use fixmaps for colouring instead.
      
      The copy_user_page()/clear_user_page() implementations are moved
      to this, which fixes the nasty blowups with spinlock debugging
      as a result of having some of these calls nested under the page
      table lock.
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      8cf1a743
  3. 22 7月, 2007 1 次提交
  4. 20 7月, 2007 28 次提交
  5. 18 7月, 2007 3 次提交
  6. 17 7月, 2007 1 次提交
    • H
      generic bug: use show_regs() instead of dump_stack() · 608e2619
      Heiko Carstens 提交于
      The current generic bug implementation has a call to dump_stack() in case a
      WARN_ON(whatever) gets hit.  Since report_bug(), which calls dump_stack(),
      gets called from an exception handler we can do better: just pass the
      pt_regs structure to report_bug() and pass it to show_regs() in case of a
      warning.  This will give more debug informations like register contents,
      etc...  In addition this avoids some pointless lines that dump_stack()
      emits, since it includes a stack backtrace of the exception handler which
      is of no interest in case of a warning.  E.g.  on s390 the following lines
      are currently always present in a stack backtrace if dump_stack() gets
      called from report_bug():
      
       [<000000000001517a>] show_trace+0x92/0xe8)
       [<0000000000015270>] show_stack+0xa0/0xd0
       [<00000000000152ce>] dump_stack+0x2e/0x3c
       [<0000000000195450>] report_bug+0x98/0xf8
       [<0000000000016cc8>] illegal_op+0x1fc/0x21c
       [<00000000000227d6>] sysc_return+0x0/0x10
      Acked-by: NJeremy Fitzhardinge <jeremy@goop.org>
      Acked-by: NHaavard Skinnemoen <hskinnemoen@atmel.com>
      Cc: Andi Kleen <ak@suse.de>
      Cc: Kyle McMartin <kyle@parisc-linux.org>
      Cc: Paul Mackerras <paulus@samba.org>
      Cc: Paul Mundt <lethal@linux-sh.org>
      Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>
      Signed-off-by: NHeiko Carstens <heiko.carstens@de.ibm.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      608e2619
  7. 16 7月, 2007 1 次提交
  8. 13 7月, 2007 2 次提交