1. 25 Sep, 2008 2 commits
    • Russell King's avatar
      [ARM] Introduce new bitmask based cache type macros · c0e95878
      Russell King authored
      Rather than trying to (inaccurately) decode the cache type from the
      registers each time we need to decide what type of cache we have,
      use a bitmask initialized early during boot.
      
      Since the setup is a one-off initialization, we can be a little more
      clever and take account of the CPU architecture as well.
      
      Note that we continue to achieve the compactness on optimised kernels
      by forcing tests to always-false or always-true as appropriate, thereby
      allowing the compiler to do build-time code elimination.
      Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      c0e95878
    • Russell King's avatar
      [ARM] Remove cache type printks · 90f1e084
      Russell King authored
      The cache type register found in ARMv5 and later CPUs changes format
      and meaning depending on the CPU architecture version.  Currently,
      this code:
      a) doesn't work for everything - Xscale's are identified as
         'unknown 5'.
      b) is not able to tell whether the caches are VIVT or VIPT from the
         cache type.
      c) prints rubbish on some ARMv6 and ARMv7+ CPUs.
      
      The two solutions to this are:
      1. Add yet more code to decode and print the various different register
         formats.
      2. Remove the code altogther.
      
      The code only exists to decode and print the cache parameters.
      Increasing the complexity of it just for the sake of a few prinks
      isn't worth it.
      Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      90f1e084
  2. 17 Sep, 2008 1 commit
  3. 09 Sep, 2008 1 commit
  4. 06 Sep, 2008 8 commits
  5. 05 Sep, 2008 1 commit
    • Russell King's avatar
      [ARM] sparse: fix several warnings · 09d9bae0
      Russell King authored
      arch/arm/kernel/process.c:270:6: warning: symbol 'show_fpregs' was not declared. Should it be static?
      
      This function isn't used, so can be removed.
      
      arch/arm/kernel/setup.c:532:9: warning: symbol 'len' shadows an earlier one
      arch/arm/kernel/setup.c:524:6: originally declared here
      
      A function containing two 'len's.
      
      arch/arm/mm/fault-armv.c:188:13: warning: symbol 'check_writebuffer_bugs' was not declared. Should it be static?
      arch/arm/mm/mmap.c:122:5: warning: symbol 'valid_phys_addr_range' was not declared. Should it be static?
      arch/arm/mm/mmap.c:137:5: warning: symbol 'valid_mmap_phys_addr_range' was not declared. Should it be static?
      
      Missing includes.
      
      arch/arm/kernel/traps.c:71:77: warning: Using plain integer as NULL pointer
      arch/arm/mm/ioremap.c:355:46: error: incompatible types in comparison expression (different address spaces)
      
      Sillies.
      Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      09d9bae0
  6. 01 Sep, 2008 13 commits
  7. 26 Aug, 2008 2 commits
  8. 25 Aug, 2008 12 commits