[PATCH] ARM: mvebu: Enable NEON support in defconfig
Arnaud Ebalard
arno at natisbad.org
Wed Mar 19 19:44:21 EDT 2014
Hi Gregory,
Gregory CLEMENT <gregory.clement at free-electrons.com> writes:
> CONFIG_NEON is no more turning on unconditionally when Armada 375 or
> Armada 38x are selected. However we still want it selected for the
> reference configuration.
>
> Signed-off-by: Gregory CLEMENT <gregory.clement at free-electrons.com>
> ---
> arch/arm/configs/mvebu_v7_defconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm/configs/mvebu_v7_defconfig b/arch/arm/configs/mvebu_v7_defconfig
> index 62b6a37626c5..36797dbfa610 100644
> --- a/arch/arm/configs/mvebu_v7_defconfig
> +++ b/arch/arm/configs/mvebu_v7_defconfig
> @@ -26,6 +26,7 @@ CONFIG_ZBOOT_ROM_BSS=0x0
> CONFIG_ARM_APPENDED_DTB=y
> CONFIG_ARM_ATAG_DTB_COMPAT=y
> CONFIG_VFP=y
> +CONFIG_NEON=y
> CONFIG_NET=y
> CONFIG_INET=y
> CONFIG_BT=y
Will the lack of support by the hardware be detected automatically
(Armada 370 does not have neon support for instance)? Or does the
logic relies on the fact that CONFIG_KERNEL_MODE_NEON is disabled?
Cheers,
a+
More information about the linux-arm-kernel
mailing list