From cace333876b12c0c6c022bee0ab64a04d455ba16 Mon Sep 17 00:00:00 2001 From: Andreas Volz Date: Tue, 21 Aug 2007 17:56:51 +0000 Subject: [PATCH] two small typo SVN revision: 31447 --- legacy/evas/README.in | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/legacy/evas/README.in b/legacy/evas/README.in index 2973888117..cc9016637a 100644 --- a/legacy/evas/README.in +++ b/legacy/evas/README.in @@ -108,7 +108,7 @@ libraries. For the test programs, XCBICCCM is also needed. --enable-fb -this is the software framebuffer drivign engine. this uses the linxu +this is the software framebuffer drivign engine. this uses the linux framebuffer device (/dev/fb) and will currently just inherit the current framebuffer settings on the fb device and use them to run in. this engine is almost fully functional except for the fb management itself. i'd be quite @@ -150,7 +150,7 @@ considerable speedups, souse it if you can. ppc owners just have to live with the c fallback functions unfortunately as no one has provided any ALTIVEC asm routines yet. :) arm owners will also have to rely on the c fallback routines as i haven't managed to come up with any arm assembly that actually -can beat the c code (when compiled whht all optimisations) in speed. +can beat the c code (when compiled with all optimisations) in speed. --enable-cpu-sse