From: Milosz Tanski <mtanski@wideopenwest.com>
To: david.lang@digitalinsight.com, paul@clubi.ie,
riel@conectiva.com.br, linux-kernel@vger.kernel.org, rms@gnu.org
Subject: [OT] Re: Why is Nvidia given GPL'd code to use in closed source drivers?
Date: Thu, 2 Jan 2003 01:34:05 -0500 [thread overview]
Message-ID: <20030102013405.4f0d3417.mtanski@wideopenwest.com> (raw)
In-Reply-To: <0a5713612060213DTVMAIL4@smtp.cwctv.net>
[-- Attachment #1: Type: text/plain, Size: 588 bytes --]
There is (was) an effort for opensource 3d drivers (including nvidia
ones), infact i rember they got quake II and III working in 32bit color
mode, if i rember correctly. If you go grieff, then go visit
http://utah-glx.sourceforge.net/ and help out. Make the drivers better
then the nvidia ones (ya right!) so they will be forced to use your code
on other paltforms (and then nvidia would be forced to use it, and thus
open up their code). I'll see you in two years, when you fully complete
the drivers? Ok, bye.
P.S: I think the code there is under a BSD (BSDish, MITish licence,
...).
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-01-02 6:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-02 6:16 RE:Re: Why is Nvidia given GPL'd code to use in closed source drivers? Hell.Surfers
2003-01-02 6:34 ` Milosz Tanski [this message]
2003-01-02 13:28 ` [OT] " Paul Jakma
2003-01-02 17:37 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2003-01-02 6:41 Hell.Surfers
2003-01-02 6:54 ` Milosz Tanski
2003-01-01 3:13 Hell.Surfers
2003-01-01 3:56 ` A Guy Called Tyketto
2003-01-01 5:17 ` [OT] " J Sloan
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=20030102013405.4f0d3417.mtanski@wideopenwest.com \
--to=mtanski@wideopenwest.com \
--cc=david.lang@digitalinsight.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paul@clubi.ie \
--cc=riel@conectiva.com.br \
--cc=rms@gnu.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