From: Mika Liljeberg <mika.liljeberg@welho.com>
To: Dave Jones <davej@redhat.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Dennis Freise <Cataclysm@final-frontier.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: New ATI FireGL driver supports 2.6 kernel
Date: Tue, 09 Sep 2003 20:41:47 +0300 [thread overview]
Message-ID: <1063129307.777.8.camel@hades> (raw)
In-Reply-To: <20030909075023.GA8065@redhat.com>
On Tue, 2003-09-09 at 10:50, Dave Jones wrote:
> On Tue, Sep 09, 2003 at 02:02:25AM +0100, Alan Cox wrote:
>
> > > Linking GPL code to binary .o files, and then disabling the
> > > MODULE_LICENSE("GPL") smells pretty fishy to me.
> >
> > If all the code they include is their own then they could have dual
> > licensed it. If not and they are modifying core kernel code to add hooks
> > for their code they aren't likely to get past the preliminary arguments
> > about a GPL violation and it being a derivative work.
>
> For one it links in the GPL'd nvidia GART module.
Hmm, dunno about that:
$ grep -i license nvidia-agp.c
MODULE_LICENSE("GPL and additional rights");
All the rest seems to be under a BSD style license.
MikaL
next prev parent reply other threads:[~2003-09-09 17:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-08 22:47 New ATI FireGL driver supports 2.6 kernel Dennis Freise
2003-09-08 22:54 ` Dave Jones
2003-09-09 1:02 ` Alan Cox
2003-09-09 7:50 ` Dave Jones
2003-09-09 13:24 ` Alan Cox
2003-09-09 17:41 ` Mika Liljeberg [this message]
2003-09-09 17:53 ` Dave Jones
2003-09-09 18:16 ` Mika Liljeberg
2003-09-09 21:00 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2003-09-08 23:07 Dennis Freise
2003-09-09 1:04 ` Alan Cox
2003-09-09 1:25 ` Mike Fedyk
2003-09-09 8:51 ` Geert Uytterhoeven
2003-09-09 6:25 ` Matias Alejo Garcia
2003-09-09 5:47 ` Brien B.
2003-09-08 18:05 Mika Liljeberg
2003-09-08 18:18 ` Stian Jordet
2003-09-08 18:27 ` Mika Liljeberg
2003-09-08 18:41 ` Dave Jones
2003-09-08 19:03 ` Arjan van de Ven
2003-09-08 19:55 ` Dave Jones
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=1063129307.777.8.camel@hades \
--to=mika.liljeberg@welho.com \
--cc=Cataclysm@final-frontier.org \
--cc=alan@lxorguk.ukuu.org.uk \
--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