public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arno@natisbad.org (Arnaud Ebalard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: mvebu: Enable NEON support in defconfig
Date: Thu, 20 Mar 2014 00:44:21 +0100	[thread overview]
Message-ID: <87a9cln48a.fsf@natisbad.org> (raw)
In-Reply-To: <1395268736-13338-1-git-send-email-gregory.clement@free-electrons.com> (Gregory CLEMENT's message of "Wed, 19 Mar 2014 23:38:56 +0100")

Hi Gregory,

Gregory CLEMENT <gregory.clement@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@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+

  reply	other threads:[~2014-03-19 23:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-19 22:38 [PATCH] ARM: mvebu: Enable NEON support in defconfig Gregory CLEMENT
2014-03-19 23:44 ` Arnaud Ebalard [this message]
2014-03-20  0:09   ` Gregory CLEMENT
2014-03-20 13:19 ` Jason Cooper

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a9cln48a.fsf@natisbad.org \
    --to=arno@natisbad.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox