From: Arjan van de Ven <arjan@infradead.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Dave Jones <davej@redhat.com>,
linux-kernel@vger.kernel.org, adaplas@pol.net
Subject: Re: nvidia fb licensing issue.
Date: Sun, 13 Mar 2005 09:18:33 +0100 [thread overview]
Message-ID: <1110701914.6278.18.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20050312215936.513039a6.akpm@osdl.org>
On Sat, 2005-03-12 at 21:59 -0800, Andrew Morton wrote:
> Dave Jones <davej@redhat.com> wrote:
> >
> > The nvidia framebuffer code added recently is marked as
> > MODULE_LICENSE(GPL), but some things seem a little odd to me..
> >
> > 1. The boilerplate at the top of drivers/video/nvidia/nv_dma.h,
> > drivers/video/nvidia/nv_local.h, and drivers/video/nvidia/nv_hw.c
> > doesn't seem to be a GPL-compatible license. It seems to be an nvidia
> > specific license with an advertising clause, and something that
> > adds restrictions on rights of U.S. Govt end users.
> >
> > 2. Some of these files clearly came from XFree86 judging from
> > the CVS idents in the source. Was this XFree86 code
> > dual-licensed by its original authors ? If so, it isn't clear.
>
> Does
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11/2.6.11-mm3/broken-out/fbdev-nvidia-licensing-clarification.patch
>
> clear things up?
somewhat; it would even make sense to consider dual licensing that thing
(like most other not-originally-gpl code in the kernel) to clarify the
legal status for real. Otherwise if you merge it with GPL it sort of
becomes GPL only.. (due to the freedom of MIT and the viral nature of
GPL) and I suspect the intention of the author was to keep allowing MIT
use...
next prev parent reply other threads:[~2005-03-13 8:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-13 4:24 Dave Jones
2005-03-13 5:59 ` Andrew Morton
2005-03-13 8:18 ` Arjan van de Ven [this message]
2005-03-14 2:03 ` Jon Smirl
2005-03-14 6:53 ` Arjan van de Ven
2005-03-15 10:32 ` Dave Airlie
2005-03-15 11:06 ` Arjan van de Ven
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=1110701914.6278.18.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=adaplas@pol.net \
--cc=akpm@osdl.org \
--cc=davej@redhat.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
all inboxes | Powered by JetHome®