1. 10 Jul, 2007 7 commits
  2. 26 Jun, 2007 2 commits
  3. 06 Jun, 2007 1 commit
  4. 11 May, 2007 6 commits
  5. 08 May, 2007 1 commit
  6. 07 May, 2007 2 commits
  7. 27 Apr, 2007 5 commits
  8. 29 Mar, 2007 1 commit
  9. 19 Mar, 2007 1 commit
  10. 16 Mar, 2007 2 commits
  11. 13 Mar, 2007 1 commit
  12. 06 Mar, 2007 1 commit
  13. 04 Mar, 2007 2 commits
  14. 26 Feb, 2007 1 commit
  15. 21 Feb, 2007 1 commit
    • Franck Bui-Huu's avatar
      [MIPS] Add basic SMARTMIPS ASE support · 9693a853
      Franck Bui-Huu authored
      
      
      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: default avatarFranck Bui-Huu <fbuihuu@gmail.com>
      Signed-off-by: default avatarRalf Baechle <ralf@linux-mips.org>
      9693a853
  16. 19 Feb, 2007 1 commit
  17. 18 Feb, 2007 1 commit
  18. 13 Feb, 2007 1 commit
  19. 11 Feb, 2007 1 commit
    • Christoph Lameter's avatar
      [PATCH] Set CONFIG_ZONE_DMA for arches with GENERIC_ISA_DMA · 5ac6da66
      Christoph Lameter authored
      
      
      As Andi pointed out: CONFIG_GENERIC_ISA_DMA only disables the ISA DMA
      channel management.  Other functionality may still expect GFP_DMA to
      provide memory below 16M.  So we need to make sure that CONFIG_ZONE_DMA is
      set independent of CONFIG_GENERIC_ISA_DMA.  Undo the modifications to
      mm/Kconfig where we made ZONE_DMA dependent on GENERIC_ISA_DMA and set
      theses explicitly in each arches Kconfig.
      
      Reviews must occur for each arch in order to determine if ZONE_DMA can be
      switched off.  It can only be switched off if we know that all devices
      supported by a platform are capable of performing DMA transfers to all of
      memory (Some arches already support this: uml, avr32, sh sh64, parisc and
      IA64/Altix).
      
      In order to switch ZONE_DMA off conditionally, one would have to establish
      a scheme by which one can assure that no drivers are enabled that are only
      capable of doing I/O to a part of memory, or one needs to provide an
      alternate means of performing an allocation from a specific range of memory
      (like provided by alloc_pages_range()) and insure that all drivers use that
      call.  In that case the arches alloc_dma_coherent() may need to be modified
      to call alloc_pages_range() instead of relying on GFP_DMA.
      Signed-off-by: default avatarChristoph Lameter <clameter@sgi.com>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      5ac6da66
  20. 10 Feb, 2007 1 commit
  21. 09 Feb, 2007 1 commit