evas: disable NEON forcefully, it is still causing misrendering when enabled

Upstream changed the default for NEON from disabled to enabled, so the recipe has to catch up

Tested with angstrom 2008.1 on a beagleboard C4

Signed-off-by: Koen Kooi <koen@openembedded.org>

diff --git a/recipes/efl1/evas.inc b/recipes/efl1/evas.inc
index eb64d7a..bcb1984 100644 (file)
--- a/recipes/efl1/evas.inc
+++ b/recipes/efl1/evas.inc
@@ -7,7 +7,7 @@ DEPENDS_virtclass-native = "freetype-native libxext-native libpng-native jpeg-na
 inherit efl
 
 BBCLASSEXTEND = "native"
-INC_PR = "r0"
+INC_PR = "r1"
 FILESPATHPKG =. "${BPN}-${PV}:${BPN}:"
 
 python populate_packages_prepend () {
@@ -81,7 +81,7 @@ RREPLACES_evas-engine-software-x11 = "liblibevas-ver-pre-svn-00-engine-software-
 
 EVAS_CPU_TWEAKS = ""
 # Disabled for now, see http://thread.gmane.org/gmane.comp.window-managers.enlightenment.devel/25194
-#EVAS_CPU_TWEAKS_armv7a = "--enable-cpu-neon"
+EVAS_CPU_TWEAKS_armv7a = "--disable-cpu-neon"
 
 # common options
 EVAS_OECONF = " \