As someone might of noticed, r300Clear calls r300ResetHwState as it tampers over states as there have been no good way to save the states that r300ClearBuffer needs to modify.
I discussed about the possible aproaches of doing state saving with Vladimir. Implementing something like R200_DB_STATECHANGE doesnt look like a good alternative as cases where something like this would be needed seem rare. Hence functions that want to play with states should probably handle it by themselves if possible. Instead of saving the states we could write states that r300Clear needs to modify directly into command buffer and just dirty mark state atoms that have been altered. Any pros, cons, other ideas? -- Aapo Tahkola ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&op=click -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
