On Wed, 2 Jun 2010 16:35:32 +0800 Brett Nash <n...@nash.id.au> said: > On Wed, 2 Jun 2010 09:39:30 +0200 > Benjamin Zores <b...@geexbox.org> wrote: > > > On Wed, Jun 2, 2010 at 9:23 AM, Carsten Haitzler > > <ras...@rasterman.com> wrote: > > > > > async != neon. neon requires a --enable. async rendering wont help > > > you unless you have more than 1 core. and yes - it needs an env var > > > set. its in the README. > > > > Yeah I'm fully aware of that. > > Though, as I used the enable-neon flag, that configures confirmed that > > and that *_neon.c files gets compiled in, I can't see a reason why it > > wouldn't be used, as pointed by Brett. > > Can you rebuild with it disabled, and try against the non-neonized evas? > > I just was expecting some better numbers... but without a baseline they > are bit meaningless.
the soc you have has a much better memory subsystem/ram from what i gather - so clockrate isn't the real factor here thats making the difference between the 2 soc's -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ras...@rasterman.com ------------------------------------------------------------------------------ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
