-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 04/17/2011 01:28 AM, Nicolas Kaiser wrote: > * Marek Olšák <mar...@gmail.com>: >> r200 does support ARB_vertex_program. The backend is in r200_vertprog.c. I >> think it has vertex shader 1.1 in D3D. >> >> The patch is wrong though. The extension should be listed in the >> ARB_vp_extension array, not card_extensions. > > Thanks! I copied it from dri/r300/r300_context.c, where it's listed > in the card_extensions as well. > > I'll fix the patch. > >> On Sun, Apr 17, 2011 at 4:57 AM, Jerome Glisse <j.gli...@gmail.com> wrote: >>> R200 hw doesn't support shader program (well what i wouldn't call what >>> r200 has a shader). > > This is one of two extensions that I noticed are enabled in both the > Matrox mga driver, as well as the r600g driver, but not in r200. > > The other one is APPLE_vertex_array_object. I've enabled it on r200 > for testing, the demo works nicely.
This is another one that I think should always be enabled. This extension really only depends on ARB_vertex_buffer_object, and that is universally supported in Mesa. I don't know of any reason to not enable APPLE_vertex_array_object and ARB_vertex_array_object universally as well. > ./src/demos/vao_demo > GL_RENDERER = Mesa DRI R200 (R200 514D) TCL DRI2 > GL_VERSION = 1.3 Mesa 7.11-devel (git-4ee40c3) Do we have VAO (either ARB or APPLE) in piglit? That would actually be a more interesting test. The Mesa demos exercise extensions pretty minimally in most cases. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAk2spFEACgkQX1gOwKyEAw9OLQCfTG/xbagEM1fNV9zjz1tp0Cct hHEAniXp3uGdhoB0Lm7fu24OfN5+fxsQ =wi/s -----END PGP SIGNATURE----- _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev