1. 15 8月, 2010 1 次提交
  2. 05 8月, 2010 1 次提交
  3. 27 2月, 2010 1 次提交
  4. 17 12月, 2009 2 次提交
  5. 18 9月, 2009 1 次提交
  6. 31 7月, 2008 1 次提交
  7. 16 7月, 2008 2 次提交
  8. 29 1月, 2008 2 次提交
  9. 30 10月, 2007 1 次提交
  10. 01 8月, 2007 2 次提交
  11. 11 7月, 2007 4 次提交
  12. 11 5月, 2007 1 次提交
  13. 14 3月, 2007 1 次提交
  14. 22 2月, 2007 1 次提交
    • F
      [MIPS] Add basic SMARTMIPS ASE support · 9693a853
      Franck Bui-Huu 提交于
      This patch adds trivial support for SMARTMIPS extension. This extension
      is currently implemented by 4KS[CD] CPUs.
      
      Basically it saves/restores ACX register, which is part of the SMARTMIPS
      ASE, when needed. This patch does *not* add any support for Smartmips MMU
      features.
      
      Futhermore this patch does not add explicit support for 4KS[CD] CPUs since
      they are respectively mips32 and mips32r2 compliant.  So with the current
      processor configuration, a platform that has such CPUs needs to select
      both configs:
      
      	CPU_HAS_SMARTMIPS
      	SYS_HAS_CPU_MIPS32_R[12]
      
      This is due to the processor configuration which is mixing up all the
      architecture variants and the processor types.
      
      The drawback of this, is that we currently pass '-march=mips32' option to
      gcc when building a kernel instead of '-march=4ksc' for 4KSC case. This
      can lead to a kernel image a little bit bigger than required.
      Signed-off-by: NFranck Bui-Huu <fbuihuu@gmail.com>
      Signed-off-by: NRalf Baechle <ralf@linux-mips.org>
      9693a853
  15. 19 2月, 2007 1 次提交
  16. 09 12月, 2006 1 次提交
  17. 02 10月, 2006 1 次提交
  18. 27 9月, 2006 1 次提交
  19. 14 7月, 2006 1 次提交
  20. 20 6月, 2006 3 次提交
  21. 27 4月, 2006 1 次提交
  22. 21 3月, 2006 1 次提交
  23. 01 12月, 2005 1 次提交
  24. 18 11月, 2005 1 次提交
  25. 30 10月, 2005 1 次提交
  26. 05 9月, 2005 2 次提交
  27. 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