From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] target options for Cortex A8/A9
Date: Sun, 1 Feb 2015 21:48:46 +0100 [thread overview]
Message-ID: <20150201214846.52ebad82@free-electrons.com> (raw)
In-Reply-To: <8F194C039449403C9E9AFFB360BCF394@JohanW7>
Dear Sagaert Johan,
On Sun, 1 Feb 2015 20:51:48 +0100, Sagaert Johan wrote:
> I am using imx53, this cpu has according to the datasheet an NEON SIMD media accelerator
> and an VFPv3 co-processor.
> So I would assume the same selections options as for the A9.
> I was wondering what makes the target options different for A8 vs A9.
>
> I would think that for the imx53 it sould be the same as for the A9,
> That is an NEON SIMD extension and a vfpv3 floating point engine.
> Please clarify, it is a bit confusing to me.
>
> For the A8 I can select vfpv3 OR Neon, but not vfpv3 WITH NEON extension.
On Cortex-A8, NEON is mandatory. On Cortex-A9, NEON is optional. So
when you activate Cortex-A8, Buildroot knows NEON is available. When
you activate Cortex-A9, since NEON is optional, you have to tell
Buildroot if NEON is actually available or not.
See arch/Config.in.arm:
config BR2_cortex_a8
bool "cortex-A8"
select BR2_ARM_CPU_HAS_NEON
select BR2_ARM_CPU_HAS_VFPV3
select BR2_ARM_CPU_HAS_THUMB2
select BR2_ARM_CPU_ARMV7A
config BR2_cortex_a9
bool "cortex-A9"
select BR2_ARM_CPU_MAYBE_HAS_NEON
select BR2_ARM_CPU_MAYBE_HAS_VFPV3
select BR2_ARM_CPU_HAS_THUMB2
select BR2_ARM_CPU_ARMV7A
Note the difference between BR2_ARM_CPU_HAS_NEON for Cortex-A8 and
BR2_ARM_CPU_MAYBE_HAS_NEON for Cortex-A9.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-02-01 20:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-01 19:51 [Buildroot] target options for Cortex A8/A9 Sagaert Johan
2015-02-01 20:48 ` Thomas Petazzoni [this message]
2015-02-02 13:58 ` Sagaert Johan
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=20150201214846.52ebad82@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