summaryrefslogtreecommitdiff
path: root/firmware/target/arm
diff options
context:
space:
mode:
authorThomas Jarosch <tomj@simonv.com>2015-03-01 18:20:22 +0100
committerThomas Jarosch <tomj@simonv.com>2015-03-01 18:23:17 +0100
commit079d7fbb8b797c235dd7d4eb292aed6c67677a78 (patch)
tree4577e0729d3b4e534193fb3f48d4551f5263a2ea /firmware/target/arm
parent55f1d9486fcff6ae7af6cac3a0200a996c194c6c (diff)
downloadrockbox-079d7fbb8b797c235dd7d4eb292aed6c67677a78.tar.gz
rockbox-079d7fbb8b797c235dd7d4eb292aed6c67677a78.zip
Revert "PictureFlow: Add move callback for buflib allocations"
It's not needed as picture flow has it's own buffer. This reverts commit 9076b433d18b5db1a1987fe99ca7c70808f22b0e. 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).
Diffstat (limited to 'firmware/target/arm')
0 files changed, 0 insertions, 0 deletions