37708dbb8c940713317d3aba6113000e8b65e40c |
|
11-Feb-2018 |
Jeff Tinker <jtinker@google.com> |
Revert "Revert "Fix MediaDrm security level APIs"" This reverts commit 3553dfe9da9f1bff6d62f3ea52f71f956a5f429b. Change-Id: I162037cfe692a0b0d277c562fc3f92d48f9446c3
/frameworks/native/headers/media_plugin/media/drm/DrmAPI.h
|
3553dfe9da9f1bff6d62f3ea52f71f956a5f429b |
|
11-Feb-2018 |
Tobias Thierer <tobiast@google.com> |
Revert "Fix MediaDrm security level APIs" This reverts commit 52d274d3428a26c3130fd72dfcc2be2f3058d56e. Reason for revert: Build cop here. The CL topic that I'm reverting broke several builds: Drm.h's openSession(Vector<uint8_t> &sessionId) hides overloaded virtual function openSession(DrmPlugin::SecurityLevel securityLevel, ..) from IDrm.h. https://android-build.googleplex.com/builds/submitted/4598692/full-eng/latest/view/logs/build_error.log Change-Id: I6c1029e615ea9f418d265c75db28981036c98ee8
/frameworks/native/headers/media_plugin/media/drm/DrmAPI.h
|
52d274d3428a26c3130fd72dfcc2be2f3058d56e |
|
06-Feb-2018 |
Jeff Tinker <jtinker@google.com> |
Fix MediaDrm security level APIs Vendors implementing the newly added MediaDrm.setSecurityLevel HAL found that it was difficult to implement properly. Also the semantics are somewhat ambiguous from the Java platform API level. This CL binds the security level assignment to openSession which clarifies the API for apps as well as making it more natural to implement in HAL modules. bug:72831697 test: VtsHalDrmV1_1TargetTest, GTS media tests Change-Id: Ib3f762b7d813872956715b67bc6eff06f1b9a978
/frameworks/native/headers/media_plugin/media/drm/DrmAPI.h
|
47265ac241233513eead1ed47ae6d28f6d02a580 |
|
23-Jan-2018 |
Rahul Frias <rfrias@google.com> |
Add new values to KeyRequestType Two additional KeyRequestTypes have been added, None and Update. None indicates that no key request is needed as keys have already been loaded. Update indicates that while keys have previously been loaded, an additional (non-renewal) license request is needed. Bug: 70335058 Change-Id: If9a2e1d9bb0a2ba92e422994f04d8ec0708030ea
/frameworks/native/headers/media_plugin/media/drm/DrmAPI.h
|
14f2336874c91e5954407cb8dd529329f1eaef24 |
|
17-Nov-2017 |
Jeff Tinker <jtinker@google.com> |
Add new MediaDrm methods Methods for querying HDCP, security levels and number of sessions bug:64001680 bug:33657579 Change-Id: Ifd0215a1879ddda940ebe0fb427b73ce906e99d7
/frameworks/native/headers/media_plugin/media/drm/DrmAPI.h
|
55e9bd7c487ee235631f302ab8626776547ac913 |
|
29-Jun-2017 |
Jiyong Park <jiyong@google.com> |
Package media/*/*.h headers as a headers lib: media_plugin_headers Headers under frameworks/native/include/media serves as an interface that is meant to be implemented by vendors. For example. media/hardware/CryptoAPI.h is implemented under vendor/widevine/libwvdrmengine/mediacrypto. When building with BOARD_VNDK_VERSION, the headers are not accessible to vendors since they have been included via the global include paths and the paths are not available when building with BOARD_VNDK_VERSION. So, we need to make a "headers library" for the media headers and modify vendors to use the headers lib. Usually, we have been doing this by moving the headers into a subdirectory (usually 'include') of a module that implements the headers. But, this approach can't be used at this time since the media headers are implemented by many modules. The chosen solution is to a separate directory headers/media_plugin and define a headers lib named media_plugin_headers there. Note: frameworks/native/headers will now be the home for such header-only libraries. Bug: 63120269 Test: build Change-Id: I67d625706b40d06c8f0602284fbcc1cc8b174c6f
/frameworks/native/headers/media_plugin/media/drm/DrmAPI.h
|