[PATCH v2 22/23] ARM: config: Add mvebu_v5_defconfig
From: Ezequiel Garcia <hidden>
Date: 2014-02-21 01:19:02
Andrew, On Sat, Feb 15, 2014 at 11:20:20AM +0100, Andrew Lunn wrote:
quoted hunk ↗ jump to hunk
Now that there is both v5 and v7 systems in mach-mvebu, the mvebu_defconfig is not sufficient, since these systems cannot be combined. Add a v5 defconfig which is based on kirkwood_defconfig, but purely DT. Signed-off-by: Andrew Lunn <andrew@lunn.ch> --- arch/arm/configs/mvebu_v5_defconfig | 166 ++++++++++++++++++++++++++++++++++++ 1 file changed, 166 insertions(+) create mode 100644 arch/arm/configs/mvebu_v5_defconfigdiff --git a/arch/arm/configs/mvebu_v5_defconfig b/arch/arm/configs/mvebu_v5_defconfig new file mode 100644 index 000000000000..42e4ec641b4c --- /dev/null +++ b/arch/arm/configs/mvebu_v5_defconfig@@ -0,0 +1,166 @@ +CONFIG_SYSVIPC=y +CONFIG_NO_HZ=y +CONFIG_HIGH_RES_TIMERS=y +CONFIG_LOG_BUF_SHIFT=19 +CONFIG_PROFILING=y +CONFIG_OPROFILE=y
You're missing CONFIG_ORION_WATCHDOG=y, probably because it doesn't build in v3.14-rc1 on ARCH_MVEBU. I think it's safe to add it to the defconfig, so once the watchdog MVEBU changes are merged, it'll get selected. -- Ezequiel Garc?a, Free Electrons Embedded Linux, Kernel and Android Engineering http://free-electrons.com