1. 14 3月, 2007 1 次提交
  2. 12 3月, 2007 1 次提交
  3. 18 2月, 2007 1 次提交
  4. 15 2月, 2007 1 次提交
  5. 14 2月, 2007 1 次提交
  6. 13 2月, 2007 10 次提交
  7. 12 12月, 2006 6 次提交
  8. 08 12月, 2006 1 次提交
  9. 06 12月, 2006 13 次提交
  10. 31 10月, 2006 1 次提交
  11. 20 10月, 2006 1 次提交
    • P
      sh: Convert INTC2 to IRQ table registration. · 66a74057
      Paul Mundt 提交于
      Currently the INTC2 code contains a fixed IRQ table that it
      iterates through to set the handler type, we move this in to
      the CPU subtype setup code instead and allow for submitting
      the table that way.
      
      This drops the ST40 tables, as nothing has been happening
      with those processors, while converting the only existing
      users to use the new table directly (SH7760 and SH7780).
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      66a74057
  12. 19 10月, 2006 2 次提交
  13. 12 10月, 2006 1 次提交
    • P
      sh: interrupt exception handling rework · baf4326e
      Paul Mundt 提交于
      Kill off interrupt_table for all of the CPU subtypes, we now
      default in to stepping in to do_IRQ() for _all_ IRQ exceptions
      and counting the spurious ones, rather than simply flipping on
      the ones we cared about. This and enabling the IRQ by default
      automatically has already uncovered a couple of bugs and IRQs
      that weren't being caught, as well as some that are being
      generated far too often (SCI Tx Data Empty, for example).
      
      The general rationale is to use a marker for interrupt exceptions,
      test for it in the handle_exception() path, and skip out to
      do_IRQ() if it's found. Everything else follows the same behaviour
      of finding the cached EXPEVT value in r2/r2_bank, we just rip out
      the INTEVT read from entry.S entirely (except for in the kGDB NMI
      case, which is another matter).
      
      Note that while this changes the do_IRQ() semantics regarding r4
      handling, they were fundamentally broken anyways (relying entirely
      on r2_bank for the cached code). With this, we do the INTEVT read
      from do_IRQ() itself (in the CONFIG_CPU_HAS_INTEVT case), or fall
      back on r4 for the muxed IRQ number, which should also be closer
      to what SH-2 and SH-2A want anyways.
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      baf4326e