All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [V4 1/2] A20-OLinuXino-Lime: new board (mainline)
Date: Sun, 28 Jun 2015 22:24:02 +0200	[thread overview]
Message-ID: <20150628222402.4d3ded80@free-electrons.com> (raw)
In-Reply-To: <559050F1.1030101@lucaceresoli.net>

Dear Luca Ceresoli,

On Sun, 28 Jun 2015 21:54:25 +0200, Luca Ceresoli wrote:


> In fact, we have several Cortex-A defconfigs that enable NEON (5 out of
> 26) and EABIHF (9 out of 26):
> 
> $ git grep -l  cortex_a -- configs/ |wc
>       26      26     878
> $ git grep -l  cortex_a -- configs/ | xargs grep -l EABIHF|wc
>        9       9     308
> $ git grep -l  cortex_a -- configs/ | xargs grep -l NEON|wc
>        5       5     158
> $
> 
> But as I said, my understanding might be wrong.
> 
> Any authoritative opinions on this?

We don't have any strong position on this I believe. From my point of
view, enabling EABIhf definitely makes sense when it is possible. And
enabling NEON support also makes sense. However, using NEON as the FPU
is a bad idea (i.e BR2_ARM_FPU_NEON=y is a bad idea).

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-06-28 20:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-26 10:06 [Buildroot] [V4 0/2] A20-OLinuXino-Lime: new board Francois Perrad
2015-06-26 10:06 ` [Buildroot] [V4 1/2] A20-OLinuXino-Lime: new board (mainline) Francois Perrad
2015-06-26 16:27   ` Luca Ceresoli
2015-06-27  6:58     ` François Perrad
2015-06-28 19:54       ` Luca Ceresoli
2015-06-28 20:24         ` Thomas Petazzoni [this message]
2015-07-07 20:32           ` Arnout Vandecappelle
2015-06-26 10:06 ` [Buildroot] [V4 2/2] A20-OLinuXino-Lime: new board (mali) Francois Perrad
2015-06-28 13:33 ` [Buildroot] [V4 0/2] A20-OLinuXino-Lime: new board Thomas Petazzoni

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=20150628222402.4d3ded80@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.