public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Helge Hafting <helge.hafting@aitel.hist.no>
To: Chris Friesen <cfriesen@nortel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Exploit in 2.6 kernels
Date: Thu, 14 Apr 2005 16:01:31 +0200	[thread overview]
Message-ID: <425E77BB.5010902@aitel.hist.no> (raw)
In-Reply-To: <425D3924.1070809@nortel.com>

Chris Friesen wrote:

> Lennart Sorensen wrote:
>
>> Graphics card companies don't realize they are hardware companies not
>> software companies and that it is hardware they make their money from?
>> Oh and they have too many lawyers?
>
>
> This has been mentioned before, but I'll say it again.
>
> Nvidia has intellectual property from *other companies* in their 
> drivers/hardware.
>
> They are *not allowed* to make the specs public due to their 
> agreements with those other companies.
>
> It's that simple.

That argument isn't very good.  It'd be quite bad if all the "intellectual
property" was Nvidia's own.  Then we'd complain that they could
simply release the specs instead of keeping them secret for no
good reason.

Of course my argument applies equally well when there is several
companies invloved.  Why can't they give us specs instead of keeping
them secret for no good reason???  The fact that nvidia isn't free
to do this _on their own_ doesn't change anything. The companies can
act together and release necessary information for the drm people.

Nvidia can, for example, tell their "ip"-partners that the specs is wanted
ant try to get a licence for handing out what's needed.  Or the other way
around - the "other companies" may want more sales of their stuff
and tell nvidia they want specs released to open-source developers. Or
simply release information about "their own" part of the card.

And for those that want to keep some things secret - they may not have 
to open
up all information - only enough to get a driver made.  For example:
"write this sequence of magic bytes to these registers in order to set
up some pipeline."  It tells how to get things done, but not every detail.
A driver based on such information might not be the best, but it
could possible be enough - and certainly better than nothing.

Helge Hafting







  reply	other threads:[~2005-04-14 13:57 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 [this message]
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
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=425E77BB.5010902@aitel.hist.no \
    --to=helge.hafting@aitel.hist.no \
    --cc=cfriesen@nortel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox