V4L2JDA should not show error message on Intel devices |
||
Issue descriptionWe should not show an error log in V4L2JDA if it's an Intel device. Device: Caroline Version: 9334.33.0 Feedback id: 57286219236 [1825:1825:0410/143209.533772:ERROR:v4l2_jpeg_decode_accelerator.cc(206)] Failed to open device libva info: VA-API version 0.39.2 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib64/va/drivers/i965_drv_video.so libva info: Found init function __vaDriverInit_0_39 libva info: va_openDriver() returns 0
,
Apr 19 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/eea08e1d749a5e8e21272e5cb281d4fdd7d7f214 commit eea08e1d749a5e8e21272e5cb281d4fdd7d7f214 Author: hiroh <hiroh@chromium.org> Date: Wed Apr 19 11:13:28 2017 Make V4L2 Jpeg Decode Accelerator not compiled on an Intel device On an Intel device, V4L2JDA isn't used. This patch makes V4L2JDA be not compiled if it's in an Intel device. BUG= 710729 TEST=confirm jpeg_accelerator_unittest is passed on x86_64 and armv7l. Also appr.tc/?debug=loopback. CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel Review-Url: https://codereview.chromium.org/2824743002 Cr-Commit-Position: refs/heads/master@{#465554} [modify] https://crrev.com/eea08e1d749a5e8e21272e5cb281d4fdd7d7f214/media/gpu/BUILD.gn [modify] https://crrev.com/eea08e1d749a5e8e21272e5cb281d4fdd7d7f214/media/gpu/ipc/service/gpu_jpeg_decode_accelerator.cc
,
Apr 20 2017
|
||
►
Sign in to add a comment |
||
Comment 1 by posciak@chromium.org
, Apr 12 2017Owner: hiroh@chromium.org
Status: Assigned (was: Available)