minigbm: add GBM_BO_USE_TEXTURING
Chromium passes in no flags to gbm_bo_create() to indicate the buffer will be used as a texture. This convention has caused confusion in the past. CL:448251 introduced BO_USE_TEXTURE, so it makes sense to match the more explicit internal semantics. TEST=run mapped_texture_test -f NV12 of drm-tests package on amd64-generic BUG=chromium:683347 Change-Id: I40782763d125e640b4bb6a157035b17ebc32cc8c Reviewed-on: https://chromium-review.googlesource.com/546884 Commit-Ready: Dongseong Hwang <dongseong.hwang@intel.com> Tested-by: Dongseong Hwang <dongseong.hwang@intel.com> Reviewed-by: Dongseong Hwang <dongseong.hwang@intel.com> Reviewed-by: Gurchetan Singh <gurchetansingh@chromium.org>
This commit is contained in:
parent
5f61c79203
commit
3909dc011b
2 changed files with 6 additions and 0 deletions
|
|
@ -22,6 +22,8 @@ uint64_t gbm_convert_flags(uint32_t flags)
|
|||
usage |= BO_USE_CURSOR_64X64;
|
||||
if (flags & GBM_BO_USE_RENDERING)
|
||||
usage |= BO_USE_RENDERING;
|
||||
if (flags & GBM_BO_USE_TEXTURING)
|
||||
usage |= BO_USE_TEXTURE;
|
||||
if (flags & GBM_BO_USE_LINEAR)
|
||||
usage |= BO_USE_LINEAR;
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue