Hi Mark,
On 4/7/21 11:46 AM, Mark Hatle wrote:
On 4/6/21 7:34 PM, quanyang.wang wrote:
From: Quanyang Wang <[email protected]>
When LICENSE is assigned to "CLOSED", it only means not to do the
license checking on LIC_FILES_CHKSUM which is very unreliable.
The license is still unknown for the packages with "CLOSED" lincese.
We can change the license to "MIT" and set COPYING.MIT to be the
license file.
This is incorrect. The generated PDI, CDO and HDF files are proprietary closed
source files. They are not licensed MIT.
For mb-realloc I'm not sure what the license is. I will check with our teams
and see if it should be MIT licensed.
The layer (recipes and other meta data) are intended to be MIT licensed, however
the other contents like these files often contain proprietary data. (Xilinx,
third party and/or end user created.)
The sample files we provide are licensed under at least the following license:
https://github.com/Xilinx/hdf-examples/blob/rel-v2020.3/LICENSE.md
but as the end user constructs their devices, bitstreams, etc they will
integrate additional third party IP that may have additional license
restrictions.
Thank you very much for your reply. I understand now.
And is it possible to change these packages to be a definite license? No
matter
"Proprietary", "Xilinx" or something else. The "CLOSED" license is
vague and
customers don't know if these packages can be included or enabled in their
distribution.
Thanks,
Quanyang
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#4882):
https://lists.yoctoproject.org/g/meta-xilinx/message/4882
Mute This Topic: https://lists.yoctoproject.org/mt/81905253/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/meta-xilinx/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
