-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Philipp Klaus Krause wrote:
> OK I found it at > http://dri.sourceforge.net/doc/dri_driver_features.phtml > > Shouldn't this be ported to the wiki? IMO, we should have an XML (and a stylesheet with it) in CVS that generates this page (or generates a page per card / driver). The total picture is fairly complicated. For example, some features require certain DRM versions to be supported. Some functionality also has caveats. For example, GL_ARB_texture_env_combine has a number of cases on G400 where it can hit software fallbacks. Maybe something like: <!-- available=(yes|no|partial|software|bug|na) --> <feature name="GL_ARB_texture_env_combine" available="partial" since="20031021" drm_maj="3" drm_min="0"> <p>While GL_ARB_texture_env_combine is supported by the driver, quirks in the functionality of the Matrox hardware prevent it from being fully implemented. There are numerous subtle cases that can result in software fallbacks.</p> </feature> Each time a developer updates the driver, the would just have to update the XML file (one (or more?) file per driver in the driver's source directory) with the new information. Dunno...I'm just talking off the top of my head... -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFDAOhEX1gOwKyEAw8RAhCyAJ4we3vOh/qkU/8WMTr+MOvu++45zACdF3Ma n/ZyzdJ0M0i+OliLyj4VxH8= =VsRX -----END PGP SIGNATURE----- ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
