
As a part of MappableSI, we are replacing GMB usage with MappableSI. Creating a MappableSI for R8 format in media capture code currently fails in service side code[1]. This is because creating a NativePixmap as part of OzoneImageBacking creation will fail as the underlying buffer is not texturable. Also for media capture code irrespective of the format, we don't really need to hold the GMB handle in the service side SharedImage backing anyways since capture code only need the GMB handle to map. Handle is then sent to renderer which actually creates a shared image which will be used in the GPU process. Hence use SHARED_IMAGE_USAGE_CPU_ONLY_READ_WRITE which instructs the service side that a NativePixmap inside the SharedImage is not necessary for this use case. This allows skipping the service side checks for texturable format. [1] https://source.chromium.org/chromium/chromium/src/+/main:ui/gfx/linux/gbm_wrapper.cc;drc=5d0194cbc9cddc2ad096da32f16d7d1eac5d4a34;l=410 Bug: 40264379, 382679374, 370760466 Change-Id: Ie1263454ca3e857efe521d1fe282f399d3db899f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6072273 Reviewed-by: Colin Blundell <blundell@chromium.org> Commit-Queue: vikas soni <vikassoni@chromium.org> Auto-Submit: vikas soni <vikassoni@chromium.org> Cr-Commit-Position: refs/heads/main@{#1401487}