1. 22 Apr, 2014 1 commit
  2. 25 Jul, 2012 1 commit
    • Rob Herring's avatar
      ARM: Add fixed PCI i/o mapping · c2794437
      Rob Herring authored
      
      
      This adds a fixed virtual mapping for PCI i/o addresses. The mapping is
      located at the last 2MB of vmalloc region (0xfee00000-0xff000000). 2MB
      is used to align with PMD size, but IO_SPACE_LIMIT is 1MB. The space
      is reserved after .map_io and can be mapped at any time later with
      pci_ioremap_io. Platforms which need early i/o mapping (e.g. for vga
      console) can call pci_map_io_early in their .map_io function.
      
      This has changed completely from the 1st implementation which only
      supported creating the static mapping at .map_io.
      Signed-off-by: default avatarRob Herring <rob.herring@calxeda.com>
      Cc: Russell King <linux@arm.linux.org.uk>
      Acked-by: default avatarNicolas Pitre <nico@linaro.org>
      c2794437
  3. 26 Nov, 2011 1 commit
  4. 27 Jul, 2010 1 commit
    • Linus Walleij's avatar
      ARM: 6225/1: make TCM allocation static and common for all archs · 1dbd30e9
      Linus Walleij authored
      
      
      This changes the TCM handling so that a fixed area is reserved at
      0xfffe0000-0xfffeffff for TCM. This areas is used by XScale but
      XScale does not have TCM so the mechanisms are mutually exclusive.
      
      This change is needed to make TCM detection more dynamic while
      still being able to compile code into it, and is a must for the
      unified ARM goals: the current TCM allocation at different places
      in memory for each machine would be a nightmare if you want to
      compile a single image for more than one machine with TCM so it
      has to be nailed down in one place.
      Signed-off-by: default avatarLinus Walleij <linus.walleij@stericsson.com>
      Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      1dbd30e9
  5. 15 Feb, 2010 1 commit
  6. 30 Jul, 2009 1 commit
  7. 15 Mar, 2009 1 commit
    • Nicolas Pitre's avatar
      [ARM] fixmap support · 5f0fbf9e
      Nicolas Pitre authored
      
      
      This is the minimum fixmap interface expected to be implemented by
      architectures supporting highmem.
      
      We have a second level page table already allocated and covering
      0xfff00000-0xffffffff because the exception vector page is located
      at 0xffff0000, and various cache tricks already use some entries above
      0xffff0000.  Therefore the PTEs covering 0xfff00000-0xfffeffff are free
      to be used.
      
      However the XScale cache flushing code already uses virtual addresses
      between 0xfffe0000 and 0xfffeffff.
      
      So this reserves the 0xfff00000-0xfffdffff range for fixmap stuff.
      
      The Documentation/arm/memory.txt information is updated accordingly,
      including the information about the actual top of DMA memory mapping
      region which didn't match the code.
      Signed-off-by: default avatarNicolas Pitre <nico@marvell.com>
      5f0fbf9e
  8. 17 Nov, 2005 1 commit
    • Russell King's avatar
      [ARM] Fix some corner cases in new mm initialisation · 02b30839
      Russell King authored
      
      
      Document that the VMALLOC_END address must be aligned to 2MB since
      it must align with a PGD boundary.
      
      Allocate the vectors page early so that the flush_cache_all() later
      will cause any dirty cache lines in the direct mapping will be safely
      written back.
      
      Move the flush_cache_all() to the second local_flush_cache_tlb() and
      remove the now redundant first local_flush_cache_tlb().
      Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      02b30839
  9. 16 Apr, 2005 1 commit
    • Linus Torvalds's avatar
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds authored
      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