Thomas Jarosch 079d7fbb8b Revert "PictureFlow: Add move callback for buflib allocations" ... It's not needed as picture flow has it's own buffer. This reverts commit 9076b433d1. Detailed explanation from Thomas Martiz (thanks!): buflib buffers can be passed to yielding functions just fine. Problems only arise if the are concurrent allocations, for example if two threads allocate from the same context simultaneously or if the callee does it's own allocations. This can't happen in the pictureflow case, it has it's own context and a single thread allocating from it. Therefore the problem isn't yield() itself, but possible concurrent buflib_alloc() calls that result from the thread switch. This is because compaction only ever happens on allocation (and not in a backgroud thread or so).		2015-03-01 18:23:17 +01:00
..
pictureflow.c	Revert "PictureFlow: Add move callback for buflib allocations"	2015-03-01 18:23:17 +01:00
pictureflow.make	Refactor and unify objcopy calls in the build system. Also now properly handles DEBUG builds on hosted targets to keep debug symbols if necessary.	2012-04-04 21:48:19 +02:00
SOURCES	Build pictureflow using overlay on lowmem targets, support JPEG AA in PF on all targets.	2009-05-07 01:23:13 +00:00