From: David Newall <davidn@davidnewall.com>
To: Chris Friesen <cfriesen@nortel.com>
Cc: Kaz Kylheku <kkylheku@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: GPL question: using large contiguous memory in proprietary driver.
Date: Wed, 15 Oct 2008 15:53:08 +1030 [thread overview]
Message-ID: <48F57E3C.5060708@davidnewall.com> (raw)
In-Reply-To: <48F55398.10005@nortel.com>
Chris Friesen wrote:
> If you sit down and write a new driver for linux, is is arguable that
> it is in fact a derivative work of the kernel and is thus subject to
> the GPL.
This is essentially the argument that SCO used when they sued IBM over
IBM's printing technology.
next prev parent reply other threads:[~2008-10-15 5:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-14 21:56 GPL question: using large contiguous memory in proprietary driver Kaz Kylheku
2008-10-14 22:05 ` Peter Zijlstra
2008-10-14 22:10 ` Alexey Dobriyan
2008-10-14 23:18 ` Kaz Kylheku
2008-10-14 22:12 ` Chris Friesen
2008-10-14 23:23 ` Kaz Kylheku
2008-10-15 2:21 ` Chris Friesen
2008-10-15 5:23 ` David Newall [this message]
2008-10-15 5:30 ` Adrian Bunk
2008-10-15 9:05 ` Alan Cox
2008-10-15 13:21 ` John Stoffel
2008-10-14 23:39 ` Kaz Kylheku
2008-10-15 11:26 ` Nick Piggin
2008-10-15 13:54 ` Mark Hounschell
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=48F57E3C.5060708@davidnewall.com \
--to=davidn@davidnewall.com \
--cc=cfriesen@nortel.com \
--cc=kkylheku@gmail.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