1. 19 2月, 2009 1 次提交
  2. 28 1月, 2009 1 次提交
  3. 01 9月, 2008 1 次提交
  4. 07 8月, 2008 1 次提交
  5. 19 4月, 2008 3 次提交
  6. 26 1月, 2008 4 次提交
  7. 27 11月, 2007 2 次提交
  8. 17 2月, 2007 1 次提交
  9. 07 2月, 2007 1 次提交
    • R
      [ARM] Move processor_modes[] to .../process.c · ae0a846e
      Russell King 提交于
      bad_mode() currently prints the mode which caused the exception, and
      then causes an oops dump to be printed which again displays this
      information (since the CPSR in the struct pt_regs is correct.)  This
      leads to processor_modes[] being shared between traps.c and process.c
      with a local declaration of it.
      
      We can clean this up by moving processor_modes[] to process.c and
      removing the duplication, resulting in processor_modes[] becoming
      static.
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      ae0a846e
  10. 07 1月, 2007 1 次提交
  11. 04 12月, 2006 1 次提交
    • L
      [ARM] 3881/4: xscale: clean up cp0/cp1 handling · afe4b25e
      Lennert Buytenhek 提交于
      XScale cores either have a DSP coprocessor (which contains a single
      40 bit accumulator register), or an iWMMXt coprocessor (which contains
      eight 64 bit registers.)
      
      Because of the small amount of state in the DSP coprocessor, access to
      the DSP coprocessor (CP0) is always enabled, and DSP context switching
      is done unconditionally on every task switch.  Access to the iWMMXt
      coprocessor (CP0/CP1) is enabled only when an iWMMXt instruction is
      first issued, and iWMMXt context switching is done lazily.
      
      CONFIG_IWMMXT is supposed to mean 'the cpu we will be running on will
      have iWMMXt support', but boards are supposed to select this config
      symbol by hand, and at least one pxa27x board doesn't get this right,
      so on that board, proc-xscale.S will incorrectly assume that we have a
      DSP coprocessor, enable CP0 on boot, and we will then only save the
      first iWMMXt register (wR0) on context switches, which is Bad.
      
      This patch redefines CONFIG_IWMMXT as 'the cpu we will be running on
      might have iWMMXt support, and we will enable iWMMXt context switching
      if it does.'  This means that with this patch, running a CONFIG_IWMMXT=n
      kernel on an iWMMXt-capable CPU will no longer potentially corrupt iWMMXt
      state over context switches, and running a CONFIG_IWMMXT=y kernel on a
      non-iWMMXt capable CPU will still do DSP context save/restore.
      
      These changes should make iWMMXt work on PXA3xx, and as a side effect,
      enable proper acc0 save/restore on non-iWMMXt capable xsc3 cores such
      as IOP13xx and IXP23xx (which will not have CONFIG_CPU_XSCALE defined),
      as well as setting and using HWCAP_IWMMXT properly.
      Signed-off-by: NLennert Buytenhek <buytenh@wantstofly.org>
      Acked-by: NDan Williams <dan.j.williams@intel.com>
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      afe4b25e
  12. 20 9月, 2006 1 次提交
  13. 19 8月, 2006 1 次提交
  14. 02 7月, 2006 1 次提交
  15. 01 7月, 2006 1 次提交
  16. 29 6月, 2006 1 次提交
  17. 22 6月, 2006 1 次提交
    • R
      [ARM] Add thread_notify infrastructure · d6551e88
      Russell King 提交于
      Some machine classes need to allow VFP support to be built into the
      kernel, but still allow the kernel to run even though VFP isn't
      present.  Unfortunately, the kernel hard-codes VFP instructions
      into the thread switch, which prevents this being run-time selectable.
      
      Solve this by introducing a notifier which things such as VFP can
      hook into to be informed of events which affect the VFP subsystem
      (eg, creation and destruction of threads, switches between threads.)
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      d6551e88
  18. 29 3月, 2006 1 次提交
  19. 22 3月, 2006 1 次提交
  20. 23 2月, 2006 1 次提交
  21. 09 2月, 2006 2 次提交
  22. 19 1月, 2006 1 次提交
  23. 15 1月, 2006 1 次提交
  24. 14 1月, 2006 1 次提交
  25. 04 1月, 2006 1 次提交
    • R
      [ARM] Cleanup ARM includes · 78ff18a4
      Russell King 提交于
      arch/arm/kernel/entry-armv.S has contained a comment suggesting
      that asm/hardware.h and asm/arch/irqs.h should be moved into the
      asm/arch/entry-macro.S include.  So move the includes to these
      two files as required.
      
      Add missing includes (asm/hardware.h, asm/io.h) to asm/arch/system.h
      includes which use those facilities, and remove asm/io.h from
      kernel/process.c.
      
      Remove other unnecessary includes from arch/arm/kernel, arch/arm/mm
      and arch/arm/mach-footbridge.
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      78ff18a4
  26. 20 12月, 2005 1 次提交
  27. 09 11月, 2005 1 次提交
  28. 06 11月, 2005 1 次提交
  29. 30 10月, 2005 1 次提交
  30. 24 9月, 2005 1 次提交
  31. 10 8月, 2005 1 次提交
  32. 09 6月, 2005 1 次提交
  33. 01 6月, 2005 1 次提交
    • R
      [PATCH] ARM SMP: Fix vector entry · ccea7a19
      Russell King 提交于
      The current vector entry system does not allow for SMP.  In
      order to work around this, we need to eliminate our reliance
      on the fixed save areas, which breaks the way we enable
      alignment traps.  This patch changes the way we handle the
      save areas such that we can have one per CPU.
      Signed-off-by: NRussell King <rmk@arm.linux.org.uk>
      ccea7a19