commit | 3a4965362d33b543ef5b3632eafdb582becbb342 | [log] [tgz] |
---|---|---|
author | Jeffrey Kardatzke <jkardatzke@google.com> | Wed Nov 29 22:19:44 2023 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Nov 29 22:19:44 2023 |
tree | 68a179b93cf4fc947801b452e16424fb25f605de | |
parent | ac8867364287368999c08b5cbe05459423cf69b4 [diff] |
media: Add ARM secure codecs support This reworks the existing change for H264 secure playback on ARM to pass the secure_handle through the picture creation method, and attach it to the picture rather than passing it through SetStream. This is more compatible with VP9/AV1 codecs and removes the state tracking in the accelerator. In order to avoid having to modify all the windows/mac code as well, we are doing this through an additional method on the accelerator interface. We will be able to drop this new method once we switch to the new flat V4L2 stateless decoder as that won't be tying input buffers to output surfaces anymore. Then we can just put it in media::CodecPicture and set that one field in the XXXDecoder and then the accelerator can use it after that. BUG=b:248610914 TEST=Secure H264 playback works on geralt, other codecs are under development still on the kernel/TEE side Change-Id: I5bd5fa41f31b61cc8fb8860c36bd7d0af9dfdce8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5067086 Reviewed-by: Nathan Hebert <nhebert@chromium.org> Commit-Queue: Jeffrey Kardatzke <jkardatzke@google.com> Cr-Commit-Position: refs/heads/main@{#1230953}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.