1. 31 May, 2014 1 commit
  2. 29 Oct, 2013 1 commit
  3. 12 Oct, 2012 1 commit
  4. 29 Jul, 2012 1 commit
  5. 13 Dec, 2011 1 commit
  6. 22 Jul, 2011 1 commit
  7. 07 Jul, 2011 1 commit
  8. 23 May, 2011 1 commit
    • Grant Likely's avatar
      arm/dt: probe for platforms via the device tree · 93c02ab4
      Grant Likely authored
      
      
      If a dtb is passed to the kernel then the kernel needs to iterate
      through compiled-in mdescs looking for one that matches and move the
      dtb data to a safe location before it gets accidentally overwritten by
      the kernel.
      
      This patch creates a new function, setup_machine_fdt() which is
      analogous to the setup_machine_atags() created in the previous patch.
      It does all the early setup needed to use a device tree machine
      description.
      
      v5: - Print warning with neither dtb nor atags are passed to the kernel
          - Fix bug in setting of __machine_arch_type to the selected machine,
            not just the last machine in the list.
      Reported-by: default avatarTixy <tixy@yxit.co.uk>
          - Copy command line directly into boot_command_line instead of cmd_line
      v4: - Dump some output when a matching machine_desc cannot be found
      v3: - Added processing of reserved list.
          - Backed out the v2 change that copied instead of reserved the
            dtb.  dtb is reserved again and the real problem was fixed by
            using alloc_bootmem_align() for early allocation of RAM for
            unflattening the tree.
          - Moved cmd_line and initrd changes to earlier patch to make series
            bisectable.
      v2: Changed to save the dtb by copying into an allocated buffer.
          - Since the dtb will very likely be passed in the first 16k of ram
            where the interrupt vectors live, memblock_reserve() is
            insufficient to protect the dtb data.
      
      [based on work originally written by Jeremy Kerr <jeremy.kerr@canonical.com>]
      Tested-by: default avatarTony Lindgren <tony@atomide.com>
      Acked-by: default avatarNicolas Pitre <nicolas.pitre@linaro.org>
      Acked-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      Signed-off-by: default avatarGrant Likely <grant.likely@secretlab.ca>
      93c02ab4
  9. 11 May, 2011 1 commit
  10. 21 Feb, 2011 1 commit
  11. 24 Jan, 2011 1 commit
  12. 16 Jul, 2010 1 commit
  13. 15 Feb, 2010 1 commit
  14. 15 Aug, 2009 1 commit
    • Russell King's avatar
      ARM: Fix broken highmem support · dde5828f
      Russell King authored
      Currently, highmem is selectable, and you can request an increased
      vmalloc area.  However, none of this has any effect on the memory
      layout since a patch in the highmem series was accidentally dropped.
      Moreover, even if you did want highmem, all memory would still be
      registered as lowmem, possibly resulting in overflow of the available
      virtual mapping space.
      
      The highmem boundary is determined by the highest allowed beginning
      of the vmalloc area, which depends on its configurable minimum size
      (see commit 60296c71 for details on
      this).
      
      We should create mappings and initialize bootmem only for low memory,
      while the zone allocator must still be told about highmem.
      
      Currently, memory nodes which are completely located in high memory
      are not supported.  This is not a huge limitation since systems
      relying on highmem support are unlikely to have discontiguous memory
      with large holes.
      
      [ A similar patch was meant to be merged before commit 5f0fbf9e
      
      
        and be available  in Linux v2.6.30, however some git rebase screw-up
        of mine dropped the first commit of the series, and that goofage
        escaped testing somehow as well. -- Nico ]
      Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      Reviewed-by: default avatarNicolas Pitre <nico@marvell.com>
      dde5828f
  15. 31 Jan, 2009 1 commit
  16. 28 Nov, 2008 1 commit
    • Nicolas Pitre's avatar
      [ARM] rationalize memory configuration code some more · 4b5f32ce
      Nicolas Pitre authored
      
      
      Currently there are two instances of struct meminfo: one in
      kernel/setup.c marked __initdata, and another in mm/init.c with
      permanent storage.  Let's keep only the later to directly populate
      the permanent version from arm_add_memory().
      
      Also move common validation tests between the MMU and non-MMU cases
      into arm_add_memory() to remove some duplication.  Protection against
      overflowing the membank array is also moved in there in order to cover
      the kernel cmdline parsing path as well.
      Signed-off-by: default avatarNicolas Pitre <nico@marvell.com>
      Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      4b5f32ce
  17. 01 Oct, 2008 1 commit
  18. 02 Aug, 2008 1 commit
  19. 30 May, 2007 1 commit
  20. 07 Dec, 2006 1 commit
  21. 27 Sep, 2006 1 commit
  22. 20 Sep, 2005 2 commits
  23. 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