... | @@ -92,7 +92,7 @@ version. |
... | @@ -92,7 +92,7 @@ version. |
|
|
|
|
|
-----
|
|
-----
|
|
|
|
|
|
## Questions about reciprocal hardware licensing
|
|
## Questions about hardware licensing
|
|
|
|
|
|
#### Q: Copyright does not cover hardware. How do you implement strongly reciprocal licensing in CERN OHL v2?
|
|
#### Q: Copyright does not cover hardware. How do you implement strongly reciprocal licensing in CERN OHL v2?
|
|
|
|
|
... | @@ -125,6 +125,15 @@ files. CERN OHL v2 provides two mechanisms to ensure that: |
... | @@ -125,6 +125,15 @@ files. CERN OHL v2 provides two mechanisms to ensure that: |
|
of the Complete Source.
|
|
of the Complete Source.
|
|
|
|
|
|
|
|
|
|
|
|
#### 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 the three
|
|
|
|
variants of the licence. Therefore, you can reference them (as when you
|
|
|
|
draw a symbol for them in a schematic) without any need to distribute
|
|
|
|
their associated sources. In this case the IC may be a custom design
|
|
|
|
also licensed under CERN OHL, but that is an independent decision of its
|
|
|
|
Licensor.
|
|
|
|
|
|
-----
|
|
-----
|
|
|
|
|
|
## Questions about software
|
|
## Questions about software
|
... | | ... | |