1. 05 3月, 2007 1 次提交
  2. 13 2月, 2007 3 次提交
    • P
      sh: Missing flush_dcache_all() proto in cacheflush.h. · fe828917
      Paul Mundt 提交于
      Some boards need this, so provide a definition.
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      fe828917
    • M
      sh: SH-DMAC compile fixes · 9f8a5e3a
      Manuel Lauss 提交于
      This patch does the following:
      - remove the make_ipr_irq stuff from dma-sh.c and replace it
        with a simple channel<->irq mapping table.
      - add DMTEx_IRQ constants for sh4 cpus
      - fix sh7751 DMAE irq number
      
      The SH7780 uses the same IRQs for DMA as other SH4 types, so
      I put the constants on top of the dma.h file.
      
      Other CPU types need to #define their own DMTEx_IRQ contants
      in their appropriate header.
      Signed-off-by: NManuel Lauss <mano@roarinelk.homelinux.net>
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      9f8a5e3a
    • P
      sh: Lazy dcache writeback optimizations. · 26b7a78c
      Paul Mundt 提交于
      This converts the lazy dcache handling to the model described in
      Documentation/cachetlb.txt and drops the ptep_get_and_clear() hacks
      used for the aliasing dcaches on SH-4 and SH7705 in 32kB mode. As a
      bonus, this slightly cuts down on the cache flushing frequency.
      
      With that and the PTEA handling out of the way, the update_mmu_cache()
      implementations can be consolidated, and we no longer have to worry
      about which configuration the cache is in for the SH7705 case.
      
      And finally, explicitly disable the lazy writeback on SMP (SH-4A).
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      26b7a78c
  3. 14 12月, 2006 1 次提交
  4. 12 12月, 2006 1 次提交
  5. 12 10月, 2006 1 次提交
  6. 03 10月, 2006 1 次提交
  7. 27 9月, 2006 7 次提交
  8. 02 2月, 2006 1 次提交
  9. 17 1月, 2006 2 次提交
  10. 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