LGPL HDL in larger FPGA designCan I dynamically call a LGPL/GPL software in my closed-source application?Changing QT library licence for application from LGPL to commercialHow can LGPL and proprietary licenses be combined?Provide closed-source application with LGPL-LibrariesDynamic linking LGPL library and licensing in Windows Store appLGPL and static linking when third-party tools are required - providing an alternate version that can accept a replacement LGPL libraryDo I have to include attribution and license files for an LGPL-licensed library together with a “work that uses the library”?Call MS-PL library in LGPL codeHow To Package A Basic PySide2 Desktop Application Under LGPL For Sale - EXAMPLE PLEASE

What is this sticking out of my wall?

How to set any file manager in Linux to show the duration like the Length feature in Windows Explorer?

Change-due function

How should we understand "unobscured by flying friends" in this context?

Is there a star over my head?

The pirate treasure of Leatherback Atoll

Why can linguists decide which use of language is correct and which is not?

Is a MySQL database a viable alternative to LDAP?

Are personality traits, ideals, bonds, and flaws required?

WPF MVVM ColorLister with navigation

More than three domains hosted on the same IP address

Why is it that I have to play this note on the piano as A sharp?

pgfgantt: month displayed as single letter

Distinguishing between octahedral and tetrahedral holes

How do I decide when to use MAPE, SMAPE and MASE for time series analysis on stock forecasting

How can I finish my PhD?

What happens when a file that is 100% paged in to the page cache gets modified by another process

How is lower/no gravity simulated on a planet with gravity, without leaving the surface?

Short story: Interstellar inspector senses "off" nature of planet hiding aggressive culture

How strong is aircraft-grade spruce?

What makes an ending "happy"?

How do you say "to hell with everything" in French?

How do I reference a custom counter that shows the section number?

Is mountain bike good for long distances?



LGPL HDL in larger FPGA design


Can I dynamically call a LGPL/GPL software in my closed-source application?Changing QT library licence for application from LGPL to commercialHow can LGPL and proprietary licenses be combined?Provide closed-source application with LGPL-LibrariesDynamic linking LGPL library and licensing in Windows Store appLGPL and static linking when third-party tools are required - providing an alternate version that can accept a replacement LGPL libraryDo I have to include attribution and license files for an LGPL-licensed library together with a “work that uses the library”?Call MS-PL library in LGPL codeHow To Package A Basic PySide2 Desktop Application Under LGPL For Sale - EXAMPLE PLEASE






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








1















There is a project called NetFPGA that has HDL code for various Ethernet uses in an FPGA. The project is listed as LGPL. From a software perspective, my understanding is that if you dynamically link a LGPL library you can use it in a commercial application. How would this work in the case of an FPGA design? The concept of dynamic linking does not really exist in the hardware design.



If I use the LGPL HDL in a larger design would I have to release the source of the whole project?
If I edit the LGPL HDL and use it in a larger design would I have to release the source of the LGPL HDL and/or the whole project?



