Roland Scheidegger wrote: > Hi, > > there are currently a couple of extensions enabled in the mesa state > tracker which probably shouldn't be. These were moved there by commit > a0ae2ca033ec2024da1e01d1c11c0437837c031b (that is with dri they were > already always enabled before). > > Someone knows off-hand which one we can enable or not? I'm going to kill > off EXT_cull_vertex and TDFX_texture_compression_FXT1, clearly we can't > handle them. > The others in question are > ARB_window_pos
handled in core mesa. > APPLE_client_storage should not be enabled by default. > MESA_pack_invert handled by core mesa. > NV_vertex_program > NV_vertex_program1_1 > > (the latter two IIRC the problem was that regs needed to be > zero-initialized) There may be other issues too. Someone would have to enable the extension(s) and do some testing. > Currently gallium dri drivers also have ARB_imaging enabled too (via > driInitExtensions()), I think that's not correct neither. Yeah, I think that needs to be disabled. -Brian ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev