Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
comp.lang.vhdl
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
Message from discussion GNU Lesser Public License and Soft IP
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Rich Webb  
View profile  
 More options Oct 12 2009, 4:16 am
Newsgroups: comp.lang.verilog, comp.lang.vhdl
From: Rich Webb <bbew...@mapson.nozirev.ten>
Date: Mon, 12 Oct 2009 04:16:02 -0400
Local: Mon, Oct 12 2009 4:16 am
Subject: Re: GNU Lesser Public License and Soft IP
Print | View thread | Show original | Report this message | Find messages by this author
On Mon, 12 Oct 2009 09:28:25 +0200, Pieter Hulshoff <phuls...@xs4all.nl>
wrote:

>Hello Steven,

>> I am looking through the GNU Lesser General Public License (LGPL) and
>> trying to understand how it applies to H/W i.e. Using the vhdl or
>> verilog IP in one of our products.

>> I have seen where it is stated that IP's license under LGPL can be
>> used in propriety products, but I don't know how one comes to this
>> conclusion from reading the LGPL.

>You should keep in mind that the (L)GPL licenses were primarily written
>with software designs in mind. As such, not all terminology maps well
>to hardware designs.

>The main difference between the GPL and the LPGL is that embedding GPL
>code within your design requires you to make your entire design available
>under the GPL, while LGPL only requires you to make the LGPL code and any
>changes you make to the LGPL code available under the LGPL.

That's correct only if the application can be supplied as an object
module that dynamically links to the LGPL code. If that's not possible
(and I'm not sure how it could be in any HDL environment) then
sufficient source code must be supplied to allow an interested user to
recreate the application with the current or a modified version of the
LGPL code. See Section 4.d of the LGPL. As you say, it's aimed at a
conventional software model.

--
Rich Webb     Norfolk, VA


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google