... | ... | @@ -348,6 +348,9 @@ The rationale document explains all this with other words: |
|
|
> anyway (albeit within the mechanism), we felt we should be more
|
|
|
> explicit about this.
|
|
|
|
|
|
#### Q: More specifically, I would like to use a [GPL2-licensed core](https://wiki.analog.com/resources/fpga/peripherals/jesd204) in my design. What are the consequences on the licensing of the rest of the files in that design?
|
|
|
|
|
|
A: If you release a product based on that design, for example if you are shipping a product containing an FPGA whose configuration bitstream has been derived from the GPL2-licensed and other sources, then according to the GPL2 terms, you are distributing the "Program" in object code form. This means you need to provide access to all the sources, and these sources must all be licensed under GPL2. This is where incompatibility issues can arise. Permissive licences such as Solderpad and CERN-OHL-P will allow re-interpreting the licensing terms in the licence so that you can treat the files as licensed under GPL2. Reciprocal licences such as CERN-OHL-L and CERN-OHL-S will not allow this re-interpretation. This makes it impossible to use cores licensed under GPL2 (or GPL3 for that matter) in a design which also uses cores licensed under CERN-OHL-L and CERN-OHL-S.
|
|
|
|
|
|
|
|
|
### Files
|
... | ... | |