FreeBSD uses a mechanism called 'ports' (and related 'packages') for the easy installation of software. It is basically a special Makefile that grabs a tarball from CD-ROM or the Internet, applies FreeBSD specific patches if necessary, configures, builds, and installs it. I managed to create such a port that dealt successfully with XFree86 3.3.3.1, Mesa 3.0 and nvidia's riva-glx distribution of GLX. The resulting 3D is not too fast, but still impressive and very promising. (BTW it will make me buy a TNT card in an hour, to replace my RIVA128 :) The last days I was busy moving this port to XFree86 3.3.4 and current GLX code. However when finished yesterday, the result was noticable slower. So I suspect something might went wrong. Before I continue investigation this evening, I would like to drop some questions here: . I use a Mesa 3.0 tarball and apply some diffs from the nvidia site to it. Is this still (XF 3.3.4) a good idea? . Is there a tag in CVS that I could use to retrieve a proper 3.0 state? . The XFree86 server displays a list of what 2d hardware acceleration features it uses. Do we have a mechanism that displays the used 3d hardware features? Albeit I use proper colordepth and resolution, I might screwed up some parameter and Mesa or GLX or XFree might have fallen back to software rendering in my case - I would like to be aware of this. Regards, Marc _______________________________________________ Mesa-dev maillist - [EMAIL PROTECTED] http://lists.mesa3d.org/mailman/listinfo/mesa-dev
