I'm also having second thoughts about allowing drivers to add function calls to the GLX dispatch table. This is a global table that has no way to identify the "owner" of a dispatch function. This functionality is currently only used by a single feature of the r200 driver. I think we'd be better off adding proper support for GLX_NV_vertex_array_range and GLX_MESA_agp_offset, hackish though they are, than supporting __glXRegisterGLXFunction. There's just way too much that can go wrong with it in a multi-card environment.
It should be easy enough to add entry-points for glXAllocateMemoryNV, glXFreeMemoryNV, and glXGetAGPOffsetMESA to the __DriverAPIRec. Is that okay with you, Keith?
I'm going to *strongly* vote that we axe these interfaces altogether. Aparently, the folks at Nvidia didn't care too much about multi-card environments when the created {GLX,WGL}_NV_vertex_array_range. The spec says "Because wglAllocateMemoryNV and wglFreeMemoryNV are not OpenGL rendering commands, these commands do not require a current context." However, there is no screen / display information passed into the functions. How is the API supposed to identify the card to allocate memory on?
GLX_MESA_agp_offset isn't any better. It has the same "context free" nature and doesn't have any screen / display information. What about the case of a AGP card and a PCI card w/PCIGART in the same system?
I know that this isn't the use-cases for which these extensions were added to DRI, but we still have to support this stuff in the "general" case. I am *very* open to suggestions of how to fix this *and* keep everybody happy. :)
------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
