GitLab

InProcessCommandBuffer doesn't currently handle dropping to 565
low-bit-depth on low-end Android. This CL adds this logic.

To safely handle low bit depth and virtualized contexts, we need
to know whether our target bit depth is compatible with the default
offscreen context. This change passes the surface format of this
context through CommandBufferTaskExecutor to allow this to be queried
from InProcessCommandBuffer.

Finally, as error-handling for the creation of the offscreen surface
is currently a bit scattered, this CL simplifies things by creating
this surface during init and passing it in to GpuChannelManager, so
any callers can just assume success.

BUG=868476

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: I8ffaa05e2ebbf6e910e76a8ef75095edf1cd3fe5
Reviewed-on: https://chromium-review.googlesource.com/1150966Reviewed-by: Bo <boliu@chromium.org>
Reviewed-by: Antoine Labour <piman@chromium.org>
Commit-Queue: Eric Karl <ericrk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578796}