The following three places use USE_OZONE to decide if we have V4L2. That's not required any more now that we use USE_V4L2_CODEC. https://cs.chromium.org/chromium/src/media/gpu/video_encode_accelerator_unittest.cc?l=53 https://cs.chromium.org/chromium/src/media/gpu/video_encode_accelerator_unittest.cc?l=1067 https://cs.chromium.org/chromium/src/content/common/sandbox_linux/bpf_gpu_policy_linux.cc?q=bpf_gpu_policy_linux.cc&sq=package:chromium&dr&l=346
https://codereview.chromium.org/2146733003/
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/5580c3ab2104c612abf89283d76239e5c26ef672 commit 5580c3ab2104c612abf89283d76239e5c26ef672 Author: henryhsu <henryhsu@chromium.org> Date: Thu Jul 14 05:11:41 2016 Remove USE_OZONE in video files Currently all chromebooks have USE_V4L2_CODEC use flag. We should use this instead of depending USE_OZONE to enable V4L2 devices. BUG= 627480 TEST=vea unittest pass, apprtc use hw encode/decode Review-Url: https://codereview.chromium.org/2146733003 Cr-Commit-Position: refs/heads/master@{#405436} [modify] https://crrev.com/5580c3ab2104c612abf89283d76239e5c26ef672/content/common/BUILD.gn [modify] https://crrev.com/5580c3ab2104c612abf89283d76239e5c26ef672/content/common/sandbox_linux/bpf_gpu_policy_linux.cc [modify] https://crrev.com/5580c3ab2104c612abf89283d76239e5c26ef672/media/gpu/BUILD.gn [modify] https://crrev.com/5580c3ab2104c612abf89283d76239e5c26ef672/media/gpu/ipc/client/BUILD.gn [modify] https://crrev.com/5580c3ab2104c612abf89283d76239e5c26ef672/media/gpu/video_encode_accelerator_unittest.cc
Comment 1 by henryhsu@chromium.org
, Jul 13 2016