mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Derek Foreman <manmower@signalmarketing.com>
To: Tomas Szepe <szepe@pinerecords.com>
Cc: DervishD <raul@pleyades.net>, Eugene <spamacct11@yahoo.com>,
	linux-kernel@vger.kernel.org,
	"ynezz @ hysteria. sk" <ynezz@hysteria.sk>
Subject: Re: best AMD motherboard for Linux
Date: Tue, 30 Dec 2003 18:46:44 -0600 (CST)	[thread overview]
Message-ID: <Pine.LNX.4.58.0312301354130.765@uberdeity> (raw)
In-Reply-To: <20031230194203.GA8062@louise.pinerecords.com>

On Tue, 30 Dec 2003, Tomas Szepe wrote:

> On Dec-30 2003, Tue, 12:32 -0600
> Derek Foreman <manmower@signalmarketing.com> wrote:
>
> > > > > planning to get GeForce FX graphics card, if it makes a difference.
> > > >
> > > >     Ask here before if you are planning to change your video card.
> > >
> > > nVidia translates to "trouble" around here.  Selected Radeon cards,
> > > on the other hand, work perfectly with opensource drivers and should
> > > perform comparably.
> >
> > I'm not sure how you're defining "comparably".  If you mean they get
> > similar numbers from glxgears, that's possible.  But the feature sets are
> > not at all comparable.  Nvidia's linux driver actually exposes the
> > features available on modern graphics hardware.
> >
> > If you're going to advise against the use of their products in a public
> > forum, I suggest you be a lot more specific.
>
> The person asking for advice was very articulate in what their primary
> concerns in choosing hardware were, and my suggestion was made with those
> in mind.

His primary requirement was that it (the motherboard) work well with
linux.  He stated that he was capable of installing drivers if he had to,
but it would be even better if it wasn't required.

Open source drivers, or whether nvidia fits your idea of a "linux
supporting company" were not on the stated list of requirements.

In fact, the message wasn't even asking for an opinion on the graphics
card.

>            Yes, I'm convinced that a binary only driver is not an adequate
> solution in "supporting linux."

Paying people to write the driver, write documentation for the driver, and
provide technical support for the driver does not meet your requirements
for "supporting linux"...  Your requirements seem steep indeed.

There are a lot of drivers in the linux source tree itself that are
just as closed to you and I as the nvidia ones.  Lots of companies only
give out their documentation under NDA to "appropriate open source
developers" (I thought one of the great things about opensource was that
everyone was an "appropriate developer").  So while we can look at the
source code, we don't have enough information about it to provide adequate
peer review or to fix bugs in it ourselves.

We still have to contact whoever has the complete documentation, and we
still have to wait for them to make a fix available.

> And by the way, you are not being specific in naming the "features
> available on modern graphics hardware," either.

Vertex programs, fragment programs, vertex buffer objects, to name a few
things.  These are also available in the closed source ATI drivers.

Run glxinfo and look at the gl version strings and the supported
extensions.  I'll send you the output of mine off-list if you'd like to do
a comparison.

If you really do have specific complaints about nvidia's drivers, it
would be polite to email them first - they do reply to their linux-bugs
email address.

Just claiming "nvidia translates into trouble" is really nothing more
than FUD.

  reply	other threads:[~2003-12-31  0:46 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-28 16:55 Eugene
2003-12-28 17:20 ` ynezz
2003-12-28 17:48   ` DervishD
2003-12-28 21:10     ` Patrick Plattes
2003-12-29 20:28       ` Shawn
2003-12-29 16:56     ` Tomas Szepe
2003-12-30 18:32       ` Derek Foreman
2003-12-30 18:35         ` Joel Jaeggli
2003-12-30 19:42         ` Tomas Szepe
2003-12-31  0:46           ` Derek Foreman [this message]
2003-12-31  9:39             ` Tomas Szepe
2004-01-01  6:15               ` Derek Foreman
2004-01-01 17:04                 ` Lionel Bouton
2004-01-01 19:37                   ` Diego Calleja
2004-01-01 21:43                   ` Martin Schlemmer
2004-01-01 21:44                   ` Derek Foreman
2004-01-02  0:15                     ` Lionel Bouton
2003-12-29 20:32   ` Shawn
     [not found] <17Mr0-3MN-9@gated-at.bofh.it>
     [not found] ` <17MTX-4tr-5@gated-at.bofh.it>
     [not found]   ` <17NmT-53G-1@gated-at.bofh.it>
     [not found]     ` <1894e-34n-11@gated-at.bofh.it>
     [not found]       ` <18wWI-5xF-5@gated-at.bofh.it>
     [not found]         ` <18y2M-7Zy-15@gated-at.bofh.it>
     [not found]           ` <18CSr-880-1@gated-at.bofh.it>
     [not found]             ` <18L9o-5xr-5@gated-at.bofh.it>
     [not found]               ` <194lF-8q6-3@gated-at.bofh.it>
     [not found]                 ` <19euJ-59K-7@gated-at.bofh.it>
     [not found]                   ` <19gZu-8vz-1@gated-at.bofh.it>
2004-01-02  6:51                     ` Yaroslav Klyukin

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=Pine.LNX.4.58.0312301354130.765@uberdeity \
    --to=manmower@signalmarketing.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=raul@pleyades.net \
    --cc=spamacct11@yahoo.com \
    --cc=szepe@pinerecords.com \
    --cc=ynezz@hysteria.sk \
    /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®