summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorNathan Rossi <nathan@nathanrossi.com>2017-08-21 18:57:41 +1000
committerNathan Rossi <nathan@nathanrossi.com>2017-08-28 23:46:58 +1000
commit39f025e07644c59cd5bf55194334230f319afd55 (patch)
treec8883feacd32d35d32dde60fa415e2b98112f1ad
parent068563ffad4896f1512b3bcf97a11dc40cdbca2e (diff)
downloadmeta-xilinx-39f025e07644c59cd5bf55194334230f319afd55.tar.gz
README.md: Add paragraph for the 'xilinx' license flag
This paragraph documents the existence of recipes that rely on closed or otherwise restricted source content that can be used to compile images for targets. The content has specific licensing and legal requirements that are outside the ability or sanity of enforcement in OpenEmbedded or Yocto and as such is up to each individual user to review and comply with. This might include EULA, Export Compliance, NDAs, Redistribution, etc. Generally speaking this content is going to be protected by Xilinx's web download service which requires an account. Signed-off-by: Nathan Rossi <nathan@nathanrossi.com> Tested-by: Alistair Francis <alistair.francis@xilinx.com> Acked-by: Alistair Francis <alistair.francis@xilinx.com> Acked-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
-rw-r--r--README.md27
1 files changed, 27 insertions, 0 deletions
diff --git a/README.md b/README.md
index eef02142..fd54577a 100644
--- a/README.md
+++ b/README.md
@@ -56,3 +56,30 @@ This layer depends on:
56 URI: git://git.openembedded.org/openembedded-core 56 URI: git://git.openembedded.org/openembedded-core
57 layers: meta 57 layers: meta
58 58
59Recipe Licenses
60===============
61
62Due to licensing restrictions some recipes in this layer rely on closed source
63or restricted content provided by Xilinx. In order to use these recipes you must
64accept or agree to the licensing terms (e.g. EULA, Export Compliance, NDA,
65Redistribution, etc). This layer **does not enforce** any legal requirement, it
66is the **responsibility of the user** the ensure that they are in compliance
67with any licenses or legal requirements for content used.
68
69In order to use recipes that rely on restricted content the `xilinx` license
70flag must be white-listed in the build configuration (e.g. `local.conf`). This
71can be done on a per package basis:
72
73 LICENSE_FLAGS_WHITELIST += "xilinx_pmu-rom"
74
75or generally:
76
77 LICENSE_FLAGS_WHITELIST += "xilinx"
78
79Generally speaking Xilinx content that is provided as a restricted download
80cannot be obtained without a Xilinx account, in order to use this content you
81must first download it with your Xilinx account and place the downloaded content
82in the `downloads/` directory of your build or on a `PREMIRROR`. Attempting to
83fetch the content using bitbake will fail, indicating the URL from which to
84acquire the content.
85