From 071ed03ed5d2dc4edc65acfe8ce902ec1f4e1034 Mon Sep 17 00:00:00 2001 From: raster Date: Mon, 30 Aug 2010 06:11:53 +0000 Subject: [PATCH] notes++ git-svn-id: svn+ssh://svn.enlightenment.org/var/svn/e/trunk/evas@51741 7cbeb6ba-43b4-40fd-8cce-4c39aea84d33 --- README.in | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/README.in b/README.in index 95f3a13..1d861f7 100644 --- a/README.in +++ b/README.in @@ -569,6 +569,18 @@ another core in the meantime allowing for higher framerates with software rendering, using more cpu resources that are available on modern multi-core cpu's. +This has been tested on x86 desktop and laptop cpu's with 2 and 4 +cores and it works well, but there seem to be some issues on tested +multi-core ARM platforms like the nvidia tegra2. The source of issue is +unknown but you will notice rendering bugs with missing content or +incorectly drawn content. This requires you also set the environment +variable EVAS_RENDER_MODE to "non-blocking" to enable it at runtime, +as the compile-time enable simply sets up the feature to be ready to +work. The runtime switch actually turns it on. If you don't plan to +use this feature, don't enable it in the build as there is a general +performance hit of maintaining this feature at all, so beware that +enabling it for single core systems will likely take a performance hit. + --enable-pipe-render **DISABLED DUE TO BUGS** this enables a multiple-thread renderer that divides the rendering -- 2.7.4