media/gpu: Create DBABuf-backed VideoFrame in VEA with v4l2 ImageProcessor, |
|
Issue descriptionTo make ImageProcessor operate on import mode, its caller, VEA (Video Encoder Accelerator), should create VideoFrame for ImageProcessor use as output. For V4L2 ImageProcessor, its only accepts DMAbuf-backed VideoFrame as output. So VEA needs to allocate DMAbuf-backed VideoFrame. Ozone platform has ability to create DMAbuf-backed VideoFrame.
,
Jan 9
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/5d39704b06e37a38fe930cf149e1c712a49a9321 commit 5d39704b06e37a38fe930cf149e1c712a49a9321 Author: Daniel Bratell <bratell@opera.com> Date: Wed Jan 09 09:33:53 2019 Remove the ::media::gpu namespace which conflicted with ::gpu We should not have sub namespace with the same name as top level namespaces since that causes name lookup conflicts. ::media::gpu in particular was only used by a single function, and I'm sure it will be fine in ::media instead, saving us from having to write ::gpu everywhere. This broke the build in certain jumbo build configurations. Bug: 910590 Change-Id: Ic735dedfe39485ec5f2bd0d0adcce22fa12ec951 Reviewed-on: https://chromium-review.googlesource.com/c/1400823 Reviewed-by: Dale Curtis <dalecurtis@chromium.org> Commit-Queue: Daniel Bratell <bratell@opera.com> Cr-Commit-Position: refs/heads/master@{#621088} [modify] https://crrev.com/5d39704b06e37a38fe930cf149e1c712a49a9321/media/gpu/platform_video_frame.cc [modify] https://crrev.com/5d39704b06e37a38fe930cf149e1c712a49a9321/media/gpu/platform_video_frame.h [modify] https://crrev.com/5d39704b06e37a38fe930cf149e1c712a49a9321/media/gpu/test/texture_ref.cc |
|
►
Sign in to add a comment |
|
Comment 1 by bugdroid1@chromium.org
, Dec 6