1. 09 8月, 2008 12 次提交
  2. 07 8月, 2008 5 次提交
  3. 03 8月, 2008 3 次提交
  4. 02 8月, 2008 1 次提交
  5. 01 8月, 2008 1 次提交
    • P
      Fix rename of at91_nand -> atmel_nand · f6ed6f78
      Pieter du Preez 提交于
      Structs called at91_nand_data where renamed to atmel_nand_data
      and configs called *MTD_NAND_AT91* where renamed to
      *MTD_NAND_ATMEL*. This was unfortunately not done consistently,
      causing NAND chips not being initialised on several ARM boards.
      
      I am aware that the author of the original change did not rename
      MTD_NAND_AT91_BUSWIDTH to MTD_NAND_ATMEL_BUSWIDTH, for example.
      All *MTD_NAND_AT91* where renamed to *MTD_NAND_ATMEL* in order
      to keep naming consistency.
      
      This patch was only tested on a MACH_SAM9_L9260, as this is the
      only ARM board I have to my disposal.
      
      Before this patch:
      
      $ git-ls-files |xargs grep atmel_nand |wc -l
      105
      $ git-ls-files |xargs grep at91_nand |wc -l
      4
      $ git-ls-files |xargs grep MTD_NAND_ATMEL |wc -l
      8
      $ git-ls-files |xargs grep MTD_NAND_AT91 |wc -l
      47
      
      After this patch:
      
      $ git-ls-files |xargs grep atmel_nand |wc -l
      109
      $ git-ls-files |xargs grep at91_nand |wc -l
      0
      $ git-ls-files |xargs grep MTD_NAND_ATMEL |wc -l
      55
      $ git-ls-files |xargs grep MTD_NAND_AT91 |wc -l
      0
      Signed-off-by: NPieter du Preez <pdupreez@gmail.com>
      Signed-off-by: NDavid Woodhouse <David.Woodhouse@intel.com>
      f6ed6f78
  6. 31 7月, 2008 1 次提交
  7. 30 7月, 2008 1 次提交
  8. 29 7月, 2008 3 次提交
  9. 28 7月, 2008 4 次提交
  10. 27 7月, 2008 5 次提交
    • R
      [ARM] Fix shared mmap when more than two maps of the same file exist · 53cdb27a
      Russell King 提交于
      The shared mmap code works fine for the test case, which only checked
      for two shared maps of the same file.  However, three shared maps
      result in one mapping remaining cached, resulting in stale data being
      visible via that mapping.  Fix this.
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      53cdb27a
    • D
      [ARM] 5179/1: Replace obsolete IRQT_* and __IRQT_* values with IRQ_TYPE_* · 6cab4860
      Dmitry Baryshkov 提交于
      IRQT_* and __IRQT_* were obsoleted long ago by patch [3692/1].
      Remove them completely. Sed script for the reference:
      
      s/__IRQT_RISEDGE/IRQ_TYPE_EDGE_RISING/g
      s/__IRQT_FALEDGE/IRQ_TYPE_EDGE_FALLING/g
      s/__IRQT_LOWLVL/IRQ_TYPE_LEVEL_LOW/g
      s/__IRQT_HIGHLVL/IRQ_TYPE_LEVEL_HIGH/g
      s/IRQT_RISING/IRQ_TYPE_EDGE_RISING/g
      s/IRQT_FALLING/IRQ_TYPE_EDGE_FALLING/g
      s/IRQT_BOTHEDGE/IRQ_TYPE_EDGE_BOTH/g
      s/IRQT_LOW/IRQ_TYPE_LEVEL_LOW/g
      s/IRQT_HIGH/IRQ_TYPE_LEVEL_HIGH/g
      s/IRQT_PROBE/IRQ_TYPE_PROBE/g
      s/IRQT_NOEDGE/IRQ_TYPE_NONE/g
      Signed-off-by: NDmitry Baryshkov <dbaryshkov@gmail.com>
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      6cab4860
    • I
      [ARM] update defconfig for eseries. · 1d1f8b37
      Ian Molton 提交于
      Signed-off-by: NIan Molton <spyro@f2s.com>
      1d1f8b37
    • A
      SL*B: drop kmem cache argument from constructor · 51cc5068
      Alexey Dobriyan 提交于
      Kmem cache passed to constructor is only needed for constructors that are
      themselves multiplexeres.  Nobody uses this "feature", nor does anybody uses
      passed kmem cache in non-trivial way, so pass only pointer to object.
      
      Non-trivial places are:
      	arch/powerpc/mm/init_64.c
      	arch/powerpc/mm/hugetlbpage.c
      
      This is flag day, yes.
      Signed-off-by: NAlexey Dobriyan <adobriyan@gmail.com>
      Acked-by: NPekka Enberg <penberg@cs.helsinki.fi>
      Acked-by: NChristoph Lameter <cl@linux-foundation.org>
      Cc: Jon Tollefson <kniht@linux.vnet.ibm.com>
      Cc: Nick Piggin <nickpiggin@yahoo.com.au>
      Cc: Matt Mackall <mpm@selenic.com>
      [akpm@linux-foundation.org: fix arch/powerpc/mm/hugetlbpage.c]
      [akpm@linux-foundation.org: fix mm/slab.c]
      [akpm@linux-foundation.org: fix ubifs]
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      51cc5068
    • 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
  11. 26 7月, 2008 4 次提交