From d6729be1fd7f2e82e7535a854e2aae006aaec5ee Mon Sep 17 00:00:00 2001 From: Koen Kooi Date: Wed, 23 Feb 2011 10:06:15 +0100 Subject: 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 --- recipes/efl1/evas.inc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'recipes/efl1') diff --git a/recipes/efl1/evas.inc b/recipes/efl1/evas.inc index eb64d7a060..bcb19849b1 100644 --- 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 = " \ -- cgit 1.2.3-korg