public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Airlie <airlied@gmail.com>
To: Doug Ledford <dledford@redhat.com>
Cc: Helge Hafting <helge.hafting@aitel.hist.no>,
	Chris Friesen <cfriesen@nortel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: nVidia stuff again
Date: Thu, 21 Apr 2005 22:54:41 +1000	[thread overview]
Message-ID: <21d7e99705042105542127cce0@mail.gmail.com> (raw)
In-Reply-To: <1114085702.26866.137.camel@compaq-rhel4.xsintricity.com>

> 
> Ha!  That's the whole damn point Dave.  Use your head.  Just because ATI
> is getting more complex with their GPU does *not* mean nVidia is.  Go

No I rely on things I read from hardware review websites and from the
GPU manufacturers to wonder what they are doing, unless putting more
transistors onto their chips is making them less complex, both ATI and
Nvidia are implementing chips primarily to implement DirectX features
(the biggest market), this means they are both heading toward the same
thing, with 3D graphics doing things on the GPU vs doing them in the
driver is going to be quite noticable you end up doing as much as
possible in the hardware,  also things like SLI are certainly more
complex not less..

ATI are making their chips less "complex" from a programming point of
view, the R300 for example has no fixed-function pipelines, for modern
apps, the shader language is translated to the GPU by the driver, for
older apps using the fixed-function pipeline the driver emulates it on
top of the programmable interface..

what this comes down to in the end is that the register interfaces are
probably converging, there are only so many ways you can send
instructions to a GPU via DMA..

> specs and they haven't.  Therefore, you can reliably discern absolutely
> *zero* information about the nVidia cards from a reference to ATI specs.

But we have some lowlevel knowledge for the Nvidia cards as well.. not
detailed but you can pick directions from the presentations they make
and marketing literature they release....
 
> "It's what you know, not what you think you know, that matters."  I
> don't know why nVidia keeps their specs secret.  All I know is what they
> tell the world.  But what I do know is that it's *possible* they could
> be telling the truth, and I have no proof otherwise, regardless of any
> suspicions.

Well when previously asked for the specs by other developers the
answer before has been IP issues, it may not be totally true now, I
think now they just don't want to support open source because they
don't believe there is any money in it...

ATI didn't release full specs for r200 because they were being nice,
the Weather Channel said we won't use your chips unless we have an
open source driver and one can only persume proceeded to purchase a
lot of chips i.e. it made monetary sense to ATI at the time.. since
then it hasn't ...

The IP reasons come from the fact that the specs they did release
didn't contain any information on how to program a lot of ATI
proprietary features..

Also it is peculiar that ATI release 2D programming specs for their
newer cards and give support to the 2D ATI driver in X, Nvidia support
the 2D NV driver in X, why not the 3D?,
Intel won't give out specs for their latest chipsets but they do
provide an open source 2D and 3D driver via Tungsten Graphics...

I'm thinking of doing up a bit of a presentation for KS on 3D drivers
and the technical issues they bring to the kernel (without even
mentioning licensing and derived works..)

Dave.

  reply	other threads:[~2005-04-21 12:54 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-12  9:34 Exploit in 2.6 kernels John M Collins
2005-04-12 12:24 ` Baruch Even
2005-04-12 15:00   ` John M Collins
2005-04-12 21:08     ` Chris Wright
2005-04-12 21:32       ` John M Collins
2005-04-13  5:28         ` Valdis.Kletnieks
2005-04-13  9:47         ` Helge Hafting
2005-04-13 12:59           ` Lennart Sorensen
2005-04-13 13:06             ` Lars Marowsky-Bree
2005-04-13 13:23               ` Lennart Sorensen
2005-04-13 14:01                 ` John M Collins
2005-04-16  2:32                   ` Adrian Bunk
2005-04-13 15:22                 ` Chris Friesen
2005-04-14 14:01                   ` Helge Hafting
2005-04-20 18:17                     ` nVidia stuff again Doug Ledford
2005-04-20 23:12                       ` Dave Airlie
2005-04-21 11:23                         ` Helge Hafting
2005-04-21 12:15                         ` Doug Ledford
2005-04-21 12:54                           ` Dave Airlie [this message]
2005-04-21 13:35                           ` Lennart Sorensen
2005-04-21 14:43                             ` Manu Abraham
2005-04-21 21:17                               ` J.A. Magallon
2005-04-22 14:44                                 ` Arjan van de Ven
2005-04-15 15:00                 ` Exploit in 2.6 kernels Alan Cox
2005-04-15 16:06                   ` Dave Airlie
2005-04-15 16:19                     ` Duncan Sands
2005-04-14 12:46             ` Helge Hafting
2005-05-05 22:00               ` Olaf Titz
2005-04-13 13:02         ` Lennart Sorensen
2005-04-13 14:26           ` Eric Rannaud
2005-04-13 14:41             ` Lennart Sorensen
2005-04-14 20:02               ` Greg Folkert
2005-04-14 22:27                 ` John M Collins
2005-05-09 18:37     ` Alessandro Salvatori

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=21d7e99705042105542127cce0@mail.gmail.com \
    --to=airlied@gmail.com \
    --cc=cfriesen@nortel.com \
    --cc=dledford@redhat.com \
    --cc=helge.hafting@aitel.hist.no \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox