From: Steven Cole <elenstev@mesatop.com>
To: "Heater, Daniel (IndSys, " "GEFanuc, VMIC)" <Daniel.Heater@gefanuc.com>
Cc: "'G. C.'" <gpc01532@hotmail.com>, linux-kernel@vger.kernel.org
Subject: RE: How to Avoid GPL Issue
Date: 01 Jul 2003 13:55:51 -0600 [thread overview]
Message-ID: <1057089350.13992.37.camel@spc9.esa.lanl.gov> (raw)
In-Reply-To: <A9D3E503844A904CB9E42AD008C1C7FDBA9BD6@vacho3misge.cho.ge.com>
On Tue, 2003-07-01 at 13:36, Heater, Daniel (IndSys, GEFanuc, VMIC)
wrote:
> > We are trying to port a third party hardware driver into Linux kernel and
> > this third party vendor does not allow us to publish the source code. Is
> > there any approach that we can avoid publicizing the third party code
> while
> > porting to Linux? Do we need to write some shim layer code in Linux kernel
>
> > to interface the third party code? How can we do that? Is there any
> document
> > or samples?
>
> It depends on what you intend to do with your port. If it is only for
> internal use (you will not distribute the ported code in any form)
> then you may not be required to supply the source code to anyone. This is
> a common interpretation of the GPL (although I can not find explicit
> language providing for this interpretation in the license).
Look here:
http://www.gnu.org/licenses/gpl-faq.html#GPLRequireSourcePostedPublic
Steven
next prev parent reply other threads:[~2003-07-01 19:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-01 19:36 How to Avoid GPL Issue Heater, Daniel (IndSys, GEFanuc, VMIC)
2003-07-01 19:55 ` Steven Cole [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-29 4:53 Dan Kegel
2003-06-27 23:04 G. C.
2003-06-28 0:03 ` root
2003-06-28 0:15 ` nick
2003-06-28 19:22 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1057089350.13992.37.camel@spc9.esa.lanl.gov \
--to=elenstev@mesatop.com \
--cc=Daniel.Heater@gefanuc.com \
--cc=gpc01532@hotmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).