1. 15 4月, 2013 3 次提交
  2. 18 3月, 2013 1 次提交
    • T
      arm: plat-orion: only build addr-map.c when needed · efaaa98d
      Thomas Petazzoni 提交于
      -flagmail-match: MVEBU
      X-flagmail-match: KIRKWOOD
      X-flagmail-match: DOVE
      
      For now, addr-map.c is needed by all 5 Marvell EBU
      sub-architectures. However, we are going to introduce the orion-mbus
      driver, which will replace the address decoding code from
      addr-map.c. In order to ease the migration process, we will do that
      one sub-architecture at a time, which will require us to remove the
      compilation of addr-map.c one sub-architecture at a time.
      
      Therefore, we split the unconditional obj-y inclusion of addr-map.c
      into 5 conditionals obj-$(CONFIG_...) lines, one per sub-architecture.
      Signed-off-by: NThomas Petazzoni <thomas.petazzoni@free-electrons.com>
      Signed-off-by: NJason Cooper <jason@lakedaemon.net>
      efaaa98d
  3. 29 9月, 2012 1 次提交
  4. 22 9月, 2012 1 次提交
    • T
      arm: plat-orion: introduce PLAT_ORION_LEGACY hidden config option · abcda1dc
      Thomas Petazzoni 提交于
      Until now, the PLAT_ORION configuration option was common to all the
      Marvell EBU SoCs, and selecting this option had the effect of enabling
      the MPP code, GPIO code, address decoding and PCIe code from
      plat-orion, as well as providing access to driver-specific header
      files from plat-orion/include.
      
      However, the Armada 370 and XP SoCs will not use the MPP and GPIO code
      (instead some proper pinctrl and gpio drivers are in preparation), and
      generally, we want to move away from plat-orion and instead have
      everything in mach-mvebu.
      
      That said, in the mean time, we want to leverage the driver-specific
      headers as well as the address decoding code, so we introduce
      PLAT_ORION_LEGACY. The older Marvell SoCs need to select
      PLAT_ORION_LEGACY, while the newer Marvell SoCs need to select
      PLAT_ORION. Of course, when PLAT_ORION_LEGACY is selected, it
      automatically selects PLAT_ORION.
      
      Then, with just PLAT_ORION, you have the address decoding code plus
      the driver-specific headers. If you add PLAT_ORION_LEGACY to this, you
      gain the old MPP, GPIO and PCIe code.
      
      Again, this is only a temporary solution until we make all Marvell EBU
      platforms converge into the mach-mvebu directory. This solution avoids
      duplicating the existing address decoding code into mach-mvebu.
      Signed-off-by: NThomas Petazzoni <thomas.petazzoni@free-electrons.com>
      Acked-by: NGregory CLEMENT <gregory.clement@free-electrons.com>
      Acked-by: NArnd Bergmann <arnd@arndb.de>
      Tested-by: NAndrew Lunn <andrew@lunn.ch>
      Signed-off-by: NJason Cooper <jason@lakedaemon.net>
      abcda1dc
  5. 14 12月, 2011 1 次提交
  6. 17 5月, 2011 2 次提交
  7. 21 12月, 2008 1 次提交
  8. 28 3月, 2008 4 次提交
  9. 11 10月, 2007 1 次提交
  10. 25 2月, 2006 1 次提交
    • Z
      [PATCH] Fix topology.c location · 9c869eda
      Zachary Amsden 提交于
      When compiling a non-default subarch, topology.c is missing from the kernel
      build.  This causes builds with CONFIG_HOTPLUG_CPU to fail.  In addition,
      on Intel processors with cpuid level > 4, it causes intel_cacheinfo.c to
      reference uninitialized data that should have been set up by the initcall
      in topology.c which calls register_cpu.  This causes a kernel panic on boot
      on newer Intel processors.  Moving topology.c to arch/i386/kernel fixes
      both of these problems.
      
      Thanks to Dan Hecht for finding and fixing this problem.
      Signed-off-by: NZachary Amsden <zach@vmware.com>
      Signed-off-by: NDan Hecht <dhect@vmware.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      9c869eda
  11. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      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