Hi,
On 16 February 2017 at 17:04, Pekka Paalanen
wrote:
> For some background, here is first an explanation of how upstream
> Weston works currently.
I agree with the summary. Must document this somewhere more lasting. :)
Any review comments I haven't replied to I've just snipped for
brevity, a
Hi,
the subject should say "timer", not "hook" I presume.
For some background, here is first an explanation of how upstream
Weston works currently.
weston_output_schedule_repaint() gets called from all over the place,
including as a response to any damage caused. It gets called directly
from re
In preparation for grouping output repaint together where possible,
switch the per-output repaint timer to a global timer which iterates
across all outputs.
This is implemented by storing the absolute time for the next repaint
for each output locally, and maintaining a global timer hook which
iter
