Currently, there are several functions where static dispatch has been disabled, but that are exported by either ATI, nVidia or both lib.
To prevent compatibility issues, it seems a good idea to export those too at least. What do you think? Should we export all function exported by both nVidia and ATI, those exported by any of them, or even just export all functions? static_dispatch="false" but exported by both ATI and nVidia: glBlendEquationSeparateEXT glBlitFramebufferEXT glGetQueryObjecti64vEXT glGetQueryObjectui64vEXT glProgramEnvParameters4fvEXT glProgramLocalParameters4fvEXT static_dispatch="false" but exported by ATI, not by nVidia: glGetHistogramEXT glGetHistogramParameterfvEXT glGetHistogramParameterivEXT glGetMinmaxEXT glGetMinmaxParameterfvEXT glGetMinmaxParameterivEXT glGetTexParameterPointervAPPLE glHistogramEXT glMinmaxEXT glResetHistogramEXT glResetMinmaxEXT glStencilFuncSeparateATI glStencilOpSeparateATI glTextureRangeAPPLE static_dispatch="false" but exported by nVidia, not by ATI: glActiveStencilFaceEXT glColorSubTableEXT glDeleteFencesNV glDepthBoundsEXT glFinishFenceNV glGenFencesNV glGetFenceivNV glIsFenceNV glSetFenceNV glTestFenceNV ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
