On Mon, 22 Jul, 2013 at 5:53 PM, Chris Wilson
<chris@xxxxxxxxxxxxxxxxxx> wrote:
With xorgMir this is not going to fly. Make sure the compatibility
cruft, first of all, exists and is out of line in a header.
Do you mean remove the various #ifdef XMIR bits, or *all* the bits
gated on xorgMir? Some of that's not going to be trivial to hide away
in a header.
And expose the driving heartbeat of when to refresh the screen
pixmap from Xmir.
I'm not sure what you mean here - Xmir exposes the on-buffer-available
callback, which gets triggered when swap_buffers has returned the next
buffer to render to. This is what I'd think of as the refresh
heartbeat. Is this not what you mean?
If you're rendering as fast as possible, this will be a
once-per-compositor-vblank event.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
