1. 09 3月, 2009 1 次提交
  2. 13 12月, 2008 1 次提交
    • R
      [ARM] fix xm_x2xx_defconfig build errors · 67fbc231
      Russell King 提交于
      drivers/built-in.o: In function `pci_set_consistent_dma_mask':
      hid-quirks.c:(.text+0x2664): multiple definition of `pci_set_consistent_dma_mask'
      drivers/built-in.o: In function `pci_set_dma_mask':
      hid-quirks.c:(.text+0x42c4): multiple definition of `pci_set_dma_mask'
      
      because drivers/pci/pci.c was not seeing the definition disabling these
      functions.
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      67fbc231
  3. 07 8月, 2008 1 次提交
  4. 16 10月, 2007 1 次提交
  5. 12 7月, 2007 1 次提交
    • E
      [ARM] 4451/1: pxa: make dma.c generic and remove cpu specific dma code · f53f066c
      Eric Miao 提交于
      Since the number of dma channels varies between pxa25x and pxa27x, it
      introduces some specific code in dma.c. This patch moves the specific
      code to pxa25x.c and pxa27x.c and makes dma.c more generic.
      
      1. add pxa_init_dma() for dma initialization, the number of channels
         are passed in by the argument
      
      2. add a "prio" field to the "struct pxa_dma_channel" for the channel
         priority, and is initialized in pxa_init_dma()
      
      3. use a general priority comparison with the channels "prio" field so
         to remove the processor specific pxa_for_each_dma_prio macro,  this
         is not lightning fast as the original one,  but it is acceptable as
         it happens when requesting dma, which is usually not so performance
         critical
      Signed-off-by: Neric miao <eric.miao@marvell.com>
      Acked-by: NNicolas Pitre <nico@cam.org>
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      f53f066c
  6. 07 10月, 2006 1 次提交
  7. 06 5月, 2006 1 次提交
  8. 04 1月, 2006 2 次提交
  9. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4