[RFC] GLX_INTEL_swap_event

[Ian Romanick]

-----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?

>> Minor nit... Since many specs have issues lists that are longer than
>> the spec, we've started putting the issues list at the end.  Look at a
>> recent spec for an example:
>>
>> http://www.opengl.org/registry/specs/ARB/glx_create_context.txt
> 
> Ok, I'll move it to the end.
> 
> 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.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAksBwysACgkQX1gOwKyEAw/MgACfXxGxCuOl6n41CnW8zWNw6eIU
5Y4AmwZxBd5xeQzwoHuS18N3cS5PNrxE
=2G/v
-----END PGP SIGNATURE-----