Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] webkitgtk24: use the correct Config.in option for NEON
Date: Fri, 9 Oct 2015 07:33:01 -0300	[thread overview]
Message-ID: <561797DD.3010009@zacarias.com.ar> (raw)
In-Reply-To: <1444382406-16293-1-git-send-email-thomas.petazzoni@free-electrons.com>

On 09/10/15 06:20, Thomas Petazzoni wrote:

> In order to enable JIT support on ARM, webkitgtk24 currently looks at
> BR2_ARM_ENABLE_NEON, which is not correct: BR2_ARM_CPU_HAS_NEON should
> be used instead.
>
> The BR2_ARM_ENABLE_NEON is only visible for cores that select
> BR2_ARM_CPU_MAYBE_HAS_NEON, in order to allow to specify if his
> particular SoC has chosen to integrate NEON or not. And if so,
> BR2_ARM_CPU_HAS_NEON gets selected.
>
> BR2_ARM_CPU_HAS_NEON is in fact selected in two different ways:
>
>   - Either directly by the CPU core selection, if NEON is mandatory in
>     this CPU core.
>
>   - Or by BR2_ARM_ENABLE_NEON, for CPU cores where NEON support is
>     optional.
>
> So really, BR2_ARM_CPU_HAS_NEON is what should be used by packages.
>
> Cc: Gustavo Zacarias <gustavo@zacarias.com.ar>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>

Acked-by: Gustavo Zacarias <gustavo@zacarias.com.ar>

  reply	other threads:[~2015-10-09 10:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-09  9:20 [Buildroot] [PATCH] webkitgtk24: use the correct Config.in option for NEON Thomas Petazzoni
2015-10-09 10:33 ` Gustavo Zacarias [this message]
2015-10-09 13:23 ` 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=561797DD.3010009@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --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