On Freitag 22 September 2006 06:37, Stefan Lucke wrote: > On Donnerstag 21 September 2006 12:53, Martin Wache wrote: > > Marko Mäkelä schrieb: > > > On Wed, Sep 20, 2006 at 10:20:49AM +0200, Martin Wache wrote: > > >> I would suggest to check what osdMutex is actually protecting, in some > > >> places I really don't know that. So for protecting what is the osdMutex > > >> needed? > > Added some comment on what osdMutex is protecting. > For Action() of cVideoOut, osdMutex is the wrong one, as the existance > and current contend of previous decoded frame has to be protected. > Introduced a separate mutex for that purpose. > > That should fix the hang situation. > > Martin, what is areaMutex for ? > From reading the the code, it is just for serializing calls of YUV() . > So it could be moved to the private section, right ?
Dropped areaMutex, as there was the possibility of loosing a current frame. This is now handled by locking with oldPictureMutex too. I guess I found a way to drop osdMutex from video-dfb.c . That will hopefully fix the reported issue with fading OSD effects too. -- Stefan Lucke _______________________________________________ Softdevice-devel mailing list [email protected] https://lists.berlios.de/mailman/listinfo/softdevice-devel
