1. 09 6月, 2009 4 次提交
  2. 07 6月, 2009 1 次提交
  3. 27 5月, 2009 2 次提交
    • B
      powerpc: Fix up dma_alloc_coherent() on platforms without cache coherency. · 8b31e49d
      Benjamin Herrenschmidt 提交于
      The implementation we just revived has issues, such as using a
      Kconfig-defined virtual address area in kernel space that nothing
      actually carves out (and thus will overlap whatever is there),
      or having some dependencies on being self contained in a single
      PTE page which adds unnecessary constraints on the kernel virtual
      address space.
      
      This fixes it by using more classic PTE accessors and automatically
      locating the area for consistent memory, carving an appropriate hole
      in the kernel virtual address space, leaving only the size of that
      area as a Kconfig option. It also brings some dma-mask related fixes
      from the ARM implementation which was almost identical initially but
      grew its own fixes.
      Signed-off-by: NBenjamin Herrenschmidt <benh@kernel.crashing.org>
      8b31e49d
    • B
      powerpc: Minor cleanups of kernel virt address space definitions · f637a49e
      Benjamin Herrenschmidt 提交于
      Make FIXADDR_TOP a compile time constant and cleanup a
      couple of definitions relative to the layout of the kernel
      address space on ppc32. We also print out that layout at
      boot time for debugging purposes.
      
      This is a pre-requisite for properly fixing non-coherent
      DMA allocactions.
      Signed-off-by: NBenjamin Herrenschmidt <benh@kernel.crashing.org>
      f637a49e
  4. 21 5月, 2009 11 次提交
  5. 19 5月, 2009 5 次提交
  6. 15 5月, 2009 2 次提交
  7. 03 5月, 2009 1 次提交
  8. 28 4月, 2009 2 次提交
  9. 23 4月, 2009 1 次提交
  10. 22 4月, 2009 1 次提交
  11. 15 4月, 2009 1 次提交
    • P
      powerpc: Fix data-corrupting bug in __futex_atomic_op · 306a8288
      Paul Mackerras 提交于
      Richard Henderson pointed out that the powerpc __futex_atomic_op has a
      bug: it will write the wrong value if the stwcx. fails and it has to
      retry the lwarx/stwcx. loop, since 'oparg' will have been overwritten
      by the result from the first time around the loop.  This happens
      because it uses the same register for 'oparg' (an input) as it uses
      for the result.
      
      This fixes it by using separate registers for 'oparg' and 'ret'.
      
      Cc: stable@kernel.org
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      306a8288
  12. 14 4月, 2009 1 次提交
    • T
      parport_pc: Fix build failure drivers/parport/parport_pc.c for powerpc · 19e05426
      Tony Breeds 提交于
      In commit 51dcdfec ("parport: Use the
      PCI IRQ if offered") parport_pc_probe_port() gained an irqflags arg.
      This isn't being supplied on powerpc.  This patch make powerpc fallback
      to the old behaviour, that is using "0" for irqflags.
      
      Fixes build failure:
      
        In file included from drivers/parport/parport_pc.c:68:
        arch/powerpc/include/asm/parport.h: In function 'parport_pc_find_nonpci_ports':
        arch/powerpc/include/asm/parport.h:32: error: too few arguments to function 'parport_pc_probe_port'
        arch/powerpc/include/asm/parport.h:32: error: too few arguments to function 'parport_pc_probe_port'
        arch/powerpc/include/asm/parport.h:32: error: too few arguments to function 'parport_pc_probe_port'
        make[3]: *** [drivers/parport/parport_pc.o] Error 1
      Signed-off-by: NTony Breeds <tony@bakeyournoodle.com>
      Signed-off-by: NAlan Cox <alan@linux.intel.com>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      19e05426
  13. 07 4月, 2009 7 次提交
  14. 06 4月, 2009 1 次提交