From: "Chris Friesen" <cfriesen@nortel.com>
To: "Fredrik Markström" <fredrik.markstrom@avalonenterprise.com>
Cc: Robert Hancock <hancockr@shaw.ca>, linux-kernel@vger.kernel.org
Subject: Re: Developing non-commercial drivers ?
Date: Tue, 18 Nov 2008 11:17:56 -0600 [thread overview]
Message-ID: <4922F8C4.80509@nortel.com> (raw)
In-Reply-To: <7a9e70560811180852y9eb2bf6s8682609dcb10fd9f@mail.gmail.com>
Fredrik Markström wrote:
> At this point I feel that we have two possibilities, help our customer
> violate GPL or say no to the project. I'd prefer a third option where
> I could tell the customer that we can setup the project in a certain
> way (some "cleanroom" setup ?) to ensure that the results can not be
> considered derived work.
>
> Is your short answer also the definite answer considering this ?
I'm not a lawyer, and you need to consult one.
There isn't really a "definate answer" since it depends on copyright
law, which varies by region. The key question is whether the driver is
a derivative work of the kernel under copyright law. For the purposes
of copyright law this is primarily a legal question, not a technical one.
There are some that claim that a driver written for another OS and
running in linux via a shim layer could qualify (especially if the
closed-source portion is written without any knowledge of linux
internals). Nvidia is one company that does this, but there are others
as well.
Also, releasing the driver under the GPL doesn't necessarily mean
"released to the world". Technically, they would only need to provide
source code to their customers. Of course, their customers would be
free to redistribute, but it's unlikely that most of them would bother.
Chris
next prev parent reply other threads:[~2008-11-18 17:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-18 16:16 Developing non-commercial drivers ? Fredrik Markström
2008-11-18 16:29 ` Robert Hancock
2008-11-18 16:52 ` Fredrik Markström
2008-11-18 17:04 ` Robert Hancock
2008-11-18 17:17 ` Xavier Bestel
2008-11-18 17:17 ` Chris Friesen [this message]
2008-11-18 18:00 ` Radhakrishnan
2008-11-18 18:13 ` Chris Friesen
2008-11-18 18:33 ` linux-os (Dick Johnson)
2008-11-18 17:40 ` Alan Cox
2008-11-22 18:16 ` Dr. David Alan Gilbert
2008-11-18 17:32 ` Alan Cox
2008-11-18 19:25 ` Valdis.Kletnieks
2008-11-18 19:29 ` Alan Cox
2008-11-18 20:20 ` Theodore Tso
2008-11-18 21:13 ` Fredrik Markström
2008-11-18 23:28 ` Theodore Tso
2008-11-19 18:38 ` Lennart Sorensen
2008-11-19 22:32 ` Fredrik Markström
2008-11-19 22:47 ` Lennart Sorensen
2008-12-01 0:19 ` Enrico Weigelt
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=4922F8C4.80509@nortel.com \
--to=cfriesen@nortel.com \
--cc=fredrik.markstrom@avalonenterprise.com \
--cc=hancockr@shaw.ca \
--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