Re: [E-devel] Edje on arm embedded device

[Cedric B. <ced...@fr...>]

On Monday 17 December 2007 13:39:16 Gustavo Sverzut Barbieri wrote:
> On Dec 17, 2007 6:13 AM, mario <dod...@gm...> wrote:
> > On Dec 16, 2007 11:04 PM, Gustavo Sverzut Barbieri <bar...@gm...> 
wrote:
> > > > I'm still working on my arm board:
> > > > All it's ok evas_fb_test run perfectly.
> > > >
> > > > Now I'm working on edje: there is a problem in a simple program:
> > >
> > > Mario, it works great on Nokia devices (arm1136jf-s and arm926ej-s), I
> > > never tried with fb engine, just software_16_x11 and software_x11, but
> > > I can't see how can this change things.
> >
> > Solved.
> > I used an old (August) version of edje taken from
> > http://download.enlightenment.org/snapshots/
> > Now I'm using the code from cvs and all it's ok....
> >
> > ok but slow :(
> > better than qtopia but still slow!
> > next step: try the software16 engine over kdrive to see if something is
> > better. ... even if kdrive seems to be impossibile to compile.
>
> Please, try to write a fb_16 using software_16 as base. I can give you
> some hints, but if you know the fb you are working with, just try to
> write a dummy engine that does some output, then put software_16 as
> the base, look at software_16_x11, the general idea is:
>    - create engine info
>    - implement drawing functions to be the software_16
>    - implement output_redraws_next_update_get() [possible almost the
> same!] to get surface that primitives will draw to. See below.
>    - implement output_redraws_next_update_push(): Mark somewhere
> regions that were dirtied, or send them to display. See below.
>    - implement output_flush(): If it's cheaper to send all updates in
> one go, send marked regions here. Free resources reserved to draw this
> frame.

It shouldn't be too hard to code a fb engine using 16bpp support. But if you 
want, I could provide you an update version of my engine sdl 16bpp engine. 
You should have exactly the same performance, with just some memory overhead.
	A 16bpp should provide you some speed improvement (between 10 to 20% speed 
increase). As I don't know much about your board nor your application, doing 
some oprofile on your board could provide you with some interesting 
information. For example, Edje use float, and if your CPU don't have a FPU, 
you could loss a lot of time in soft float (In some case more than 25% is 
possible).

Hope, this could help you,
	Cedric