From: Eric A. <an...@te...> - 2001-01-07 18:48:25
|
That was my question. From what I read, the 3dfx license was required on anything that was recognizably from Glide. This is of course incompatible with the XF86 licensing requirements (Nothing but an X/BSD-like license. There was a big discussion about licenses not too long ago on the XF86 lists, and I think that was the consensus), so I wasn't sure if having seen a lot of Glide code would make it illegal for me to write a V3 driver and put it under the X license. Of course, V5 support would be out unless 3dfx allowed code that could be considered Derivative Work to be relicensed for X. I've started on it now, but considering my only driver knowledge is from working on the glide fixes, browsing the tdfx code in DRI, and the V3 manual, it'll be slow. I'm not looking at/copying Glide for this at all. It'll be a hobby kind of thing, not something I'll be working frequently. (All that homework really ought to take precedence). Of course, if I ever get anything running I'll post it, but I wouldn't expect that for a long while. As far as comments on a speedup, anything CPU-bound will get a definite speedup from not needing to call out to Glide. For other activities, one hope would be to get page flipping. It may be possible, or at least easier, with some of the code written for the FSAA/SLI on V5. That would provide a major speedup, particularly at the high resolutions I like to run at. I also want to add performance boxes, because they're just so fun. > > The glide license is fairly liberal. Check out the glide3 CVS and read > COPYING. You aren't contaminated. You can reuse glide code, though you > need to put 3DFX copyright disclaimers in your derivative works. -- Eric Anholt an...@te... |