Skip to contentSkip to conversation

evas: disable cpu neon support for palmpre machine

PATCH In review Simon Busch 5 participants 12 messages Feb 8, 2011 – Mar 1, 2011

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 evas: disable cpu neon support for palmpre machine

Neon support in evas is currently broken for the palmpre machine. If we enable neon support evas causes alignment trap errors and lets the device freeze in the end. This should be reverted after the bug in evas code is found and fixed.

---
 recipes/efl1/evas.inc |    5 ++++-
 1 files changed, 4 insertions(+), 1 deletions(-)
recipes/efl1/evas.inc +4 -1
index eb64d7a..ad30eba 100644
@@ -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 () {
@@ -83,6 +83,9 @@ 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"
 
+# Neon support for evas is broken on palmpre currently (causes the device to freeze)
+EVAS_CPU_TWEAKS_palmpre = "--disable-cpu-neon"
+
 # common options
 EVAS_OECONF = " \
                 --x-includes=${STAGING_INCDIR}/X11 \
Signature · 1 line
1.7.1
#1 lore raw
Quoted 23 lines · Simon Busch

Neon support in evas is currently broken for the palmpre machine. If we enable neon support evas causes alignment trap errors and lets the device freeze in the end. This should be reverted after the bug in evas code is found and fixed.

---
  recipes/efl1/evas.inc |    5 ++++-
  1 files changed, 4 insertions(+), 1 deletions(-)
recipes/efl1/evas.inc +1 -1
index eb64d7a..ad30eba 100644
@@ -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 () {

recipes/efl1/evas.inc EVAS_CPU_TWEAKS = "" · line 91

Quoted 9 lines
recipes/efl1/evas.inc +3 -0
@@ -83,6 +83,9 @@ 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"
 
+# Neon support for evas is broken on palmpre currently (causes the device to freeze)
+EVAS_CPU_TWEAKS_palmpre = "--disable-cpu-neon"
+
  # common options
  EVAS_OECONF = " \
                  --x-includes=${STAGING_INCDIR}/X11 \

Shouldn't this be changing the armv7a EVAS_CPU_TWEAKS that's above yours to be uncommented and as a --disable?

Signature · 2 lines
Tom Rini
Mentor Graphics Corporation
#2 lore raw
Quoted 32 lines · Tom Rini
Quoted 31 lines · Simon Busch

Neon support in evas is currently broken for the palmpre machine. If we enable neon
support evas causes alignment trap errors and lets the device freeze in the end. This
should be reverted after the bug in evas code is found and fixed.

---
 recipes/efl1/evas.inc |    5 ++++-

 1 files changed, 4 insertions(+), 1 deletions(-)
recipes/efl1/evas.inc +0 -0
index eb64d7a..ad30eba 100644
@@ -7,7 +7,7 @@ DEPENDS_virtclass-native = "freetype-native libxext-native

libpng-native jpeg-na
 inherit efl

 BBCLASSEXTEND = "native"

recipes/efl1/evas.inc +1 -1
-INC_PR = "r0"
+INC_PR = "r1"

 FILESPATHPKG =. "${BPN}-${PV}:${BPN}:"

 python populate_packages_prepend () {

recipes/efl1/evas.inc +0 -0
@@ -83,6 +83,9 @@ 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"

Quoted 10 lines
Quoted 7 lines

+# Neon support for evas is broken on palmpre currently (causes the device to freeze)

recipes/efl1/evas.inc +2 -0
+EVAS_CPU_TWEAKS_palmpre = "--disable-cpu-neon"
+
 # common options
 EVAS_OECONF = " \
                 --x-includes=${STAGING_INCDIR}/X11 \

Shouldn't this be changing the armv7a EVAS_CPU_TWEAKS that's above yours to be uncommented and as a --disable?

that would disable neon for all armv7a machines probably not what is needed here. The patch seems ok but I think it will make this recipe machine specific if it already is not on the other hand punishing all armv7 will keep the recipe still generic

Quoted 10 lines

--
Tom Rini
Mentor Graphics Corporation

_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

#3 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 44 lines · Khem Raj
Quoted 32 lines · Tom Rini
Quoted 31 lines · Simon Busch

Neon support in evas is currently broken for the palmpre machine. If we enable neon
support evas causes alignment trap errors and lets the device freeze in the end. This
should be reverted after the bug in evas code is found and fixed.

---
 recipes/efl1/evas.inc |    5 ++++-
 1 files changed, 4 insertions(+), 1 deletions(-)
recipes/efl1/evas.inc +0 -0
index eb64d7a..ad30eba 100644
@@ -7,7 +7,7 @@ DEPENDS_virtclass-native = "freetype-native libxext-native

libpng-native jpeg-na
inherit efl

BBCLASSEXTEND = "native"

recipes/efl1/evas.inc +1 -1
-INC_PR = "r0"
+INC_PR = "r1"
 FILESPATHPKG =. "${BPN}-${PV}:${BPN}:"
 
 python populate_packages_prepend () {
@@ -83,6 +83,9 @@ 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"

Quoted 10 lines

recipes/efl1/evas.inc EVAS_CPU_TWEAKS = "" · line 91

Quoted 7 lines

+# Neon support for evas is broken on palmpre currently (causes the device to freeze)

recipes/efl1/evas.inc +2 -0
+EVAS_CPU_TWEAKS_palmpre = "--disable-cpu-neon"
+
 # common options
 EVAS_OECONF = " \
                 --x-includes=${STAGING_INCDIR}/X11 \

Shouldn't this be changing the armv7a EVAS_CPU_TWEAKS that's above yours to be uncommented and as a --disable?

Quoted 2 lines

that would disable neon for all armv7a machines probably not what is needed here.

Actually, that was how I did it :) The NEON code that was added doesn't build with gcc 4.3.x and binutils 2.18.x, so I disabled it by not enabling it. If it builds and works with gcc 4.3.x nowadays we should enable it and find out why the palmpre breaks.

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFNUtvMMkyGM64RGpERApZsAKCqED8JCVCdRqPtGfZ8gAZ+uCk0swCcD96s 9LMHSgBQMcskY+N/zSOAvc4=
=lI+a
-----END PGP SIGNATURE-----

#4 lore raw
Quoted 48 lines · Koen Kooi

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 44 lines · Khem Raj
Quoted 42 lines · Tom Rini
Quoted 33 lines · Simon Busch

Neon support in evas is currently broken for the palmpre machine. If we enable neon
support evas causes alignment trap errors and lets the device freeze in the end. This
should be reverted after the bug in evas code is found and fixed.

---
 recipes/efl1/evas.inc |    5 ++++-
 1 files changed, 4 insertions(+), 1 deletions(-)
recipes/efl1/evas.inc +0 -0
index eb64d7a..ad30eba 100644
@@ -7,7 +7,7 @@ DEPENDS_virtclass-native = "freetype-native libxext-native

libpng-native jpeg-na
inherit efl

BBCLASSEXTEND = "native"

recipes/efl1/evas.inc +1 -1
-INC_PR = "r0"
+INC_PR = "r1"
 FILESPATHPKG =. "${BPN}-${PV}:${BPN}:"
 
 python populate_packages_prepend () {
@@ -83,6 +83,9 @@ 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"

+# Neon support for evas is broken on palmpre currently (causes the device to freeze)

recipes/efl1/evas.inc EVAS_CPU_TWEAKS = "" · line 91

Quoted 5 lines
recipes/efl1/evas.inc +2 -0
+EVAS_CPU_TWEAKS_palmpre = "--disable-cpu-neon"
+
 # common options
 EVAS_OECONF = " \
                 --x-includes=${STAGING_INCDIR}/X11 \

Shouldn't this be changing the armv7a EVAS_CPU_TWEAKS that's above yours to be uncommented and as a --disable?

Quoted 7 lines
Quoted 2 lines

that would disable neon for all armv7a machines probably not what is needed here.

Actually, that was how I did it :) The NEON code that was added doesn't build with gcc 4.3.x and binutils 2.18.x, so I disabled it by not enabling it. If it builds and works with gcc 4.3.x nowadays we should enable it and find out why the palmpre breaks.

Evas builds fine these days with neon support enabled but it enables it by default. I really need to find the cause of the breakage on the palmpre but don't have too much time to debug it so this is a interim solution only until the bug is found and fixed.

regards,
morphis

#5 lore raw
Quoted 57 lines · Simon Busch
Quoted 48 lines · Koen Kooi

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 44 lines · Khem Raj
Quoted 42 lines · Tom Rini
Quoted 33 lines · Simon Busch

Neon support in evas is currently broken for the palmpre machine. If we enable neon
support evas causes alignment trap errors and lets the device freeze in the end. This
should be reverted after the bug in evas code is found and fixed.

---
  recipes/efl1/evas.inc |    5 ++++-
  1 files changed, 4 insertions(+), 1 deletions(-)
recipes/efl1/evas.inc +0 -0
index eb64d7a..ad30eba 100644
@@ -7,7 +7,7 @@ DEPENDS_virtclass-native = "freetype-native libxext-native

libpng-native jpeg-na
inherit efl

BBCLASSEXTEND = "native"

recipes/efl1/evas.inc +1 -1
-INC_PR = "r0"
+INC_PR = "r1"
  FILESPATHPKG =. "${BPN}-${PV}:${BPN}:"
 
  python populate_packages_prepend () {
@@ -83,6 +83,9 @@ 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"

+# Neon support for evas is broken on palmpre currently (causes the device to freeze)

recipes/efl1/evas.inc EVAS_CPU_TWEAKS = "" · line 91

Quoted 5 lines
recipes/efl1/evas.inc +2 -0
+EVAS_CPU_TWEAKS_palmpre = "--disable-cpu-neon"
+
  # common options
  EVAS_OECONF = " \
                  --x-includes=${STAGING_INCDIR}/X11 \

Shouldn't this be changing the armv7a EVAS_CPU_TWEAKS that's above yours to be uncommented and as a --disable?

Quoted 7 lines
Quoted 2 lines

that would disable neon for all armv7a machines probably not what is needed here.

Actually, that was how I did it :) The NEON code that was added doesn't build with gcc 4.3.x and binutils 2.18.x, so I disabled it by not enabling it. If it builds and works with gcc 4.3.x nowadays we should enable it and find out why the palmpre breaks.

Quoted 4 lines

Evas builds fine these days with neon support enabled but it enables it by default. I really need to find the cause of the breakage on the palmpre but don't have too much time to debug it so this is a interim solution only until the bug is found and fixed.

My only concern is that are we sure other armv7a targets aren't also having fatal problems?

Signature · 2 lines
Tom Rini
Mentor Graphics Corporation
#6 lore raw
Quoted 68 lines · Tom Rini
Quoted 67 lines · Simon Busch
Quoted 64 lines · Koen Kooi

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 52 lines · Khem Raj
Quoted 37 lines · Tom Rini
Quoted 35 lines · Simon Busch

Neon support in evas is currently broken for the palmpre machine. If we
enable neon
support evas causes alignment trap errors and lets the device freeze in
the end. This
should be reverted after the bug in evas code is found and fixed.

---
 recipes/efl1/evas.inc |    5 ++++-

 1 files changed, 4 insertions(+), 1 deletions(-)
recipes/efl1/evas.inc +0 -0
index eb64d7a..ad30eba 100644
@@ -7,7 +7,7 @@ DEPENDS_virtclass-native = "freetype-native

libxext-native
libpng-native jpeg-na
 inherit efl

 BBCLASSEXTEND = "native"

recipes/efl1/evas.inc +1 -1
-INC_PR = "r0"
+INC_PR = "r1"

 FILESPATHPKG =. "${BPN}-${PV}:${BPN}:"

 python populate_packages_prepend () {

recipes/efl1/evas.inc +0 -0
@@ -83,6 +83,9 @@ 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"

Quoted 12 lines
Quoted 8 lines

+# Neon support for evas is broken on palmpre currently (causes the device
to freeze)

recipes/efl1/evas.inc +2 -0
+EVAS_CPU_TWEAKS_palmpre = "--disable-cpu-neon"
+
 # common options
 EVAS_OECONF = " \
                 --x-includes=${STAGING_INCDIR}/X11 \

Shouldn't this be changing the armv7a EVAS_CPU_TWEAKS that's above yours to
be uncommented and as a --disable?

Quoted 2 lines

that would disable neon for all armv7a machines probably not what is needed here.

Actually, that was how I did it :) The NEON code that was added doesn't build with gcc 4.3.x and binutils 2.18.x, so I disabled it by not enabling it. If it builds and works with gcc 4.3.x nowadays we should enable it and find out why the palmpre breaks.

Quoted 5 lines
Quoted 5 lines

Evas builds fine these days with neon support enabled but it enables it by default. I really need to find the cause of the breakage on the palmpre but
don't have too much time to debug it so this is a interim solution only until the bug is found and fixed.

that would be nice because once we add machine override it can become a common escape for other machines
and changing this to be a machine specific recipe is not desired unless absolutely needed

Quoted 3 lines

My only concern is that are we sure other armv7a targets aren't also having fatal problems?

we don't fix what we don't know is broken

Quoted 10 lines

--
Tom Rini
Mentor Graphics Corporation

_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

#7 lore raw
Quoted 81 lines · Khem Raj
Quoted 68 lines · Tom Rini
Quoted 67 lines · Simon Busch
Quoted 64 lines · Koen Kooi

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 52 lines · Khem Raj
Quoted 37 lines · Tom Rini
Quoted 35 lines · Simon Busch

Neon support in evas is currently broken for the palmpre machine. If we
enable neon
support evas causes alignment trap errors and lets the device freeze in
the end. This
should be reverted after the bug in evas code is found and fixed.

---
  recipes/efl1/evas.inc |    5 ++++-
  1 files changed, 4 insertions(+), 1 deletions(-)
recipes/efl1/evas.inc +0 -0
index eb64d7a..ad30eba 100644
@@ -7,7 +7,7 @@ DEPENDS_virtclass-native = "freetype-native

libxext-native
libpng-native jpeg-na
inherit efl

BBCLASSEXTEND = "native"

recipes/efl1/evas.inc +1 -1
-INC_PR = "r0"
+INC_PR = "r1"
  FILESPATHPKG =. "${BPN}-${PV}:${BPN}:"
 
  python populate_packages_prepend () {
@@ -83,6 +83,9 @@ 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"

Quoted 12 lines

recipes/efl1/evas.inc

Quoted 8 lines

+# Neon support for evas is broken on palmpre currently (causes the device
to freeze)

recipes/efl1/evas.inc +2 -0
+EVAS_CPU_TWEAKS_palmpre = "--disable-cpu-neon"
+
  # common options
  EVAS_OECONF = " \
                  --x-includes=${STAGING_INCDIR}/X11 \

Shouldn't this be changing the armv7a EVAS_CPU_TWEAKS that's above yours to
be uncommented and as a --disable?

Quoted 2 lines

that would disable neon for all armv7a machines probably not what is needed here.

Actually, that was how I did it :) The NEON code that was added doesn't build with gcc 4.3.x and binutils 2.18.x, so I disabled it by not enabling it. If it builds and works with gcc 4.3.x nowadays we should enable it and find out why the palmpre breaks.

Quoted 5 lines
Quoted 5 lines

Evas builds fine these days with neon support enabled but it enables it by default. I really need to find the cause of the breakage on the palmpre but
don't have too much time to debug it so this is a interim solution only until the bug is found and fixed.

that would be nice because once we add machine override it can become a common escape for other machines
and changing this to be a machine specific recipe is not desired unless absolutely needed

Quoted 1 line
Quoted 4 lines
Quoted 2 lines

My only concern is that are we sure other armv7a targets aren't also having fatal problems?

we don't fix what we don't know is broken

Right. But it sounds like it shouldn't be too hard to see if it is broken elsewhere :)

Signature · 2 lines
Tom Rini
Mentor Graphics Corporation
#8 lore raw

Am Mittwoch, den 09.02.2011, 16:45 -0700 schrieb Tom Rini:

Quoted 80 lines · Khem Raj
Quoted 79 lines · Tom Rini
Quoted 67 lines · Simon Busch
Quoted 66 lines · Koen Kooi
Quoted 63 lines

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 51 lines · Khem Raj
Quoted 37 lines · Tom Rini
Quoted 35 lines · Simon Busch

Neon support in evas is currently broken for the palmpre machine. If we
enable neon
support evas causes alignment trap errors and lets the device freeze in
the end. This
should be reverted after the bug in evas code is found and fixed.

---
  recipes/efl1/evas.inc |    5 ++++-
  1 files changed, 4 insertions(+), 1 deletions(-)
recipes/efl1/evas.inc +0 -0
index eb64d7a..ad30eba 100644
@@ -7,7 +7,7 @@ DEPENDS_virtclass-native = "freetype-native

libxext-native
libpng-native jpeg-na
inherit efl

BBCLASSEXTEND = "native"

recipes/efl1/evas.inc +1 -1
-INC_PR = "r0"
+INC_PR = "r1"
  FILESPATHPKG =. "${BPN}-${PV}:${BPN}:"
 
  python populate_packages_prepend () {
@@ -83,6 +83,9 @@ 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"

Quoted 11 lines

recipes/efl1/evas.inc

Quoted 7 lines

+# Neon support for evas is broken on palmpre currently (causes the device to freeze)

recipes/efl1/evas.inc +2 -0
+EVAS_CPU_TWEAKS_palmpre = "--disable-cpu-neon"
+
  # common options
  EVAS_OECONF = " \
                  --x-includes=${STAGING_INCDIR}/X11 \

Shouldn't this be changing the armv7a EVAS_CPU_TWEAKS that's above yours to
be uncommented and as a --disable?

Quoted 2 lines

that would disable neon for all armv7a machines probably not what is needed here.

Actually, that was how I did it :) The NEON code that was added doesn't build with gcc 4.3.x and binutils 2.18.x, so I disabled it by not enabling it. If it builds and works with gcc 4.3.x nowadays we should enable it and find out why the palmpre breaks.

Quoted 4 lines
Quoted 4 lines

Evas builds fine these days with neon support enabled but it enables it by default. I really need to find the cause of the breakage on the palmpre but don't have too much time to debug it so this is a interim solution only until the bug is found and fixed.

that would be nice because once we add machine override it can become a common escape for other machines
and changing this to be a machine specific recipe is not desired unless absolutely needed

Quoted 1 line
Quoted 7 lines
Quoted 4 lines
Quoted 2 lines

My only concern is that are we sure other armv7a targets aren't also having fatal problems?

we don't fix what we don't know is broken

Right. But it sounds like it shouldn't be too hard to see if it is broken elsewhere :)

This patch [1] is superseded by Koen’s commit d6729be1 [2].

Thanks,

Paul

[1] http://patches.openembedded.org/patch/497/
[2] http://cgit.openembedded.org/cgit.cgi/openembedded/commit/?id=d6729be1fd7f2e82e7535a854e2aae006aaec5ee

#9 lore raw
Quoted 84 lines · Paul Menzel

Am Mittwoch, den 09.02.2011, 16:45 -0700 schrieb Tom Rini:

Quoted 83 lines · Khem Raj
Quoted 82 lines · Tom Rini
Quoted 67 lines · Simon Busch
Quoted 66 lines · Koen Kooi
Quoted 63 lines

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 51 lines · Khem Raj
Quoted 37 lines · Tom Rini
Quoted 35 lines · Simon Busch

Neon support in evas is currently broken for the palmpre machine. If we
enable neon
support evas causes alignment trap errors and lets the device freeze in
the end. This
should be reverted after the bug in evas code is found and fixed.

---
  recipes/efl1/evas.inc |    5 ++++-
  1 files changed, 4 insertions(+), 1 deletions(-)
recipes/efl1/evas.inc +0 -0
index eb64d7a..ad30eba 100644
@@ -7,7 +7,7 @@ DEPENDS_virtclass-native = "freetype-native

libxext-native
libpng-native jpeg-na
inherit efl

BBCLASSEXTEND = "native"

recipes/efl1/evas.inc +1 -1
-INC_PR = "r0"
+INC_PR = "r1"
  FILESPATHPKG =. "${BPN}-${PV}:${BPN}:"
 
  python populate_packages_prepend () {
@@ -83,6 +83,9 @@ 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"

Quoted 11 lines

recipes/efl1/evas.inc

Quoted 7 lines

+# Neon support for evas is broken on palmpre currently (causes the device to freeze)

recipes/efl1/evas.inc +2 -0
+EVAS_CPU_TWEAKS_palmpre = "--disable-cpu-neon"
+
  # common options
  EVAS_OECONF = " \
                  --x-includes=${STAGING_INCDIR}/X11 \

Shouldn't this be changing the armv7a EVAS_CPU_TWEAKS that's above yours to
be uncommented and as a --disable?

Quoted 2 lines

that would disable neon for all armv7a machines probably not what is needed here.

Actually, that was how I did it :) The NEON code that was added doesn't build with gcc 4.3.x and binutils 2.18.x, so I disabled it by not enabling it. If it builds and works with gcc 4.3.x nowadays we should enable it and find out why the palmpre breaks.

Quoted 4 lines
Quoted 4 lines

Evas builds fine these days with neon support enabled but it enables it by default. I really need to find the cause of the breakage on the palmpre but don't have too much time to debug it so this is a interim solution only until the bug is found and fixed.

that would be nice because once we add machine override it can become a common escape for other machines
and changing this to be a machine specific recipe is not desired unless absolutely needed

Quoted 3 lines

My only concern is that are we sure other armv7a targets aren't also having fatal problems?

Quoted 6 lines
Quoted 4 lines
Quoted 1 line

we don't fix what we don't know is broken

Right. But it sounds like it shouldn't be too hard to see if it is broken elsewhere :)

This patch [1] is superseded by Koen’s commit d6729be1 [2].

I already saw Koen's commit but nevertheless someone should try to find out why Neon makes such troubles on our arm targets.

regards,
SImon

#10 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 87 lines · Simon Busch
Quoted 86 lines · Paul Menzel

Am Mittwoch, den 09.02.2011, 16:45 -0700 schrieb Tom Rini:

Quoted 85 lines · Khem Raj
Quoted 83 lines · Tom Rini
Quoted 67 lines · Simon Busch
Quoted 66 lines · Koen Kooi
Quoted 63 lines

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 51 lines · Khem Raj
Quoted 37 lines · Tom Rini
Quoted 35 lines · Simon Busch

Neon support in evas is currently broken for the palmpre machine. If we
enable neon
support evas causes alignment trap errors and lets the device freeze in
the end. This
should be reverted after the bug in evas code is found and fixed.

---
  recipes/efl1/evas.inc |    5 ++++-
  1 files changed, 4 insertions(+), 1 deletions(-)
recipes/efl1/evas.inc +0 -0
index eb64d7a..ad30eba 100644
@@ -7,7 +7,7 @@ DEPENDS_virtclass-native = "freetype-native

libxext-native
libpng-native jpeg-na
inherit efl

BBCLASSEXTEND = "native"

recipes/efl1/evas.inc +1 -1
-INC_PR = "r0"
+INC_PR = "r1"
  FILESPATHPKG =. "${BPN}-${PV}:${BPN}:"
 
  python populate_packages_prepend () {
@@ -83,6 +83,9 @@ 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"

Quoted 11 lines

recipes/efl1/evas.inc

Quoted 7 lines

+# Neon support for evas is broken on palmpre currently (causes the device to freeze)

recipes/efl1/evas.inc +2 -0
+EVAS_CPU_TWEAKS_palmpre = "--disable-cpu-neon"
+
  # common options
  EVAS_OECONF = " \
                  --x-includes=${STAGING_INCDIR}/X11 \

Shouldn't this be changing the armv7a EVAS_CPU_TWEAKS that's above yours to
be uncommented and as a --disable?

Quoted 2 lines

that would disable neon for all armv7a machines probably not what is needed here.

Actually, that was how I did it :) The NEON code that was added doesn't build with gcc 4.3.x and binutils 2.18.x, so I disabled it by not enabling it. If it builds and works with gcc 4.3.x nowadays we should enable it and find out why the palmpre breaks.

Quoted 4 lines
Quoted 4 lines

Evas builds fine these days with neon support enabled but it enables it by default. I really need to find the cause of the breakage on the palmpre but don't have too much time to debug it so this is a interim solution only until the bug is found and fixed.

that would be nice because once we add machine override it can become a common escape for other machines
and changing this to be a machine specific recipe is not desired unless absolutely needed

Quoted 3 lines

My only concern is that are we sure other armv7a targets aren't also having fatal problems?

we don't fix what we don't know is broken

Quoted 7 lines
Quoted 4 lines
Quoted 2 lines

Right. But it sounds like it shouldn't be too hard to see if it is broken elsewhere :)

This patch [1] is superseded by Koen’s commit d6729be1 [2].

I already saw Koen's commit but nevertheless someone should try to find out why Neon makes such troubles on our arm targets.

In my case, the ASM is written with gcc 4.5 and binutils 2.20 in mind, so the constraints are a bit different, resulting in misrendered buttons. I can't say what your problem with the palm is, probably a buggy kernel.

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFNZhNtMkyGM64RGpERAg/uAJ9pxS8OmICemCcYlbzVMgv8leE3TACgq94Z E4r6Df8nBJOdxstJbOyb+eA=
=6KUG
-----END PGP SIGNATURE-----

#11 lore raw
Quoted 7 lines · Koen Kooi
Quoted 2 lines

I already saw Koen's commit but nevertheless someone should try to find out why Neon makes such troubles on our arm targets.

In my case, the ASM is written with gcc 4.5 and binutils 2.20 in mind, so the constraints are a bit different, resulting in misrendered buttons. I can't say what your problem with the palm is, probably a buggy kernel.

hmm I can have a look at the code if you like.

Signature · 1 line
-Khem