323d172db73f2512fbc230e739e49d55f25bdb71 |
|
29-Jun-2017 |
Jiyong Park <jiyong@google.com> |
Build android.hardware.drm@1.0-service with BOARD_VNDK_VERSION Instead of relying on the global include paths, use the new headers lib 'media_plugin_headers'. Also, media/SharedLibrary.h is not used, thus deleted. Bug: 37342627 Test: BOARD_VNDK_VERSION=current m -j android.hardware.drm@1.0-service Change-Id: I30d8bcb6315b734cef7ad082c432da51eb33119c
/hardware/interfaces/drm/1.0/default/Android.mk
|
c019787ce9fb9f251c96cdb5a5d3a9ef21842d9b |
|
23-Jun-2017 |
Steven Moreland <smoreland@google.com> |
Use vendor variant of libstagefright_foundation. Rather than having a lib called libstagefright_foundation and one called libstagefright_foundation_vendor, we now just have one library and the build system keeps track of the vendor APIs that are exposed. Test: (sanity) boot device, watch (part of) DRM protected movie. Change-Id: I7495be3e8f546cac1b4909108313cf61fc85b1d8
/hardware/interfaces/drm/1.0/default/Android.mk
|
07770c78e18c5b09ba116fa1e779fe4408c42e3f |
|
19-Jun-2017 |
Jiyong Park <jiyong@google.com> |
Remove dependency to libmediadrm from drm HAL drm HAL has been using libmediadrm for android::SharedLibrary class and android::PluginLoader class. This is a Treble violation since libmediadrm is a framework-only library that is not available to vendors. To solve the problem, the two classes are copied into this directory to form a small static library android.hardware.drm@1.0-helper.a. Bug: 38302533 Test: mm under /hardware/interfaces/drm/1.0/default and /hardware/interfaces/drm/1.0/vts/functional Change-Id: I7b4e5cdb3bc815e971e0c3b7ec99ea86042e13eb
/hardware/interfaces/drm/1.0/default/Android.mk
|
eb845dab6e6b286b01e22734bbc8db3fe81885b9 |
|
15-Jun-2017 |
Jiyong Park <jiyong@google.com> |
Use libstagefright_foundation_vendor DRM HAL is a library in vendor. When BOARD_VNDK_VERSION is turned on, any lib in vendor partition can only link against to other vendor libs or libs marked as vendor_available:true. This lib is using libstagefright_foundation and the lib is not available to vendors. Instead, libstagefright_foundation_vendor is provided as a vendor-variant of the foundation library. Thus switching to the vendor variant. Bug: 37462569 Test: m android.hardware.drm@1.0-impl Change-Id: Iaee9886f9ba3643e1c19928690bad13c26ac29d7
/hardware/interfaces/drm/1.0/default/Android.mk
|
467c0db62c648da651a41c000381055b1703c5dc |
|
27-Apr-2017 |
John W. Bruce <juce@google.com> |
Prefix ENABLE_MEDIADRM_64 with TARGET_ This build-time flag should be prefixed. Bug: 37039525 Test: Built OS Change-Id: If6f6cd1ad2df5f000a4264cabeb7d9eb77e194ea
/hardware/interfaces/drm/1.0/default/Android.mk
|
136b5e46eca868a99d0c581659785756c25ec6f3 |
|
14-Apr-2017 |
Iliyan Malchev <malchev@google.com> |
Route DRM HAL libbinder traffic to /dev/vndbinder b/37309712 Test: marlin Change-Id: I72c2304842bd21b5393c17be5beeeb90a74d5345 Signed-off-by: Iliyan Malchev <malchev@google.com>
/hardware/interfaces/drm/1.0/default/Android.mk
|
fcde9ff3a08a2c569f0ec90fa3487ecb9d34444d |
|
24-Mar-2017 |
John W. Bruce <juce@google.com> |
Add Flag for Enabling 64-bit Legacy DRM Plugins We are ready for devices to begin migrating to a 64-bit Legacy DRM Loader. However, not all devices are ready to make this jump yet. A device needs to have all of its Legacy DRM Plugins ready to run as 64-bit before it can do this. This includes having 64-bit hardware integrations. So that devices can turn on 64-bit support as they get ready, I am adding flags that can be set in a device's device.mk file. There are two parts: * ENABLE_MEDIADRM_64 enables building the Legacy DRM Plugin HAL as 64-bit. * Setting drm.64bit.enabled=true in PRODUCT_PROPERTY_OVERRIDES switches the Legacy DRM Plugin HAL to searching for DRM Plugins in the 64-bit directory. Test: Validated that turning on these flags enables a 64-bit Legacy DRM Plugin HAL that loads 64-bit Legacy DRM Plugins from the lib64 directory. Bug: 36076017 Change-Id: I8d21fc7e7c0357eb6755839d41caa0f37ca20aff
/hardware/interfaces/drm/1.0/default/Android.mk
|
7e73d5b90831df7fdbced22792e5198fcae897af |
|
24-Feb-2017 |
Steven Moreland <smoreland@google.com> |
Remove viral dependency on libhwbinder. (2/2) find hardware/interfaces -name Android.mk -exec sed -i -e '/libhwbinder \\/d' {} \; find hardware/interfaces -name Android.bp -exec sed -i -e '/"libhwbinder"/d' {} \; ./hardware/interfaces/update-makefiles.sh Note, automotive has some actual dependencies on libhwbinder, filed b/35758626 for this. Test: everything links Test: (sanity) booted marlin on internal master with these changes Bug: 35710429 Change-Id: I6d0726c8130d00684b978efbdd48e3ae396f12e5
/hardware/interfaces/drm/1.0/default/Android.mk
|
a0da1a1c3dadac195e598890360c7b9226874ba8 |
|
13-Feb-2017 |
Steven Moreland <smoreland@google.com> |
Move hidl shims to the vendor partition. (2/2) We need google shims on the vendor partition because they are providing an implementation of a vendor defined interface. They were written by google just as a courtesy/to make the transition easier. They're basically a set for vendors to assemble their hal implementations from. Bug: 34135607 Test: marlin persist.hal.binderization on/off Change-Id: I2e2af5af39264cf290259755bb9b2eb9827a21f5
/hardware/interfaces/drm/1.0/default/Android.mk
|
da002fe6415cee1e37cc3131aafb79ddb53f01e5 |
|
19-Jan-2017 |
Jeff Tinker <jtinker@google.com> |
Reorganize drm hal modules Previously the drm and crypto plugins were separate hals. This implied a separation of implementation libraries which causes problems for some drm schemes. The reorganization combines the hals into a single interface under drm. Tests: basic gtests passing Change-Id: I5cde6ff9f60625a0219731c4dbfcaefbd9f27f88 related-to-bug: 32815560
/hardware/interfaces/drm/1.0/default/Android.mk
|
d59d36252e688b1b04661061d243ca2cde03de14 |
|
16-Dec-2016 |
Jeff Tinker <jtinker@google.com> |
Implement services for crypto+drm HALs Test: service runs, basic gtests pass bug:32815560 Change-Id: I9642f20d11805c56c46ddede64e776df5314f089
/hardware/interfaces/drm/1.0/default/Android.mk
|