Is there any kind of overview on how graphics contexts are implemented? Here a few of the questions I'm having...
When multitasking, how does the context get changed? When multitasking, how long does it take to change context? Does graphics hardware have a single set of context registers, or are there multiple sets for fast context switch? How is drmCreateContext related to the driver's context variables? How many contexts can I have, per processes, globally? How are the states diff'd to minimize state changes on process switch? Do state changes get queued like other 3D ops? Finally, the questions I am trying to answer for the R200... 1) When implementing per context drawables how do I make sure the hardware knows what buffer I am drawing to? Is the code already written for this since each context can be drawing into either the front or the back buffer? 2) How do modify the clear functions not to use a global variable for the buffer pointer, instead they need to get it from the context? ===== Jon Smirl [EMAIL PROTECTED] __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
