summaryrefslogtreecommitdiffstats
path: root/gpu/gpu_config.gypi
Commit message (Collapse)AuthorAgeFilesLines
* Support for ozone graphics in content.rjkroege@chromium.org2013-05-291-0/+1
| | | | | | | | BUG=178543 Review URL: https://chromiumcodereview.appspot.com/14985005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@202749 0039d316-1c4b-4281-b951-d872f2087c98
* Move gpu_test_config stuff from content/ to gpu/zmo@chromium.org2013-05-281-0/+4
| | | | | | | | | | | | Again, these code is not depending on any content stuff, so moving it to gpu/ side will allow us to disable more gpu tests per GPU. BUG=230477 TEST=gpu_unittests,tree TBR=kbr@chromium.org, piman@chromium.org Review URL: https://codereview.chromium.org/15827008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@202690 0039d316-1c4b-4281-b951-d872f2087c98
* Cleanup link dependency and include rules.zmo@chromium.org2013-05-241-0/+1
| | | | | | | | | | BUG=230477 TEST=win bots link fine, check_deps R=apatrick@chromium.org, piman@chromium.org Review URL: https://codereview.chromium.org/16019008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@202175 0039d316-1c4b-4281-b951-d872f2087c98
* Make Win64 release build againjschuh@chromium.org2013-05-241-0/+2
| | | | | | | | | | | This disables a warning to fix breakage from r201875 TBR=zmo@chromium.org, piman@chromium.org R=zmo@chromium.org, piman@chromium.org Review URL: https://codereview.chromium.org/16028002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@202131 0039d316-1c4b-4281-b951-d872f2087c98
* Move GPU device/driver info related code from content to gpu.zmo@chromium.org2013-05-231-0/+69
| | | | | | | | | | | | | | | | | | | | Try to reland r201380 with build fix. This has been suggested by gman, and agreed by kbr and jam, for the following reasons: 1) These are gpu related code, and are independent of content / browser, so putting them under gpu/ is the right thing to do conceptually. 2) This enables us to set up tests in various places with the correct blacklisting/driver_bug_workarounds information. Otherwise, for the moment, gpu/ has no visibility into content/ side, so we have to duplicate the driver_bug_workarounds code and hardwire them for testing purpose. This is going to cause a lot of bugs in the future, as we have the two pieces of code for the same thing (one for chrome and one for testing) and people will easily forget to update one or the other. As for this patch, I didn't change the logic, and try to minimize the refactoring. All improvements enabled by this relocation will be done in follow-up CLs. BUG=230477 TEST=tree TBR=apatrick@chromium.org, joi@chromium.org, kbr@chromium.org, piman@chromium.org, sky@chromium.org Review URL: https://codereview.chromium.org/15745014 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@201875 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 201380 "Move GPU device/driver info related code from con..."zmo@chromium.org2013-05-211-36/+0
| | | | | | | | | | | | | | | | | | | | | | | | > Move GPU device/driver info related code from content to gpu. > > This has been suggested by gman, and agreed by kbr and jam, for the following reasons: > > 1) These are gpu related code, and are independent of content / browser, so putting them under gpu/ is the right thing to do conceptually. > > 2) This enables us to set up tests in various places with the correct blacklisting/driver_bug_workarounds information. Otherwise, for the moment, gpu/ has no visibility into content/ side, so we have to duplicate the driver_bug_workarounds code and hardwire them for testing purpose. This is going to cause a lot of bugs in the future, as we have the two pieces of code for the same thing (one for chrome and one for testing) and people will easily forget to update one or the other. > > As for this patch, I didn't change the logic, and try to minimize the refactoring. All improvements enabled by this relocation will be done in follow-up CLs. > > BUG=230477 > TEST=tree > TBR=gman@chromium.org, joi@chromium.org, kbr@chromium.org, piman@chromium.org > > Review URL: https://codereview.chromium.org/15385003 TBR=zmo@chromium.org Review URL: https://codereview.chromium.org/15619004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@201386 0039d316-1c4b-4281-b951-d872f2087c98
* Move GPU device/driver info related code from content to gpu.zmo@chromium.org2013-05-211-0/+36
This has been suggested by gman, and agreed by kbr and jam, for the following reasons: 1) These are gpu related code, and are independent of content / browser, so putting them under gpu/ is the right thing to do conceptually. 2) This enables us to set up tests in various places with the correct blacklisting/driver_bug_workarounds information. Otherwise, for the moment, gpu/ has no visibility into content/ side, so we have to duplicate the driver_bug_workarounds code and hardwire them for testing purpose. This is going to cause a lot of bugs in the future, as we have the two pieces of code for the same thing (one for chrome and one for testing) and people will easily forget to update one or the other. As for this patch, I didn't change the logic, and try to minimize the refactoring. All improvements enabled by this relocation will be done in follow-up CLs. BUG=230477 TEST=tree TBR=gman@chromium.org, joi@chromium.org, kbr@chromium.org, piman@chromium.org Review URL: https://codereview.chromium.org/15385003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@201380 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-05-10 08:01:42 +0000