mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Milosz Tanski <mtanski@wideopenwest.com>
Cc: david.lang@digitalinsight.com, paul@clubi.ie,
	riel@conectiva.com.br,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	rms@gnu.org
Subject: Re: [OT] Re: Why is Nvidia given GPL'd code to use in closed source drivers?
Date: 02 Jan 2003 17:37:39 +0000	[thread overview]
Message-ID: <1041529059.24829.13.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <20030102013405.4f0d3417.mtanski@wideopenwest.com>

On Thu, 2003-01-02 at 06:34, Milosz Tanski wrote:
> 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,

Utah-GLX supports the older Nvidia cards, and works in XFree86 4.2 at
least - although since its based on an older Mesa not all stuff works
well with it.

Alan


  parent reply	other threads:[~2003-01-02 16:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-02  6:16 Hell.Surfers
2003-01-02  6:34 ` [OT] " Milosz Tanski
2003-01-02 13:28   ` Paul Jakma
2003-01-02 17:37   ` Alan Cox [this message]
  -- 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=1041529059.24829.13.camel@irongate.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=david.lang@digitalinsight.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtanski@wideopenwest.com \
    --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

all inboxes | Powered by JetHome®