From: Eric A. <an...@te...> - 2001-01-07 07:08:15
|
I've got the page updated again, with more Glide code and instructions. I've converted the h5 code so it compiles, but I have no way to test it. The configuration and compilation is also a little more friendly. Now I'm working on getting my linux functional to test if these changes still work on that side. What is the best way to get patches into Glide? The Bug Reports area has some pretty old bugs, and some really easy-to-fix ones, but none are committed or closed. As far as I can tell, very little is happening with the Glide code. Are there any FreeBSD people with a V5 willing to try this code? Feedback would be wonderful. My goal is to get this eventually into a port so that people don't have to go through this mess. Finally, would there be any chance of being able to make a 3dfx driver (at least for voodoo3) without needing Glide, to further simplify the install process and offer some bit of speedup? What would the legality be? If I were interested in working on that, have I been "contaminated" by looking at the Glide code? Would I be allowed to take from the Glide code for making a new driver? On Thursday 04 January 2001 22:50, Eric Anholt wrote: > For those FreeBSD users out there, I have put changes for FreeBSD-current > DRI up on my website. It's for the voodoo3, but mga should work (I would > hope), and voodoo5 would probably just require porting of the v3 stuff I > did. I have had success with this code and the Mesa demos, tuxracer for > FreeBSD, and Linux Q3a. If only I could get wine with opengl working... I > also have some code for overclocking the v3 from the X config file, but it > is incorrect for other voodoos, and there is no protection for them. My > system is also pretty unstable right now, so I haven't tested the overclock > much. > > It's preliminary, and some explanation and diffs are lacking, but I need > some sleep. > > http://www.teleport.com/~anholt/devel/dri/index.html > -- Eric Anholt an...@te... |