I had a few minutes this evening and went on a crusade to nail bogus state submitted to R300 DRM driver.
My thoughts were that since sometimes blending works and sometimes it does note there might be some sort of corruption problem in the R300 Mesa driver and it emits bogus state.
The results are negative - I could not find any bogus register access, thus whatever happens to the hardware is either due to one of the state registers or some other path is taken.
The sideeffect is that I wrote some code to check "unchecked" state for validity and after some thought I committed it - even though the error is not there this is a nice precaution anyway. So "unchecked" state is no longer unchecked..
best
Vladimir Dergachev
------------------------------------------------------- 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_id=6595&alloc_id=14396&op=click -- _______________________________________________ Dri-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dri-devel
