Quoting Alex SONG ([EMAIL PROTECTED]): > hi, > > i am currently working on the DFB savage driver and i would like to see > how it performs. i am currently running df_layer with an mpeg1 file and i > changed df_layer to use a YV12 surface in stead of YUY2 to test the savage > driver overlays. > > i am very new to profiling and its techniques and currently i am just > using top to see how much cpu it uses. when i run df_layer 7 pids show up > so i assume this is the different threads for everything. i sprinkled some > printfs over the directfb code and i found out that there is a process for > main, keyboard events, mouse events, libmpeg3 video, libmpeg3 audio and i > can't figure out what the other two threads are. i placed printf's at > every function registered by pthread_create. any ideas any one ?
libpthread uses one manager thread. The last thread may be the second mouse device? > also has anyone turned on the profiling flags in gcc with directfb ? does > it work ? i have not used the profiling features of gcc before. I had to link an application statically after compiling directfb with profiling support. "CFLAGS=-pg ./autogen.sh --enable-static" should work. > btw, i got YUY2, UYVY and YV12/I420 overlays to work with the DFB savage > driver. Good news, did you look at the "dfb_layers_hook_primary" function. You can replace the implementation of the primary layer completely to implement the features of the savage streams. -- Best regards, Denis Oliver Kropp .------------------------------------------. | DirectFB - Hardware accelerated graphics | | http://www.directfb.org/ | "------------------------------------------" Convergence GmbH -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe directfb-dev" as subject.
