From: ebiederm@xmission.com (Eric W. Biederman)
To: "Android" <android@turbosport.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: XFree 4.0.1/NVIDIA 0.9-5/2.4.0-testX/11 woes [solved]
Date: 29 Nov 2000 07:34:05 -0700 [thread overview]
Message-ID: <m14s0qvode.fsf@frodo.biederman.org> (raw)
In-Reply-To: <E140x2k-0005Ou-00@the-village.bc.nu> <001501c05a06$2267b760$19211518@vnnys1.ca.home.com>
In-Reply-To: "Android"'s message of "Wed, 29 Nov 2000 05:13:15 -0800"
"Android" <android@turbosport.com> writes:
> > > I've never seen such thing as code without bugs. In my experience,
> > > the NVIDIA drivers are by far the most complete and solid 3D drivers
> > > under Linux.
> >
> > You are welcome to your opinion. I've got this great bridge to sell you
> too
>
> So, unless the company has fully released the details of their NVIDIA card
> to whomever wrote
> the Linux driver, then don't think for a moment that it is crash-free.
It would be very odd if NVIDIA didn't release the details to themselves.
What they haven't done is released good source code.
Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-29 15:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-29 0:02 XFree 4.0.1/NVIDIA 0.9-5/2.4.0-testX/11 woes [solved] Petter Sundlöf
2000-11-29 0:12 ` Alan Cox
2000-11-29 0:22 ` Petter Sundlöf
2000-11-29 0:39 ` Dan Hollis
2000-11-29 1:10 ` J . A . Magallon
2000-11-29 1:29 ` Dan Hollis
2000-11-29 1:48 ` J . A . Magallon
2000-11-29 2:01 ` Kiril Vidimce
2000-11-29 2:08 ` Alan Cox
2000-11-29 2:24 ` Kiril Vidimce
2000-11-29 2:32 ` Alan Cox
2000-11-29 2:48 ` Kiril Vidimce
2000-11-29 9:37 ` Yoann Vandoorselaere
2000-11-29 3:12 ` Kiril Vidimce
2000-11-29 13:13 ` Android
2000-11-29 14:34 ` Eric W. Biederman [this message]
2000-11-29 16:57 ` James Simmons
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=m14s0qvode.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=android@turbosport.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.