[RFC] GLX_INTEL_swap_event
Jesse Barnes
jbarnes at virtuousgeek.org
Mon Nov 16 13:34:59 PST 2009
On Mon, 16 Nov 2009 13:25:01 -0800
Ian Romanick <idr at freedesktop.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Jesse Barnes wrote:
> > On Mon, 16 Nov 2009 11:51:31 -0800
> > Ian Romanick <idr at freedesktop.org> wrote:
> >
> >> All X events are 32 bytes, but GLX_BUFFER_SWAP_COMPLETE_INTEL is 34
> >> bytes. Perhaps the SBC could be only 4-bytes? Having more than
> >> 2**32 buffers swaps seems unlikely. :)
> >
> > Arg, miscounted. :) That would make it fail to match the OML
> > stuff, but is probably ok...
>
> Only in the protocol. The structure returned to clients can still use
> uint64_t. Right?
Yeah, true.
> > Thanks for checking it out. What's the ARB process for this? Once
> > we're shipping an implementation should it be hosted at the opengl
> > GLX extension registry? Or do we need some ARB approval of the
> > event code we're using?
>
> To get the spec posted in the registry, I just need to put it in the
> Khronos SVN repo and as Jon to mirror it to the website.
>
> The enum values are allocated, in blocks, to implementers. It doesn't
> look like Mesa or Intel have any GLX enums reserved. I'll have to ask
> for a block. It will *probably* be 0x8180 through 0x818F. It looks
> like we also need an event code. This will probably be 17.
>
> I'm not sure what the process is for the event mask bit, so I'll ask.
Great, thanks.
--
Jesse Barnes, Intel Open Source Technology Center
More information about the xorg-devel
mailing list