On Tuesday, October 23, 2007 10:03 am Jesse Barnes wrote:
> On Tuesday, October 23, 2007 7:32 am Michel Dänzer wrote:
> > > Thinking about this more, I think we can make the counter not
> > > decrease, but I don't think we can avoid bad behavior.
> >
> > Why not, with something like the scheme Ian outlined above?
>
> You snipped out the reasons: we'll get bad behavior of one sort or
> another no matter what, unless we have genlocked displays.
Ok, you guys banged this into my head on IRC. So the calculation will
be:
msc += last_pipe_vblank_count - cur_pipeX_vblank_count
like Ian said (where last_pipeX_vblank_count is updated everytime the
drawable moves onto pipe X). This gets a little ugly since I'll need
to track both a per-drawable MSC count as well as per-pipe
last_pipeX_vblank_count values. And unfortunately, since the drawable
movement is tracked in per-driver SAREA fields, this code can't be
generic. Ugg.
Thanks,
Jesse
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
--
_______________________________________________
Dri-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dri-devel
