[cairo] gallium surface still maintained ?
guillerodriguez.dev at gmail.com
Fri Aug 5 09:38:46 UTC 2016
2016-08-05 11:00 GMT+02:00 Enrico Weigelt, metux IT consult <
enrico.weigelt at gr13.net>:
> On 05.08.2016 10:35, Enrico Weigelt, metux IT consult wrote:
> Oh, could you check whether your driver sets DRM_CAP_DUMB_PREFER_SHADOW.
> On my box (w/ an i915) the driver sets this flag, so I'll have to assume
> that writing individual bytes going to be slow, and a shadow buffer
> should be used, which then is copied over in bursts.
The driver I am using does not set that flag.
Anyway my application does all compositing on a back (shadow) buffer, and
then blits dirty regions to the DRM buffer.
> Now the interesting question: how to archieve that ?
> Is there some easy way to trace which pixels/regions in a image surface
> have been touched ?
I keep track of dirty regions which are merged together using a naive
algorithm: The resulting dirty region is just a rectangle that encloses all
dirty rectangles. That is then blitted to the screen in each update cycle.
This merging algorithm is obviously inefficient in some cases. For example
let's say you have two small dirty regions in opposite corners of the
screen; the merged dirty region will be large, and blitting that will be
less efficient than blitting the two original dirty regions. You could
optimize this by applying some heuristics in order to decide when to merge
and when not to merge, but I haven't found the need to do that yet.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the cairo