mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: <Hell.Surfers@cwctv.net>
To: riel@conectiva.com.br, linux-kernel@vger.kernel.org
Subject: Re: GPL and Nvidia
Date: Wed, 1 Jan 2003 18:05:32 +0000	[thread overview]
Message-ID: <0c1c12302180113DTVMAIL8@smtp.cwctv.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 239 bytes --]

and how would it work otherwise? without GPL include/files? magic? divine act of god?

Dean. Three ways to kill yourself, and ive been drove in one...

On 	Wed, 1 Jan 2003 14:35:10 -0200 (BRST) 	Rik van Riel <riel@conectiva.com.br> wrote:

[-- Attachment #2: Type: message/rfc822, Size: 1923 bytes --]

From: Rik van Riel <riel@conectiva.com.br>
To: Hell.Surfers@cwctv.net
Cc: linux-kernel@vger.kernel.org, "" <andre@linux-ide.org>
Subject: Re: GPL and Nvidia
Date: Wed, 1 Jan 2003 14:35:10 -0200 (BRST)
Message-ID: <Pine.LNX.4.50L.0301011432500.2429-100000@imladris.surriel.com>

On Wed, 1 Jan 2003 Hell.Surfers@cwctv.net wrote:

> lets see, In Britain we dont have "lawyers" we have solicitors, "no
> legal ground" yes I do have legal ground, having the hardware is
> irrelevent, I have the drivers, the "improperly" licensed drivers as
> they are, I dont discriminate againtst nvidia users, I am unhappy I cant
> help them with those modules, they include GPL routines

Where is your proof that nvidia includes copyrightable GPL
routines in their driver ?

Without such proof, you have no grounds to make an accusation
against nvidia.

Yes, I am at times annoyed by getting reports about "kernel bugs"
that turn out to be caused by the nvidia driver, but that doesn't
change the fact that that driver is made by nvidia and they get
to decide if and how they want to publish it.

regards,

Rik
-- 
Bravely reimplemented by the knights who say "NIH".
http://www.surriel.com/		http://guru.conectiva.com/
Current spamtrap:  <a href=mailto:"october@surriel.com">october@surriel.com</a>

             reply	other threads:[~2003-01-01 17:57 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-01 18:05 Hell.Surfers [this message]
2003-01-02 21:44 ` Bill Davidsen
  -- strict thread matches above, loose matches on Subject: below --
2003-01-01  4:37 Hell.Surfers
2003-01-01  7:17 ` Andre Hedrick
2003-01-01 16:44   ` Dan Egli
2003-01-02  0:33     ` Paul Jakma
2003-01-02 11:19       ` Andrew Walrond
2003-01-02 17:21         ` Gerhard Mack
2003-01-02 20:48           ` David Schwartz
2003-01-02 21:26             ` Andre Hedrick
2003-01-03  5:14               ` William Lee Irwin III
2003-01-03  9:17             ` Helge Hafting
2003-01-02 21:33         ` Bill Davidsen
2003-01-02 21:56           ` Andre Hedrick
2003-01-02 21:46         ` Jon Portnoy
2003-01-02 22:39           ` Andrew Walrond
2003-01-02 23:40             ` Jon Portnoy
2003-01-01 16:35 ` Rik van Riel

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=0c1c12302180113DTVMAIL8@smtp.cwctv.net \
    --to=hell.surfers@cwctv.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@conectiva.com.br \
    /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®