1. 24 11月, 2014 1 次提交
    • P
      MIPS: Kconfig option to better exercise/debug hybrid FPRs · f4af6fb2
      Paul Burton 提交于
      The hybrid FPR scheme exists to allow for compatibility between existing
      FP32 code and newly compiled FP64A code. Such code should hopefully be
      rare in the real world, and for the moment is difficult to come across.
      All code except that built for the FP64 ABI can correctly execute using
      the hybrid FPR scheme, so debugging the hybrid FPR implementation can
      be eased by forcing all such code to use it. This is undesirable in
      general due to the trap & emulate overhead of the hybrid FPR
      implementation, but is a very useful option to have for debugging.
      Signed-off-by: NPaul Burton <paul.burton@imgtec.com>
      Cc: linux-mips@linux-mips.org
      Cc: Alexander Viro <viro@zeniv.linux.org.uk>
      Cc: linux-fsdevel@vger.kernel.org
      Cc: linux-kernel@vger.kernel.org
      Patchwork: https://patchwork.linux-mips.org/patch/7680/Signed-off-by: NRalf Baechle <ralf@linux-mips.org>
      f4af6fb2
  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. 31 3月, 2014 1 次提交
  4. 30 10月, 2013 1 次提交
  5. 05 7月, 2013 1 次提交
  6. 16 4月, 2012 1 次提交
  7. 25 5月, 2011 1 次提交
  8. 21 1月, 2011 1 次提交
    • D
      kconfig: rename CONFIG_EMBEDDED to CONFIG_EXPERT · 6a108a14
      David Rientjes 提交于
      The meaning of CONFIG_EMBEDDED has long since been obsoleted; the option
      is used to configure any non-standard kernel with a much larger scope than
      only small devices.
      
      This patch renames the option to CONFIG_EXPERT in init/Kconfig and fixes
      references to the option throughout the kernel.  A new CONFIG_EMBEDDED
      option is added that automatically selects CONFIG_EXPERT when enabled and
      can be used in the future to isolate options that should only be
      considered for embedded systems (RISC architectures, SLOB, etc).
      
      Calling the option "EXPERT" more accurately represents its intention: only
      expert users who understand the impact of the configuration changes they
      are making should enable it.
      Reviewed-by: NIngo Molnar <mingo@elte.hu>
      Acked-by: NDavid Woodhouse <david.woodhouse@intel.com>
      Signed-off-by: NDavid Rientjes <rientjes@google.com>
      Cc: Greg KH <gregkh@suse.de>
      Cc: "David S. Miller" <davem@davemloft.net>
      Cc: Jens Axboe <axboe@kernel.dk>
      Cc: Arnd Bergmann <arnd@arndb.de>
      Cc: Robin Holt <holt@sgi.com>
      Cc: <linux-arch@vger.kernel.org>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      6a108a14
  9. 30 10月, 2010 1 次提交
  10. 27 2月, 2010 2 次提交
  11. 17 12月, 2009 2 次提交
  12. 13 12月, 2008 1 次提交
  13. 31 7月, 2008 1 次提交
  14. 29 4月, 2008 1 次提交
  15. 23 10月, 2007 1 次提交
  16. 06 7月, 2007 1 次提交
  17. 27 2月, 2007 1 次提交
  18. 20 2月, 2007 1 次提交
  19. 07 2月, 2007 1 次提交
  20. 14 7月, 2006 1 次提交
  21. 27 4月, 2006 1 次提交
  22. 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