(https://github.com/NetFPGA/NetFPGA-public/wiki/Licensing)










share|improve this question






























    1















    There is a project called NetFPGA that has HDL code for various Ethernet uses in an FPGA. The project is listed as LGPL. From a software perspective, my understanding is that if you dynamically link a LGPL library you can use it in a commercial application. How would this work in the case of an FPGA design? The concept of dynamic linking does not really exist in the hardware design.



    If I use the LGPL HDL in a larger design would I have to release the source of the whole project?
    If I edit the LGPL HDL and use it in a larger design would I have to release the source of the LGPL HDL and/or the whole project?



    (https://github.com/NetFPGA/NetFPGA-public/wiki/Licensing)










    share|improve this question


























      1












      1








      1








      There is a project called NetFPGA that has HDL code for various Ethernet uses in an FPGA. The project is listed as LGPL. From a software perspective, my understanding is that if you dynamically link a LGPL library you can use it in a commercial application. How would this work in the case of an FPGA design? The concept of dynamic linking does not really exist in the hardware design.



      If I use the LGPL HDL in a larger design would I have to release the source of the whole project?
      If I edit the LGPL HDL and use it in a larger design would I have to release the source of the LGPL HDL and/or the whole project?



      (https://github.com/NetFPGA/NetFPGA-public/wiki/Licensing)










      share|improve this question














      There is a project called NetFPGA that has HDL code for various Ethernet uses in an FPGA. The project is listed as LGPL. From a software perspective, my understanding is that if you dynamically link a LGPL library you can use it in a commercial application. How would this work in the case of an FPGA design? The concept of dynamic linking does not really exist in the hardware design.



      If I use the LGPL HDL in a larger design would I have to release the source of the whole project?
      If I edit the LGPL HDL and use it in a larger design would I have to release the source of the LGPL HDL and/or the whole project?



      (https://github.com/NetFPGA/NetFPGA-public/wiki/Licensing)







      lgpl hardware






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked 10 hours ago









      Eric JohnsonEric Johnson

      1284 bronze badges




      1284 bronze badges























          1 Answer
          1






          active

          oldest

          votes


















          2
















          The aim of the LGPL license is that people can replace the LGPL code in a larger project, without requiring that the complete source code of the larger project is disclosed.



          I am not familiar with how HDL works for FPGA design, but the LGPL requires that



          • you release the modified LGPL HDL code under the LGPL license

          • you release the rest of the full project in a format that makes it possible to re-create your FPGA design with another version of the LGPL code. This format does not need to be human-readable or source code.

          • you give recipients of the FPGA design the right to replace the LGPL portion of it.





          share|improve this answer



























            Your Answer








            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "619"
            ;
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function()
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled)
            StackExchange.using("snippets", function()
            createEditor();
            );

            else
            createEditor();

            );

            function createEditor()
            StackExchange.prepareEditor(
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            imageUploader:
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/4.0/"u003ecc by-sa 4.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            ,
            noCode: true, onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );














            draft saved

            draft discarded
















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fopensource.stackexchange.com%2fquestions%2f8767%2flgpl-hdl-in-larger-fpga-design%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            2
















            The aim of the LGPL license is that people can replace the LGPL code in a larger project, without requiring that the complete source code of the larger project is disclosed.



            I am not familiar with how HDL works for FPGA design, but the LGPL requires that



            • you release the modified LGPL HDL code under the LGPL license

            • you release the rest of the full project in a format that makes it possible to re-create your FPGA design with another version of the LGPL code. This format does not need to be human-readable or source code.

            • you give recipients of the FPGA design the right to replace the LGPL portion of it.





            share|improve this answer





























              2
















              The aim of the LGPL license is that people can replace the LGPL code in a larger project, without requiring that the complete source code of the larger project is disclosed.



              I am not familiar with how HDL works for FPGA design, but the LGPL requires that



              • you release the modified LGPL HDL code under the LGPL license

              • you release the rest of the full project in a format that makes it possible to re-create your FPGA design with another version of the LGPL code. This format does not need to be human-readable or source code.

              • you give recipients of the FPGA design the right to replace the LGPL portion of it.





              share|improve this answer



























                2














                2










                2









                The aim of the LGPL license is that people can replace the LGPL code in a larger project, without requiring that the complete source code of the larger project is disclosed.



                I am not familiar with how HDL works for FPGA design, but the LGPL requires that



                • you release the modified LGPL HDL code under the LGPL license

                • you release the rest of the full project in a format that makes it possible to re-create your FPGA design with another version of the LGPL code. This format does not need to be human-readable or source code.

                • you give recipients of the FPGA design the right to replace the LGPL portion of it.





                share|improve this answer













                The aim of the LGPL license is that people can replace the LGPL code in a larger project, without requiring that the complete source code of the larger project is disclosed.



                I am not familiar with how HDL works for FPGA design, but the LGPL requires that



                • you release the modified LGPL HDL code under the LGPL license

                • you release the rest of the full project in a format that makes it possible to re-create your FPGA design with another version of the LGPL code. This format does not need to be human-readable or source code.

                • you give recipients of the FPGA design the right to replace the LGPL portion of it.






                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered 8 hours ago









                Bart van Ingen SchenauBart van Ingen Schenau

                8,06117 silver badges30 bronze badges




                8,06117 silver badges30 bronze badges































                    draft saved

                    draft discarded















































                    Thanks for contributing an answer to Open Source Stack Exchange!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid


                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.

                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fopensource.stackexchange.com%2fquestions%2f8767%2flgpl-hdl-in-larger-fpga-design%23new-answer', 'question_page');

                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Invision Community Contents History See also References External links Navigation menuProprietaryinvisioncommunity.comIPS Community ForumsIPS Community Forumsthis blog entry"License Changes, IP.Board 3.4, and the Future""Interview -- Matt Mecham of Ibforums""CEO Invision Power Board, Matt Mecham Is a Liar, Thief!"IPB License Explanation 1.3, 1.3.1, 2.0, and 2.1ArchivedSecurity Fixes, Updates And Enhancements For IPB 1.3.1Archived"New Demo Accounts - Invision Power Services"the original"New Default Skin"the original"Invision Power Board 3.0.0 and Applications Released"the original"Archived copy"the original"Perpetual licenses being done away with""Release Notes - Invision Power Services""Introducing: IPS Community Suite 4!"Invision Community Release Notes

                    Canceling a color specificationRandomly assigning color to Graphics3D objects?Default color for Filling in Mathematica 9Coloring specific elements of sets with a prime modified order in an array plotHow to pick a color differing significantly from the colors already in a given color list?Detection of the text colorColor numbers based on their valueCan color schemes for use with ColorData include opacity specification?My dynamic color schemes

                    Ласкавець круглолистий Зміст Опис | Поширення | Галерея | Примітки | Посилання | Навігаційне меню58171138361-22960890446Bupleurum rotundifoliumEuro+Med PlantbasePlants of the World Online — Kew ScienceGermplasm Resources Information Network (GRIN)Ласкавецькн. VI : Літери Ком — Левиправивши або дописавши її