Posted: February 10, 2012 21:20 by cpratt
As discussed in OCAP_RI-588, there are issues with the mpeos_podGetCCIBits() API. More importantly, by providing a "program" argument, it's presuming the platform is tracking program-level information that isn't assumed by any other mpeos-level APIs.
The MPEOS API change described in porting forum post Proposed MPEOS change for signaling of CCI during live/DVR decode/playback means that the stack is now notified of CCI status when presenting/recording - which are the only program-level operations that require access to encrypted streams. The org.ocap.hardware.CopyControl API can utilize the last-provided notifications to return CCI for a given Service.
Leveraging this, mpeos_podGetCCIBits() should no longer be needed as its only use is for org.ocap.hardware.CopyControl. So I'm proposing it be removed from MPEOS.
Note: It's not clear if org.ocap.hardware.CopyControl is used by any applications. But it has some obvious issues of its own...