Am Sonntag, den 14.08.2005, 12:04 +0200 schrieb Philipp Klaus Krause: > I have some questions about the SiS driver: > > 1) The SiS driver looks different from the other drivers. It doesn't > have a custom tnl_pipeline as all the other drivers except tdfx do. > Was this some old style of writing drivers and all others have already > been converted?
The custom tnl_pipeline is merely an optimization for the more-or-less common case of unclipped primitives. Depending on the capabilities of the hardware more restrictions apply (e.g. one-sided lighting, with some primitives flat shading may not be supported, ...). Mesa drivers can work without a custom tnl_pipeline. It's not a replacement for the general case though. All drivers have the standard _tnl_render_stage as last fallback stage in the pipeline. Regards, Felix > > 2) Has any of the work on DRI for SiS 6326 been merged into DRM or Mesa? > > 3) Is there any documentation for the SiS 305. I mean, what did the > people that wrote this driver use? Or is it just a 6326 with another > texture unit added so the documentation for the 6326 was used? > The wiki says there is no documentation except that two documents from > UtahGLX which obviously aren't enough for writing a driver. Was this > driver released by SiS or was the chip reverse-engineered? > > Philipp > -- | Felix Kühling <[EMAIL PROTECTED]> http://fxk.de.vu | | PGP Fingerprint: 6A3C 9566 5B30 DDED 73C3 B152 151C 5CC1 D888 E595 | ------------------------------------------------------- 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
