David Bucciarelli wrote:
>
> Hi,
>
> I have done a small update:
>
> - checked in of the 3Dfx/demos/*.{rgb,bin} files (sorry, you will have
> to download ~400k at the next cvs checkout, but it is only one time
> operation);
>
> - updated the README and the README.3DFX files with my home email
> address ([EMAIL PROTECTED]) and the MESA_GLX_FX related documentation (read
> below);
>
> - few changes in the Mesa/src/X/xmesa1.c in order to support the new
> MESA_GLX_FX behavior:
>
> - unset => print a warning message and use the X11 driver;
> - "disable" => use the X11 driver;
> - "window" => use the in-window-hack or the Voodoo Rush
> in-window-rendering
> support;
> - "fullscreen" => use the fullscreen/fullspeed rendering.
>
> The new MESA_GLX_FX behavior was discussed few days ago at
> news.3dfx.com, it looks like the best possible solution.
I haven't read the 3dfx newsgroups in quite a while. What was the
problem?
I don't know if I'd like Mesa to print a warning if you don't have
MESA_GLX_FX set. Mesa shouldn't print anything during normal operation.
> Brian, I didn't read any comment about your proposal for introducing a
> bug-report tracking system but it looks like a very good idea. It is
> very easy to lost/forget a bug-report. Are you going to setup this stuff
> ?
I haven't had time to investigate it. Perhaps I could find a volunteer
to look into this. A bug tracking system would be nice but I'd rather
not be responsible for set-up / maintenace.
-Brian
----------------------------------------------------------------------
Brian Paul Avid Technology / Softimage [EMAIL PROTECTED]
_______________________________________________
Mesa-dev maillist - [EMAIL PROTECTED]
http://lists.mesa3d.org/mailman/listinfo/mesa-dev
