Initial DRI3000 protocol specs available

[Keith Packard]

James Jones <jajones at nvidia.com> writes:

> If you associate an X Fence Sync with your swap operation, the driver 
> has the option to trigger it directly from the client command stream and 
> wake up only the applications waiting for that fence.

Yeah, right now we're doing some hand-waving about serialization which
isn't entirely satisfying.

> The compositor, 
> if using GL, could have received the swap notification event and already 
> programmed the response compositing based on it before the swap even 
> completes, and just insert a token to make the GPU or kernel wait for 
> the fence to complete before executing the compositing rendering
> commands.

We just don't have these issues with the open source drivers, so it's
really hard for us to reason about this kind of asynchronous
operation. Access to the underlying buffers is mediated by the kernel
which ensures that as long as you serialize kernel calls, you will
serialize hw execution as well.

-- 
keith.packard at intel.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 827 bytes
Desc: not available
URL: <http://lists.x.org/archives/xorg-devel/attachments/20130307/fd62d3d6/attachment.pgp>