1. 19 6月, 2008 1 次提交
    • K
      powerpc/booke: Add support for new e500mc core · 3dfa8773
      Kumar Gala 提交于
      The new e500mc core from Freescale is based on the e500v2 but with the
      following changes:
      
      * Supports only the Enhanced Debug Architecture (DSRR0/1, etc)
      * Floating Point
      * No SPE
      * Supports lwsync
      * Doorbell Exceptions
      * Hypervisor
      * Cache line size is now 64-bytes (e500v1/v2 have a 32-byte cache line)
      Signed-off-by: NKumar Gala <galak@kernel.crashing.org>
      3dfa8773
  2. 12 6月, 2008 1 次提交
  3. 03 6月, 2008 3 次提交
    • K
      [POWERPC] 40x/Book-E: Save/restore volatile exception registers · fca622c5
      Kumar Gala 提交于
      On machines with more than one exception level any system register that
      might be modified by the "normal" exception level needs to be saved and
      restored on taking a higher level exception.  We already are saving
      and restoring ESR and DEAR.
      
      For critical level add SRR0/1.
      For debug level add CSRR0/1 and SRR0/1.
      For machine check level add DSRR0/1, CSRR0/1, and SRR0/1.
      
      On FSL Book-E parts we always save/restore the MAS registers for critical,
      debug, and machine check level exceptions.  On 44x we always save/restore
      the MMUCR.
      
      Additionally, we save and restore the ksp_limit since we have to adjust it
      for each exception level.
      Signed-off-by: NKumar Gala <galak@kernel.crashing.org>
      Acked-by: NPaul Mackerras <paulus@samba.org>
      fca622c5
    • K
      [POWERPC] Rework EXC_LEVEL_EXCEPTION_PROLOG code · 369e757b
      Kumar Gala 提交于
      * Cleanup the code a bit my allocating an INT_FRAME on our exception
        stack there by make references go from GPR11-INT_FRAME_SIZE(r8) to
        just GPR11(r8)
      * simplify {lvl}_transfer_to_handler code by moving the copying of the
        temp registers we use if we come from user space into the PROLOG
      * If the exception came from kernel mode copy thread_info flags,
        preempt, and task pointer from the process thread_info.
      Signed-off-by: NKumar Gala <galak@kernel.crashing.org>
      Acked-by: NPaul Mackerras <paulus@samba.org>
      369e757b
    • K
      [POWERPC] Move to runtime allocated exception stacks · bcf0b088
      Kumar Gala 提交于
      For the additonal exception levels (critical, debug, machine check) on
      40x/book-e we were using "static" allocations of the stack in the
      associated head.S.
      
      Move to a runtime allocation to make the code a bit easier to read as
      we mimic how we handle IRQ stacks.  Its also a bit easier to setup the
      stack with a "dummy" thread_info in C code.
      Signed-off-by: NKumar Gala <galak@kernel.crashing.org>
      Acked-by: NPaul Mackerras <paulus@samba.org>
      bcf0b088
  4. 14 5月, 2008 1 次提交
  5. 17 4月, 2008 1 次提交
    • K
      [POWERPC] Rework Book-E debug exception handling · eb0cd5fd
      Kumar Gala 提交于
      The architecture allows for "Book-E" style debug interrupts to either go
      to critial interrupts of their own debug interrupt level.  To allow for
      a dynamic kernel to support machines of either type we want to be able to
      compile in the interrupt handling code for both exception levels.
      
      Towards this goal we renamed the debug handling macros to specify the
      interrupt level in their name (DEBUG_CRIT_EXCEPTION/DebugCrit and
      DEBUG_DEBUG_EXCEPTION/DebugDebug).
      
      Additionally, on the Freescale Book-e parts we expanded the exception
      stacks to cover the maximum case of needing three exception stacks (normal,
      machine check and debug).
      
      There is some kernel text space optimization to be gained if a kernel is
      configured for a specific Freescale implementation but we aren't handling
      that now to allow for the single kernel image support.
      Signed-off-by: NKumar Gala <galak@kernel.crashing.org>
      eb0cd5fd
  6. 24 12月, 2007 1 次提交
  7. 10 2月, 2006 1 次提交
  8. 20 1月, 2006 1 次提交
  9. 10 11月, 2005 1 次提交
  10. 01 10月, 2005 1 次提交
  11. 26 6月, 2005 1 次提交
  12. 22 6月, 2005 1 次提交
  13. 01 5月, 2005 1 次提交
  14. 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