5

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 ...


4

How would [the LGPL] work in the case of an FPGA design? It doesn't. At least, not very well. You've correctly identified the problem with this license construction. The only situation I can think of where the LGPL might be usefully applied to an FPGA design would be in a design that uses dynamic reconfiguration. In particular, this might be relevant to ...


1

If I use the LGPL HDL in a larger design would I have to release the source of the whole project? Possibly, but if so that's likely a limitation of the FPGA development tooling. If the tooling were good, it would let you isolate the LGPL'd component's placement in the design specifically to facilitate replacing it in-place without rebuilding the entire ...


Only top voted, non community-wiki answers of a minimum length are eligible