Conversation

Notices

1. Free Silicon Foundation (fsi@mastodon.f-si.org)'s status on Friday, 21-Dec-2018 02:50:59 EST Free Silicon Foundation

   @kmicu

   Not all CAD tool vendors publish part or all of their licenses, hence the list below is not exhaustive:
   https://www.synopsys.com/verification/prototyping/haps/synopsys-license-agreement.html (section 2.2 comma 3)
   http://s3.mentor.com/company/enduser-english.pdf (section 4.1)

   Those using such tools should refer to the text of their licenses directly.

   1. clacke@libranet.de ❌ (notclacke@pleroma.soykaf.com)'s status on Saturday, 16-Mar-2019 02:49:11 EDT clacke@libranet.de ❌

      in reply to
      For context, the Synopsys LA §2.2 and item 3 say:
      
      > [ . . . ] when you are granted a license to any Implementation IP, you will have a nonexclusive right to:
      
      > [ . . . ] distribute the Implementation IP in netlist or GDSII format as part of any of your Integrated Designs to any third party that provides foundry services to you, solely for the purpose of having that foundry make physical implementations of one or more of entire Integrated Designs of yours, as long as the third-party foundry is subject to confidentiality obligations regarding the Implementation IP that are no less restrictive than the confidentiality obligations in this agreement [ . . . ]
      1. clacke@libranet.de ❌ (notclacke@pleroma.soykaf.com)'s status on Saturday, 16-Mar-2019 02:50:46 EDT clacke@libranet.de ❌

         in reply to
         It's a similar situation to how gcc compilation produces binaries that contain bits and pieces from libgcc, except that the GCC license terms explicitly do *not* make the resulting binary subject to the GPLv3 (on the condition that you don't mix GCC with proprietary plugins). The proprietary silicon IP vendors are far more jealously guarding their designs.
         
         https://www.gnu.org/licenses/gcc-exception-faq.html
         
         @clacke