Re: [Dri-devel] per-screen client-side glx extensions

[Ian R. <id...@us...>]

Keith Whitwell wrote:
> Ian Romanick wrote:
> 
>> There are two ways to go on this.  One way is to make a new 
>> GLX_MESA_memory_allocate extension that just extends the existing 
>> glXAllocateMemoryNV, glXFreeMemoryNV, and glXGetAGPOffsetMESA to take 
>> a display pointer and screen.  This is by far the easiest choice and 
>> by far the least forward-looking.
>>
>> The other way to go would be to implement support for 
>> ARB_vertex_array_object in the r200 driver (which is now part of the 
>> 1.5 core spec) and add a "trivial" layered extension for pixel data.  
>> Since this extension is now part of the core, and there are existing 
>> apps (i.e., UT2k3) that *really* want to use it, this is the most 
>> forward-looking approach.  It will also take longer and be a lot more 
>> work.  If I'm not mistaken, it will also require merging Mesa 5.1 to 
>> DRI...and that ain't gonna happen for awhile.
>>
>> So, here's the question of the day:  do you & your customers need the 
>> existing functionality in XFree86 or just in the embedded branch?  If 
>> the latter, then I'd like to axe it just from the DRI trunk and work 
>> towards the 2nd option.
> 
> We need it specifically in the DRI.  I'd be relatively happy with the 
> first proposal as a stop-gap measure.

Attached is the spec I whipped up for GLX_MESA_allocate_memory.  Keith, 
does this suit your short-term needs?  If so, I should be able to 
replace the existing implementation of the GLX_NV_vertex_array_range 
allocator with this one quickly after Felix commits his changes.