Added FBO Invalidation workaround for Nexus 6.
We have run into a driver issue where after we invalidate a Frame Buffer Object it gets into a state where it will randomly drop draw calls and/or texture copies. I have added a workaround for this issue by skipping frame buffer invalidations on Adreno 420s. This is valid because invalidations set the frame buffer to be in an undefined state so skipping them is technically okay, however we may lose optimizations that could happen at the driver level for operations being performed on an undefined FBO. R=sievers@chromium.org, vmiura@chromium.org BUG=443060 Review URL: https://codereview.chromium.org/1034663003 Cr-Commit-Position: refs/heads/master@{#322403}
Showing
Please register or sign in to comment