diff options
author | zmo@chromium.org <zmo@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-05-08 22:56:20 +0000 |
---|---|---|
committer | zmo@chromium.org <zmo@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-05-08 22:56:20 +0000 |
commit | a0ee86c8d352a4768ee9f7532b14c53274225cf3 (patch) | |
tree | a748e37fe18229213bbbd498a7df48f98410544d /remoting/webapp/host_plugin_wrapper.js | |
parent | a4a677780b78fc469976cf50fd2cbe28aefcff83 (diff) | |
download | chromium_src-a0ee86c8d352a4768ee9f7532b14c53274225cf3.zip chromium_src-a0ee86c8d352a4768ee9f7532b14c53274225cf3.tar.gz chromium_src-a0ee86c8d352a4768ee9f7532b14c53274225cf3.tar.bz2 |
Makes sure driver_bug_workarounds takes effect in Android.
Right now the hardwired workarounds are still in place, but will be removed soon.
With this CL, the workarounds should be obtained from the json file, and this should overwrite the hardwired settings.
A few things in this CL:
1) Generally the browser process decides which workarounds are needed, and pass down to command buffer through a commandline switch in GPU process launch. However, in Android, we don't have a GPU process, so we append the switch immediately after we compute it in browser startup, and later pick up by command buffer because gpu thread and browser main thread are in the same process, therefore the same commandline.
2) add gl_extensions as a blacklist feature because this is the only reliable way to identify Vivante devices.
BUG=227162
TEST=android devices that need workaround get them, for example, hisilicon device
R=epenner,kbr
Review URL: https://chromiumcodereview.appspot.com/14762004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@199034 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'remoting/webapp/host_plugin_wrapper.js')
0 files changed, 0 insertions, 0 deletions