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 09:12:40 +1000 [thread overview]
Message-ID: <21d7e997050420161234141e23@mail.gmail.com> (raw)
In-Reply-To: <1114021024.26866.63.camel@compaq-rhel4.xsintricity.com>
> But *that's* the point people keep ignoring: the specs for programming
> the hardware, in some cases, reveals details about the hardware's
> implementation that nVidia does *not* want to release (in addition to
> suggesting their software tricks). Why is it that people *assume* that
> just the programming docs tells a person nothing about the hardware? We
> already know that knowing the registers of a card and what those
> registers do tells you implicit information about the card's design and
> also reveals implicit information about the design of software that
> works with the card. How complex the card's registers and programming
> interface is determines how much you can infer, and the more RISC like
> or simple the card is and the more that is handled in the driver, the
> more obviously the design can be inferred just from the programming
> specs.
I think the programming specs for a 3D graphics card can tell you
very little about it, the R200 specs are very good but I doubt anyone
would have a clue how to design the internals of the card just from
looking at them, and now that GPUs are getting more like CPUs in terms
of shaders and programming languages the specs are getting less and
less useful to tell what is actually going on....
The main reasons they don't like open source is from where I'm
standing, their IP lawyers and probably not being able to do sneaky
hacks in the driver because people can see them..
Dave.
>
> The aic7xxx chips are a perfect example of this exact same thing. If
> you know how to program the registers on that card, then you know almost
> everything about the hardware. It's that simple (and that's a big part
> of what makes it very fast, lots of room for driver optimizations and
> enhanced feature support).
>
> --
> Doug Ledford <dledford@redhat.com>
> http://people.redhat.com/dledford
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2005-04-20 23:12 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 [this message]
2005-04-21 11:23 ` Helge Hafting
2005-04-21 12:15 ` Doug Ledford
2005-04-21 12:54 ` Dave Airlie
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=21d7e997050420161234141e23@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