From: Manu Abraham <manu@kromtek.com>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: Doug Ledford <dledford@redhat.com>,
Dave Airlie <airlied@gmail.com>,
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 18:43:40 +0400 [thread overview]
Message-ID: <4267BC1C.1050801@kromtek.com> (raw)
In-Reply-To: <20050421133554.GU17865@csclub.uwaterloo.ca>
Lennart Sorensen wrote:
> On Thu, Apr 21, 2005 at 08:15:02AM -0400, Doug Ledford wrote:
>
>>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
>>back to my original example of the aic7xxx cards. The alternative to
>>their simple hardware design is something like the BusLogic or QLogic
>>cards that are far more complex. Your assuming that because the ATI
>>cards are getting more complex and people are less able to discern their
>>makeup just by reading the specs that the nVidia cards are doing the
>>same, nVidia is telling you otherwise, and you are just blowing that off
>>as though you know more about their cards than they do. Reality is that
>>they *could* be telling the truth and the fact that their card is a more
>>simplistic card than ATIs may be the very reason that ATI has ponied up
>>specs and they haven't. Therefore, you can reliably discern absolutely
>>*zero* information about the nVidia cards from a reference to ATI specs.
>
>
> Certainly possible. Maybe all their real IP is in the code, although if
> that was true, letting opensource peope ahve the programing spec and
> have to do their own drivers wouldn't expose that IP. I have no idea.
>
Even without opening up the code, but with programming specs there are
many graphics driver guys out there, given the specs out it would not be
too hard to have a decent driver, without the Nvidia IP. In that case
there would be no question of IP violation.
Or maybe somebody can do a clean room implementation provided Nvidia
agrees to some NDA, and the resultant work is acceptable to Nvidia
provided that it is free of their IP.. Many hardware vendors do resort
to these to get their hardware working properly under Linux, and in some
cases, the Linux driver has proved to be a better driver than their
Windows counterparts, albeit with lesser gimmicks/features.
Manu
next prev parent reply other threads:[~2005-04-21 14:47 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
2005-04-21 13:35 ` Lennart Sorensen
2005-04-21 14:43 ` Manu Abraham [this message]
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=4267BC1C.1050801@kromtek.com \
--to=manu@kromtek.com \
--cc=airlied@gmail.com \
--cc=cfriesen@nortel.com \
--cc=dledford@redhat.com \
--cc=helge.hafting@aitel.hist.no \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
/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