1. 14 5月, 2009 4 次提交
  2. 01 4月, 2009 1 次提交
  3. 30 3月, 2009 3 次提交
  4. 24 3月, 2009 2 次提交
  5. 12 3月, 2009 1 次提交
    • S
      MIPS: NEC VR5500 processor support fixup · a644b277
      Shinya Kuribayashi 提交于
      Current VR5500 processor support lacks of some functions which are
      expected to be configured/synthesized on arch initialization.
      
      Here're some VR5500A spec notes:
      
      * All execution hazards are handled in hardware.
      
      * Once VR5500A stops the operation of the pipeline by WAIT instruction,
        it could return from the standby mode only when either a reset, NMI
        request, or all enabled interrupts is/are detected.  In other words,
        if interrupts are disabled by Status.IE=0, it keeps in standby mode
        even when interrupts are internally asserted.
      
        Notes on WAIT: The operation of the processor is undefined if WAIT
        insn is in the branch delay slot.  The operation is also undefined
        if WAIT insn is executed when Status.EXL and Status.ERL are set to 1.
      
      * VR5500A core only implements the Load prefetch.
      
      With these changes, it boots fine.
      Signed-off-by: NShinya Kuribayashi <shinya.kuribayashi@necel.com>
      Signed-off-by: NRalf Baechle <ralf@linux-mips.org>
      a644b277
  6. 28 2月, 2009 1 次提交
  7. 31 1月, 2009 2 次提交
  8. 11 1月, 2009 6 次提交
  9. 13 12月, 2008 1 次提交
  10. 21 11月, 2008 1 次提交
  11. 28 10月, 2008 2 次提交
  12. 06 9月, 2008 2 次提交
  13. 31 7月, 2008 1 次提交
  14. 27 7月, 2008 2 次提交
    • J
      mips: use generic show_mem() · e66ddf1a
      Johannes Weiner 提交于
      Remove arch-specific show_mem() in favor of the generic version.
      
      This also removes the following redundant information display:
      
      	- pages in swapcache, printed by show_swap_cache_info()
      
      where show_mem() calls show_free_areas(), which calls
      show_swap_cache_info().
      
      And show_mem() does now actually print something on configurations
      with multiple nodes.
      Signed-off-by: NJohannes Weiner <hannes@saeurebad.de>
      Acked-by: NRalf Baechle <ralf@linux-mips.org>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      e66ddf1a
    • F
      dma-mapping: add the device argument to dma_mapping_error() · 8d8bb39b
      FUJITA Tomonori 提交于
      Add per-device dma_mapping_ops support for CONFIG_X86_64 as POWER
      architecture does:
      
      This enables us to cleanly fix the Calgary IOMMU issue that some devices
      are not behind the IOMMU (http://lkml.org/lkml/2008/5/8/423).
      
      I think that per-device dma_mapping_ops support would be also helpful for
      KVM people to support PCI passthrough but Andi thinks that this makes it
      difficult to support the PCI passthrough (see the above thread).  So I
      CC'ed this to KVM camp.  Comments are appreciated.
      
      A pointer to dma_mapping_ops to struct dev_archdata is added.  If the
      pointer is non NULL, DMA operations in asm/dma-mapping.h use it.  If it's
      NULL, the system-wide dma_ops pointer is used as before.
      
      If it's useful for KVM people, I plan to implement a mechanism to register
      a hook called when a new pci (or dma capable) device is created (it works
      with hot plugging).  It enables IOMMUs to set up an appropriate
      dma_mapping_ops per device.
      
      The major obstacle is that dma_mapping_error doesn't take a pointer to the
      device unlike other DMA operations.  So x86 can't have dma_mapping_ops per
      device.  Note all the POWER IOMMUs use the same dma_mapping_error function
      so this is not a problem for POWER but x86 IOMMUs use different
      dma_mapping_error functions.
      
      The first patch adds the device argument to dma_mapping_error.  The patch
      is trivial but large since it touches lots of drivers and dma-mapping.h in
      all the architecture.
      
      This patch:
      
      dma_mapping_error() doesn't take a pointer to the device unlike other DMA
      operations.  So we can't have dma_mapping_ops per device.
      
      Note that POWER already has dma_mapping_ops per device but all the POWER
      IOMMUs use the same dma_mapping_error function.  x86 IOMMUs use device
      argument.
      
      [akpm@linux-foundation.org: fix sge]
      [akpm@linux-foundation.org: fix svc_rdma]
      [akpm@linux-foundation.org: build fix]
      [akpm@linux-foundation.org: fix bnx2x]
      [akpm@linux-foundation.org: fix s2io]
      [akpm@linux-foundation.org: fix pasemi_mac]
      [akpm@linux-foundation.org: fix sdhci]
      [akpm@linux-foundation.org: build fix]
      [akpm@linux-foundation.org: fix sparc]
      [akpm@linux-foundation.org: fix ibmvscsi]
      Signed-off-by: NFUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
      Cc: Muli Ben-Yehuda <muli@il.ibm.com>
      Cc: Andi Kleen <andi@firstfloor.org>
      Cc: Thomas Gleixner <tglx@linutronix.de>
      Cc: Ingo Molnar <mingo@elte.hu>
      Cc: Avi Kivity <avi@qumranet.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      8d8bb39b
  15. 16 7月, 2008 1 次提交
  16. 09 7月, 2008 2 次提交
  17. 26 6月, 2008 1 次提交
  18. 16 6月, 2008 4 次提交
  19. 06 6月, 2008 2 次提交
  20. 12 5月, 2008 1 次提交