diff options
author | Alexandre Elias <aelias@chromium.org> | 2015-04-07 18:00:05 -0700 |
---|---|---|
committer | Alexandre Elias <aelias@chromium.org> | 2015-04-08 01:01:14 +0000 |
commit | f5d0dccf607c7722c1e7f36f667a98efb5065706 (patch) | |
tree | cfeaefcd811da77e93244f3fcf63de0b3a1bffb5 /chrome/common/switch_utils.cc | |
parent | c3658c1d19ed01c9ddf2070561403ccfed78b9eb (diff) | |
download | chromium_src-f5d0dccf607c7722c1e7f36f667a98efb5065706.zip chromium_src-f5d0dccf607c7722c1e7f36f667a98efb5065706.tar.gz chromium_src-f5d0dccf607c7722c1e7f36f667a98efb5065706.tar.bz2 |
Disable framebuffer discarding on Mali-4xx and clean up.
It seems all of the known bugs with Mali-400 are related to framebuffer
discarding. Blacklist framebuffer discarding universally on Mali-400
and reenable ganesh and canvas where it was still blacklisted on Mali-400.
There was a preexisting workaround applied to all ARM < 4.4 which was
originally written in the context of Mali-T604; this explains why the
bugs only reproed on some Mali-400 devices. Add a new one for all 4xx.
Also, a recently added Nexus 6 workaround did essentially the same
thing, but at the level of making the discard do nothing instead of not
advertising the extension. In OpenGL ES 3, this is a core method so
failing to advertise won't be sufficient, so merge the two workarounds
and remove the "_ext_" from the name.
BUG=449488,451230
Review URL: https://codereview.chromium.org/1068573004
Cr-Commit-Position: refs/heads/master@{#324152}
(cherry picked from commit 8ef99b8a51842a038c64cd2b1ab1896228651ec2)
Review URL: https://codereview.chromium.org/1070493002
Cr-Commit-Position: refs/branch-heads/2357@{#12}
Cr-Branched-From: 59d4494849b405682265ed5d3f5164573b9a939b-refs/heads/master@{#323860}
Diffstat (limited to 'chrome/common/switch_utils.cc')
0 files changed, 0 insertions, 0 deletions