Restrict GPU Raster on CrOS to Intel

gpu/config/software_rendering_list_json.cc

Index: gpu/config/software_rendering_list_json.cc
diff --git a/gpu/config/software_rendering_list_json.cc b/gpu/config/software_rendering_list_json.cc
index 1cadf12202e05370b105a61773ea63d27fab39e5..91c1ed458c145aa1a7805ff4e59f73a1b2642f17 100644
--- a/gpu/config/software_rendering_list_json.cc
+++ b/gpu/config/software_rendering_list_json.cc
@@ -18,7 +18,7 @@ const char kSoftwareRenderingListJson[] = LONG_STRING_CONST(
 {
   "name": "software rendering list",
   // Please update the version number whenever you change this file.
-  "version": "12.19",
+  "version": "12.20",
   "entries": [
     {
       "id": 1,
@@ -1495,6 +1495,26 @@ LONG_STRING_CONST(
       "features": [
         "gpu_rasterization"
       ]
+    },
+    {
+      "id": 137,
+      "description": "GPU rasterization should only be enabled on Intel Chromebooks with GLES 3.0 for now.",
+      "cr_bugs": [684094],
+      "os": {
+        "type": "chromeos"
+      },
+      "features": [
+        "gpu_rasterization"
+      ],
+      "exceptions": [
+        {
+          "vendor_id": "0x8086",
+          "pixel_shader_version": {

[vmiura, 2017/03/04 02:04:47]

Is there a reason to use "pixel_shader_versionn" > 3 instead of "gl_version" >
3?

[ericrk, 2017/03/07 01:46:42]

Nope. However, decided to move to an explicit blacklist, as it turns out this
filter won't exclude SandyBridge.

+            "op": ">=",
+            "value": "3.0"
+          }
+        }
+      ]
     }
   ]
 }