X fence sync objects are triggered relative to a given X screen's rendering operations. To perform this operation, they must be tied to a screen. As suggested by Aaron Plattner, mimick core protocol and use a drawable to identify which screen a fence sync object should belong to.
Signed-off-by: James Jones <[email protected]> Reviewed-by: Aaron Plattner <[email protected]> --- syncproto.h | 5 ++++- 1 files changed, 4 insertions(+), 1 deletions(-) diff --git a/syncproto.h b/syncproto.h index 6e851e4..1453e44 100644 --- a/syncproto.h +++ b/syncproto.h @@ -81,6 +81,7 @@ PERFORMANCE OF THIS SOFTWARE. #define XSyncCounter CARD32 #define XSyncAlarm CARD32 #define XSyncFence CARD32 +#define Drawable CARD32 /* * Initialize @@ -350,12 +351,13 @@ typedef struct _xSyncCreateFenceReq { CARD8 reqType; CARD8 syncReqType; CARD16 length B16; + Drawable d B32; XSyncFence fid B32; BOOL initially_triggered; CARD8 pad0; CARD16 pad1; } xSyncCreateFenceReq; -#define sz_xSyncCreateFenceReq 12 +#define sz_xSyncCreateFenceReq 16 /* * Put a fence object in the "triggered" state. @@ -466,6 +468,7 @@ typedef struct _xSyncAlarmNotifyEvent { #undef XSyncCounter #undef XSyncAlarm #undef XSyncFence +#undef Drawable #endif /* _SYNCPROTO_H_ */ -- 1.7.1 _______________________________________________ [email protected]: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
