1. 17 2月, 2015 1 次提交
  2. 24 5月, 2014 1 次提交
    • R
      MIPS: MT: Remove SMTC support · b633648c
      Ralf Baechle 提交于
      Nobody is maintaining SMTC anymore and there also seems to be no userbase.
      Which is a pity - the SMTC technology primarily developed by Kevin D.
      Kissell <kevink@paralogos.com> is an ingenious demonstration for the MT
      ASE's power and elegance.
      
      Based on Markos Chandras <Markos.Chandras@imgtec.com> patch
      https://patchwork.linux-mips.org/patch/6719/ which while very similar did
      no longer apply cleanly when I tried to merge it plus some additional
      post-SMTC cleanup - SMTC was a feature as tricky to remove as it was to
      merge once upon a time.
      Signed-off-by: NRalf Baechle <ralf@linux-mips.org>
      b633648c
  3. 01 4月, 2014 1 次提交
    • H
      MIPS: Loongson: Add basic Loongson-3 definition · 152ebb44
      Huacai Chen 提交于
      Loongson-3 is a multi-core MIPS family CPU, it support MIPS64R2 fully.
      Loongson-3 has the same IMP field (0x6300) as Loongson-2.
      
      Loongson-3 has a hardware-maintained cache, system software doesn't
      need to maintain coherency.
      
      Loongson-3A is the first revision of Loongson-3, and it is the quad-
      core version of Loongson-2G. Loongson-3A has a simplified version named
      Loongson-2Gq, the main difference between Loongson-3A/2Gq is 3A has two
      HyperTransport controller but 2Gq has only one. HT0 is used for cross-
      chip interconnection and HT1 is used to link PCI bus. Therefore, 2Gq
      cannot support NUMA but 3A can. For software, Loongson-2Gq is simply
      identified as Loongson-3A.
      
      Exsisting Loongson family CPUs:
      Loongson-1: Loongson-1A, Loongson-1B, they are 32-bit MIPS CPUs.
      Loongson-2: Loongson-2E, Loongson-2F, Loongson-2G, they are 64-bit
                  single-core MIPS CPUs.
      Loongson-3: Loongson-3A(including so-called Loongson-2Gq), they are
                  64-bit multi-core MIPS CPUs.
      Signed-off-by: NHuacai Chen <chenhc@lemote.com>
      Signed-off-by: NHongliang Tao <taohl@lemote.com>
      Signed-off-by: NHua Yan <yanh@lemote.com>
      Tested-by: NAlex Smith <alex.smith@imgtec.com>
      Reviewed-by: NAlex Smith <alex.smith@imgtec.com>
      Cc: John Crispin <john@phrozen.org>
      Cc: Steven J. Hill <Steven.Hill@imgtec.com>
      Cc: Aurelien Jarno <aurelien@aurel32.net>
      Cc: linux-mips@linux-mips.org
      Cc: Fuxin Zhang <zhangfx@lemote.com>
      Cc: Zhangjin Wu <wuzhangjin@gmail.com>
      Patchwork: https://patchwork.linux-mips.org/patch/6629/Signed-off-by: NRalf Baechle <ralf@linux-mips.org>
      152ebb44
  4. 14 12月, 2012 1 次提交
  5. 28 9月, 2012 1 次提交
    • D
      Make most arch asm/module.h files use asm-generic/module.h · 786d35d4
      David Howells 提交于
      Use the mapping of Elf_[SPE]hdr, Elf_Addr, Elf_Sym, Elf_Dyn, Elf_Rel/Rela,
      ELF_R_TYPE() and ELF_R_SYM() to either the 32-bit version or the 64-bit version
      into asm-generic/module.h for all arches bar MIPS.
      
      Also, use the generic definition mod_arch_specific where possible.
      
      To this end, I've defined three new config bools:
      
       (*) HAVE_MOD_ARCH_SPECIFIC
      
           Arches define this if they don't want to use the empty generic
           mod_arch_specific struct.
      
       (*) MODULES_USE_ELF_RELA
      
           Arches define this if their modules can contain RELA records.  This causes
           the Elf_Rela mapping to be emitted and allows apply_relocate_add() to be
           defined by the arch rather than have the core emit an error message.
      
       (*) MODULES_USE_ELF_REL
      
           Arches define this if their modules can contain REL records.  This causes
           the Elf_Rel mapping to be emitted and allows apply_relocate() to be
           defined by the arch rather than have the core emit an error message.
      
      Note that it is possible to allow both REL and RELA records: m68k and mips are
      two arches that do this.
      
      With this, some arch asm/module.h files can be deleted entirely and replaced
      with a generic-y marker in the arch Kbuild file.
      
      Additionally, I have removed the bits from m32r and score that handle the
      unsupported type of relocation record as that's now handled centrally.
      Signed-off-by: NDavid Howells <dhowells@redhat.com>
      Acked-by: NSam Ravnborg <sam@ravnborg.org>
      Signed-off-by: NRusty Russell <rusty@rustcorp.com.au>
      786d35d4
  6. 17 8月, 2012 1 次提交
  7. 23 7月, 2012 1 次提交
    • K
      MIPS: Add CPU support for Loongson1B · 2fa36399
      Kelvin Cheung 提交于
      Loongson 1B is a 32-bit SoC designed by Institute of Computing Technology
      (ICT) and the Chinese Academy of Sciences (CAS), which implements the
      MIPS32 release 2 instruction set.
      
      [ralf@linux-mips.org: But which is not strictly a MIPS32 compliant device
      which also is why it identifies itself with the Legacy Vendor ID in the
      PrID register.  When applying the patch I shoveled some code around to
      keep things in alphabetical order and avoid forward declarations.]
      Signed-off-by: NKelvin Cheung <keguang.zhang@gmail.com>
      Cc: To: linux-mips@linux-mips.org
      Cc: linux-kernel@vger.kernel.org
      Cc: wuzhangjin@gmail.com
      Cc: zhzhl555@gmail.com
      Cc: Kelvin Cheung <keguang.zhang@gmail.com>
      Patchwork: https://patchwork.linux-mips.org/patch/3976/Signed-off-by: NRalf Baechle <ralf@linux-mips.org>
      2fa36399
  8. 15 5月, 2012 1 次提交
  9. 08 12月, 2011 2 次提交
  10. 19 5月, 2011 1 次提交
  11. 11 1月, 2009 1 次提交
  12. 28 10月, 2008 1 次提交
  13. 11 10月, 2008 1 次提交
  14. 11 7月, 2007 1 次提交
  15. 27 6月, 2007 1 次提交
  16. 26 4月, 2006 1 次提交
  17. 08 11月, 2005 1 次提交
  18. 30 10月, 2005 2 次提交
  19. 05 9月, 2005 1 次提交
  20. 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