Upgrade libdrm to upstream |
|||
Issue descriptionlibdrm is now at 2.4.70 upstream libdrm is at 2.4.80 While adding support R16 GPUMemoryBuffer in https://codereview.chromium.org/2920793005/ reveman suggested to update the libdrm in chromeos and chrome/src/third_party https://codereview.chromium.org/2920793005/diff/120001/ui/ozone/platform/drm/common/drm_util.cc#newcode22 instead of defining DRM_FORMAT_R16 fourcc_code('R', '1', '6', ' ') in chrome code.
,
Sep 25 2017
,
Jan 4 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/45063aa67e808ea901b18c57b7bb4a29fd783503 commit 45063aa67e808ea901b18c57b7bb4a29fd783503 Author: Kristian H. Kristensen <hoegsberg@chromium.org> Date: Thu Jan 04 00:10:33 2018 ozone/drm: Use upstream drm color structs and blob functions Bug: 586475 , 733703 Change-Id: Id8a08fefff1af4f80fd5520a18cc1c9417147552 Reviewed-on: https://chromium-review.googlesource.com/848301 Reviewed-by: Daniel Nicoara <dnicoara@chromium.org> Commit-Queue: Kristian H. Kristensen <hoegsberg@chromium.org> Cr-Commit-Position: refs/heads/master@{#526866} [modify] https://crrev.com/45063aa67e808ea901b18c57b7bb4a29fd783503/ui/ozone/platform/drm/common/drm_util.cc [modify] https://crrev.com/45063aa67e808ea901b18c57b7bb4a29fd783503/ui/ozone/platform/drm/gpu/drm_device.cc
,
Jan 4 2018
|
|||
►
Sign in to add a comment |
|||
Comment 1 by rijubrat...@intel.com
, Jun 19 2017