Rob Shortt wrote: > First draft of directfb output for Mevas. This "works" but it is > pretty slow because all image operations are done in software and > are only memcpyed to the directfb surface.
Yes and no. I didn't try it, but it looks very slow:
| data = img.get_raw_data("BGRA")
| self._surface.overlay(DSPF_ARGB, str(data))
| self._surface.flip()
This involves more than one memcpy because the data is converted to
python strings and copied again and again. There are two ways to make
it faster: add support for directfb in imlib2 like we have it for
pygame. With that you can memcpy without any python code. Or put some
imlib2 code in directfb to do the same. When I have some time I try to
play with it.
> -Add a directfb imagelib backend to take full advantages of the hw
> accell directfb lets us do.
That would be the way to go. But when you do that, we get a new
problem with having two image backends. E.g. you use directfb and
start mplayer with bmovl2. bmovl2 needs imlib2 as imagelib, so we must
transform data between backend changes.
Dischi
--
panic ("No CPUs found. System halted.\n");
2.4.3 linux/arch/parisc/kernel/setup.c
pgpyZ8YyaH8kr.pgp
Description: PGP signature
