... | @@ -144,11 +144,11 @@ files. CERN-OHL-S provides two mechanisms to ensure that: |
... | @@ -144,11 +144,11 @@ files. CERN-OHL-S provides two mechanisms to ensure that: |
|
#### Q: My PCB is made of ICs, which are made of plastic, metal and a chip, which is itself made of silicon. How far do I need to go in terms of providing the source designs for all this?
|
|
#### Q: My PCB is made of ICs, which are made of plastic, metal and a chip, which is itself made of silicon. How far do I need to go in terms of providing the source designs for all this?
|
|
|
|
|
|
A: The ICs in your design qualify as "Available Components" in
|
|
A: The ICs in your design qualify as "Available Components" in
|
|
CERN-OHL-S and CERN-OHL-L. Therefore, you can reference them (as when
|
|
CERN-OHL-S and CERN-OHL-L (the two cases where this question makes
|
|
you draw a symbol for them in a schematic) without any need to
|
|
sense). Therefore, as a Licensee, you can reference them (as when you
|
|
distribute their associated sources. In this case the IC may be a custom
|
|
draw a symbol for them in a schematic) without any need to distribute
|
|
design also licensed under CERN OHL, but that is an independent decision
|
|
their associated sources. In this case the IC may be a custom design
|
|
of its
|
|
also licensed under CERN OHL, but that is an independent decision of its
|
|
Licensor.
|
|
Licensor.
|
|
|
|
|
|
-----
|
|
-----
|
... | @@ -171,7 +171,7 @@ design. |
... | @@ -171,7 +171,7 @@ design. |
|
|
|
|
|
## Questions about FPGA and ASIC design
|
|
## Questions about FPGA and ASIC design
|
|
|
|
|
|
#### Q: An ASIC or FPGA design is licensed under CERN OHL v2. What are the implications regarding proprietary primitives and macros used in the design?
|
|
#### Q: An FPGA design is licensed under CERN-OHL-S or CERN-OHL-L. What are the implications regarding proprietary primitives and macros used in the design?
|
|
|
|
|
|
A: Proprietary blocks readily available in the design tools fall under
|
|
A: Proprietary blocks readily available in the design tools fall under
|
|
the definition of "Available Components" and it is therefore not
|
|
the definition of "Available Components" and it is therefore not
|
... | @@ -179,7 +179,19 @@ required to ship them when you distribute the design sources or products |
... | @@ -179,7 +179,19 @@ required to ship them when you distribute the design sources or products |
|
based on those
|
|
based on those
|
|
designs.
|
|
designs.
|
|
|
|
|
|
#### Q: Is an FPGA bitstream a Product according to the definition of Product in CERN OHL v2?
|
|
#### Q: An ASIC design is licensed under CERN-OHL-S or CERN-OHL-L. What are the implications regarding proprietary primitives and macros used in the design?
|
|
|
|
|
|
|
|
This case is slightly more complicated than the one for FPGA designs. We
|
|
|
|
did not find good wording to make sure the primitive libraries (e.g. the
|
|
|
|
so-called [PDKs](https://en.wikipedia.org/wikis/Process_design_kit))
|
|
|
|
were excluded from the distribution obligations. Not excluding them
|
|
|
|
would make the licences applicable in only an extremely reduced number
|
|
|
|
of cases. In the end we decided to allow the original Licensor to mark
|
|
|
|
some components as "Available Components" so that the PDK case and
|
|
|
|
others can be easily
|
|
|
|
covered.
|
|
|
|
|
|
|
|
#### Q: Is an FPGA bitstream a Product according to the definition of Product in CERN OHL?
|
|
|
|
|
|
A: Yes, a bitstream results from the processing of source files and is
|
|
A: Yes, a bitstream results from the processing of source files and is
|
|
therefore a Product, provided that those sources are licensed under the
|
|
therefore a Product, provided that those sources are licensed under the
|
... | @@ -198,10 +210,10 @@ infringing any of my patents when you use that design for all purposes |
... | @@ -198,10 +210,10 @@ infringing any of my patents when you use that design for all purposes |
|
CERN OHL allows (studying, modifying, making hardware, selling it...).
|
|
CERN OHL allows (studying, modifying, making hardware, selling it...).
|
|
This is meant to reassure you as a Licensee and therefore favour
|
|
This is meant to reassure you as a Licensee and therefore favour
|
|
adoption of designs licensed under the CERN OHL. Conversely, if you sue
|
|
adoption of designs licensed under the CERN OHL. Conversely, if you sue
|
|
me for patent infringement in that particular design, you will loose all
|
|
me for patent infringement in that particular design, you will lose all
|
|
the rights I granted you in the licence. This two-way section on patents
|
|
the rights I granted you in the licence. This two-way section on patents
|
|
is intended to provide for a much reassuring environment when it comes
|
|
is intended to provide for a reassuring environment when it comes to
|
|
to sharing hardware designs.
|
|
sharing hardware designs.
|
|
|
|
|
|
-----
|
|
-----
|
|
|
|
|
... | @@ -217,15 +229,15 @@ same happens in hardware. We use the word "reciprocal" instead of |
... | @@ -217,15 +229,15 @@ same happens in hardware. We use the word "reciprocal" instead of |
|
to copyright. So, when you use the licence, you need to add a Notice to
|
|
to copyright. So, when you use the licence, you need to add a Notice to
|
|
your designs with one of the three following suffixes: S, L or P:
|
|
your designs with one of the three following suffixes: S, L or P:
|
|
|
|
|
|
- CERN-OHL2-S is a strongly reciprocal licence. For example, if you
|
|
- CERN-OHL-S is a strongly reciprocal licence. For example, if you
|
|
release HDL files under CERN-OHL2-S and then somebody uses those
|
|
release HDL files under CERN-OHL-S and then somebody uses those
|
|
files in their FPGA, when they distribute the bitstream (either
|
|
files in their FPGA, when they distribute the bitstream (either
|
|
putting it online or shipping a product with it) they need to make
|
|
putting it online or shipping a product with it) they need to make
|
|
the rest of the HDL design available under CERN-OHL2-S as well.
|
|
the rest of the HDL design available under CERN-OHL-S as well.
|
|
- CERN-OHL2-L is a weakly reciprocal licence. For the example above,
|
|
- CERN-OHL-L is a weakly reciprocal licence. For the example above, if
|
|
if you release your part of the design under CERN-OHL2-L, somebody
|
|
you release your part of the design under CERN-OHL-L, somebody who
|
|
who distributes a bitstream which includes your part does not need
|
|
distributes a bitstream which includes your part does not need to
|
|
to distribute the rest of the design files as well.
|
|
distribute the rest of the design files as well.
|
|
- CERN-OHL2-P is a permissive licence. It allows people to take your
|
|
- CERN-OHL2-P is a permissive licence. It allows people to take your
|
|
code, relicense it and use it without any obligation to distribute
|
|
code, relicense it and use it without any obligation to distribute
|
|
the sources when they ship a product.
|
|
the sources when they ship a product.
|
... | @@ -235,7 +247,7 @@ your designs with one of the three following suffixes: S, L or P: |
... | @@ -235,7 +247,7 @@ your designs with one of the three following suffixes: S, L or P: |
|
In general, it is good to keep notices in the design files as simple as
|
|
In general, it is good to keep notices in the design files as simple as
|
|
possible. For example, in your circuit schematics you can have in each
|
|
possible. For example, in your circuit schematics you can have in each
|
|
page a little square with a notice inside saying "Copyright XYZ, 2018
|
|
page a little square with a notice inside saying "Copyright XYZ, 2018
|
|
Licensed under CERN-OHL2-S". In the layout, you could have a similar box
|
|
Licensed under CERN-OHL-S". In the layout, you could have a similar box
|
|
in one of the documentation layers. Then, for more involved notices, you
|
|
in one of the documentation layers. Then, for more involved notices, you
|
|
can use a NOTICE text file in the top directory of the project. One
|
|
can use a NOTICE text file in the top directory of the project. One
|
|
example of such more involved notices would be one where you specify
|
|
example of such more involved notices would be one where you specify
|
... | @@ -249,18 +261,18 @@ packaging. |
... | @@ -249,18 +261,18 @@ packaging. |
|
|
|
|
|
#### Q: What happens to the rights of the Licensees of a Licensor if the rights of the Licensor under this licence are terminated?
|
|
#### Q: What happens to the rights of the Licensees of a Licensor if the rights of the Licensor under this licence are terminated?
|
|
|
|
|
|
A: It's his rights as licensee that terminate. He is still a licensor,
|
|
A: It's his/her rights as Licensee that terminate. (S)he is still a
|
|
and therefore the rights of downstream licensees are not
|
|
Licensor, and therefore the rights of downstream Licensees are not
|
|
affected.
|
|
affected.
|
|
|
|
|
|
-----
|
|
-----
|
|
|
|
|
|
## Questions about distribution
|
|
## Questions about distribution
|
|
|
|
|
|
#### Q: Does private distribution of sources or products trigger any obligations?
|
|
#### Q: Does private distribution of sources or products trigger any obligations in CERN-OHL-S and CERN-OHL-L?
|
|
|
|
|
|
A: If you distribute a product privately, and the sources for that
|
|
A: If you distribute a product privately, and the sources for that
|
|
product are licensed under CERN-OHL2-S or CERN-OHL2-L, then you need to
|
|
product are licensed under CERN-OHL-S or CERN-OHL-L, then you need to
|
|
make the sources available to the recipient of that product. No need to
|
|
make the sources available to the recipient of that product. No need to
|
|
distribute them more widely. The recipient of those sources of course
|
|
distribute them more widely. The recipient of those sources of course
|
|
has the right to make them available to the public.
|
|
has the right to make them available to the public.
|
... | @@ -269,10 +281,9 @@ has the right to make them available to the public. |
... | @@ -269,10 +281,9 @@ has the right to make them available to the public. |
|
|
|
|
|
## Questions on licence compatibility
|
|
## Questions on licence compatibility
|
|
|
|
|
|
#### Q: Is CERN OHL v2 compatible with GPL?
|
|
#### Q: Is CERN OHL compatible with GPL?
|
|
|
|
|
|
A: No. From the [explanatory
|
|
A: No. From the rationale document:
|
|
document](https://www.ohwr.org/5994):
|
|
|
|
|
|
|
|
> We thought hard about compatibility with other licences. An earlier
|
|
> We thought hard about compatibility with other licences. An earlier
|
|
> version of the draft contained a mechanism for options, and a specific
|
|
> version of the draft contained a mechanism for options, and a specific
|
... | | ... | |