From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] configs: nitrogen*: enable NEON support
Date: Fri, 16 Sep 2016 16:13:44 +0200 [thread overview]
Message-ID: <20160916161344.54fed11e@free-electrons.com> (raw)
In-Reply-To: <20160916130902.23091-1-gary.bisson@boundarydevices.com>
Hello,
On Fri, 16 Sep 2016 15:09:02 +0200, Gary Bisson wrote:
> Signed-off-by: Gary Bisson <gary.bisson@boundarydevices.com>
> ---
> configs/nitrogen6sx_defconfig | 3 +++
> configs/nitrogen6x_defconfig | 3 +++
> configs/nitrogen7_defconfig | 1 +
> 3 files changed, 7 insertions(+)
>
> diff --git a/configs/nitrogen6sx_defconfig b/configs/nitrogen6sx_defconfig
> index bd92f55..1df658b 100644
> --- a/configs/nitrogen6sx_defconfig
> +++ b/configs/nitrogen6sx_defconfig
> @@ -1,6 +1,9 @@
> # architecture
> BR2_arm=y
> BR2_cortex_a9=y
> +BR2_ARM_ENABLE_NEON=y
> +BR2_ARM_ENABLE_VFP=y
> +BR2_ARM_FPU_NEON=y
So, -mfpu=neon here
> +BR2_ARM_ENABLE_NEON=y
> +BR2_ARM_ENABLE_VFP=y
> +BR2_ARM_FPU_NEON=y
And here.
> # system
> BR2_TARGET_GENERIC_GETTY=y
> diff --git a/configs/nitrogen7_defconfig b/configs/nitrogen7_defconfig
> index a8f3b45..adce0fb 100644
> --- a/configs/nitrogen7_defconfig
> +++ b/configs/nitrogen7_defconfig
> @@ -1,6 +1,7 @@
> # architecture
> BR2_arm=y
> BR2_cortex_a7=y
> +BR2_ARM_FPU_NEON_VFPV4=y
But here, -mfpu=neon-vfpv4
Why this difference?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-09-16 14:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 13:09 [Buildroot] [PATCH] configs: nitrogen*: enable NEON support Gary Bisson
2016-09-16 14:13 ` Thomas Petazzoni [this message]
2016-09-16 14:20 ` Gary Bisson
2016-09-16 16:26 ` Thomas Petazzoni
2016-09-16 16:44 ` Gary Bisson
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=20160916161344.54fed11e@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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