> 2) Figure out what memory manager you are using and, if it is the > fake one, disable any paths in the driver that rely on the assumption of > persistent video-ram buffers, and provide alternatives. This would > effectively mean switching between i915tex and i965 versions of > CopyTexSubImage, texture uploads, etc, and turning off extensions like > FBO's for the fake manager.
I just took a look at the extension list -- it seems like you have **unconditionally** removed framebuffer objects and pixel buffer objects from the extension list??? This isn't really acceptable. People rely on that functionality, and removing it is a major regression. It's also needless in the TTM case, because FBOs and PBOs still work there. The problems can be solved, I'm very happy to work with you to solve them, but it would have been hugely preferable to do so while the code was on a branch. Keith ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Mesa3d-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
