diff options
author | zmo@google.com <zmo@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-11-04 23:25:19 +0000 |
---|---|---|
committer | zmo@google.com <zmo@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-11-04 23:25:19 +0000 |
commit | fc0d94c64292dc6702e2b4c28e446dbcd14f0ad2 (patch) | |
tree | fa814fb9f7a832aac889f6eed383749ef48a2f03 /media | |
parent | f01e513c6eaeaa21cfb13cfd8eed272228837e3c (diff) | |
download | chromium_src-fc0d94c64292dc6702e2b4c28e446dbcd14f0ad2.zip chromium_src-fc0d94c64292dc6702e2b4c28e446dbcd14f0ad2.tar.gz chromium_src-fc0d94c64292dc6702e2b4c28e446dbcd14f0ad2.tar.bz2 |
Don't initialize GL bindings in browser process even if libpci doesn't exist on Linux.
Initializing GL bindings seems to crash chrome sometime with fglrx drivers. We should definitely avoid that.
So the ATI cards we want to blacklist cannot be done at through preliminary gpu info collection, but it can be done at GPU process launch time. We use GL_VENDOR and GL_RENDERER string for blacklisting rather than vendor_id.
BUG=94973
TEST=unittest
Review URL: http://codereview.chromium.org/8476013
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@108739 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'media')
0 files changed, 0 insertions, 0 deletions