1. 29 7月, 2008 1 次提交
  2. 16 5月, 2008 1 次提交
  3. 03 10月, 2007 2 次提交
    • P
      sh: Make kgdb i-cache flushing less inept. · 01bd5e9e
      Paul Mundt 提交于
      kgdb had its own ranged I-cache flushing routine that attempted to
      duplicate the flush_icache_range() functionality, but managed to do
      an explicit D-cache writeback & invalidate twice on SH-4. This is
      a no-op for SH-3, and the flush_icache_range() semantics already do
      what kgdb was feebly attempting to do already, so just move over to
      that and kill off the wrapper.
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      01bd5e9e
    • P
      sh: kgdb section mismatches and tidying. · a90f3547
      Paul Mundt 提交于
      The kgdb console setup was callable from a left-over deferred
      initialization path, which in turn depends on __init symbols. Since
      the deferred initialization was removed some time ago, kill off the
      rest of those remnants and move kgdb_init() and friends to __init.
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      a90f3547
  4. 07 5月, 2007 1 次提交
  5. 13 2月, 2007 1 次提交
    • P
      sh: Use a jump call table for debug trap handlers. · f413d0d9
      Paul Mundt 提交于
      This rips out most of the needlessly complicated sh_bios and kgdb
      trap handling, and forces it all through a common fast dispatch path.
      As more debug traps are inserted, it's important to keep them in sync
      for all of the parts, not just SH-3/4.
      
      As the SH-2 parts are unable to do traps in the >= 0x40 range, we
      restrict the debug traps to the 0x30-0x3f range on all parts, and
      also bump the kgdb breakpoint trap down in to this range (from 0xff
      to 0x3c) so it's possible to use for nommu.
      
      Optionally, this table can be padded out to catch spurious traps for
      SH-3/4, but we don't do that yet..
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      f413d0d9
  6. 27 9月, 2006 1 次提交
  7. 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