1. 24 7月, 2009 1 次提交
  2. 03 6月, 2009 1 次提交
  3. 30 5月, 2009 5 次提交
  4. 01 5月, 2009 3 次提交
  5. 28 4月, 2009 1 次提交
  6. 10 11月, 2008 1 次提交
  7. 07 11月, 2008 1 次提交
  8. 06 11月, 2008 2 次提交
  9. 23 10月, 2008 1 次提交
  10. 03 10月, 2008 1 次提交
  11. 01 10月, 2008 4 次提交
  12. 01 9月, 2008 1 次提交
  13. 24 4月, 2008 1 次提交
  14. 19 4月, 2008 1 次提交
  15. 21 7月, 2007 2 次提交
  16. 30 5月, 2007 1 次提交
  17. 09 5月, 2007 1 次提交
  18. 15 2月, 2007 1 次提交
  19. 09 2月, 2007 1 次提交
  20. 13 12月, 2006 1 次提交
    • R
      [ARM] Unuse another Linux PTE bit · ad1ae2fe
      Russell King 提交于
      L_PTE_ASID is not really required to be stored in every PTE, since we
      can identify it via the address passed to set_pte_at().  So, create
      set_pte_ext() which takes the address of the PTE to set, the Linux
      PTE value, and the additional CPU PTE bits which aren't encoded in
      the Linux PTE value.
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      ad1ae2fe
  21. 09 12月, 2006 2 次提交
  22. 30 11月, 2006 1 次提交
  23. 30 6月, 2006 1 次提交
    • R
      [ARM] Set bit 4 on section mappings correctly depending on CPU · 8799ee9f
      Russell King 提交于
      On some CPUs, bit 4 of section mappings means "update the
      cache when written to".  On others, this bit is required to
      be one, and others it's required to be zero.  Finally, on
      ARMv6 and above, setting it turns on "no execute" and prevents
      speculative prefetches.
      
      With all these combinations, no one value fits all CPUs, so we
      have to pick a value depending on the CPU type, and the area
      we're mapping.
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      8799ee9f
  24. 29 6月, 2006 2 次提交
    • R
      [ARM] nommu: provide a way for correct control register value selection · 22b19086
      Russell King 提交于
      Most MMU-based CPUs have a restriction on the setting of the data cache
      enable and mmu enable bits in the control register, whereby if the data
      cache is enabled, the MMU must also be enabled.  Enabling the data
      cache without the MMU is an invalid combination.
      
      However, there are CPUs where the data cache can be enabled without the
      MMU.
      
      In order to allow these CPUs to take advantage of that, provide a
      method whereby each proc-*.S file defines the control regsiter value
      for use with nommu (with the MMU disabled.)  Later on, when we add
      support for enabling the MMU on these devices, we can adjust the
      "crval" macro to also enable the data cache for nommu.
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      22b19086
    • H
      [ARM] nommu: Initial uCLinux support for MMU-based CPUs · d090ddda
      Hyok S. Choi 提交于
      In noMMU mode, various of functions which are defined in mm/proc-*.S
      is not valid or needed to be avoided. i.g. switch_mm is not needed,
      just returns and this makes the I & D caches are valid which shows
      great improvement of performance including task switching and IPC.
      Signed-off-by: NHyok S. Choi <hyok.choi@samsung.com>
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      d090ddda
  25. 25 6月, 2006 1 次提交
  26. 27 3月, 2006 1 次提交
  27. 22 3月, 2006 1 次提交