rk3399: licensing of hdcp.bin

[vagrantc]

The file plat/rockchip/rk3399/drivers/dp/hdcp.bin is a binary without source.

In the commit it was introduced, it suggests it is not open source:

commit c76631c52b0b1550ff182c177555485700274314
Author: Ziyuan Xu [email protected]
Date: Thu Oct 27 19:07:35 2016 +0800

rockchip: include hdcp.bin and declare hdcp key decryption handler                                         

For some reason, HDCP key decrytion can't open source in ATF, so we                                        
build it as hdcp.bin. Besides declare the handler for decrypting.

Change-Id: Ia67ff2442ab43cb3ee4875b3d59cc1608e854b4b                                                       
Signed-off-by: Ziyuan Xu <[email protected]>
Signed-off-by: Caesar Wang <[email protected]>

Is it possible to get additional clarity on the licensing of this file? If not possible, would it be possible or meaningful to have a variant build without this binary included? Many free software distributions, such as Debian, require building from source in order to be allowed in the distribution.

Thanks!

[ghost]

@rockchip-linux

[jwerner-chromium]

I'll leave the license question to Rockchip, but it should be pretty easy to add a compile-time option to optionally exclude this binary. It is only needed for HDCP support (a DRM feature for video streaming), if you don't care about that the rest of the firmware should work perfectly fine without it. Just change rk3399/plat_sip_calls.c to not handle the RK_SIP_HDCP* SMCs when this option is set, and then exclude rk3399/drivers/dp/cdn_dp.c and the blob from rk3399/platform.mk.

[arm-tf-bot]

Hello @vagrantc!

Thank you for raising an issue for Trusted Firmware-A.

The TF-A project has now migrated to www.trustedfirmware.org. This issue tracker will still remain accessible for some time, but only for historical reasons. From now on you should raise any new issues on trustedfirmware.org.

How do I raise issues for TF-A?

Please use our new issue tracking board. For this you just need to login with your existing GitHub account. We also have a guide to help you raise the issue with the appropriate labels and tags. This way it will be easier for both you and us to track and address the issue most effectively.

What if I face any problems?

You can send us an email in the public TF-A mailing list. Here you can also find all the mailing lists for all the projects hosted under trustedfirmware.org.

We are looking forward to seeing you in trustedfirmware.org!

The Trusted Firmware-A team

[ssg-bot]

Hello @vagrantc!

Thank you for raising an issue for Trusted Firmware-A.

The TF-A project has now migrated to www.trustedfirmware.org. This issue tracker will still remain accessible for some time, but only for historical reasons. From now on you should raise any new issues on trustedfirmware.org.

How do I raise issues for TF-A?

Please use our new issue tracking board. For this you just need to login with your existing GitHub account. We also have a guide to help you raise the issue with the appropriate labels and tags. This way it will be easier for both you and us to track and address the issue most effectively.

What if I face any problems?

You can send us an email in the public TF-A mailing list. Here you can also find all the mailing lists for all the projects hosted under trustedfirmware.org.

We are looking forward to seeing you in trustedfirmware.org!

The Trusted Firmware-A team