From: Nicholas Petreley <nicholas@petreley.com>
To: linux-kernel@vger.kernel.org
Subject: Re: NVidia driver with 2.5
Date: Wed, 20 Feb 2002 09:58:41 -0800 [thread overview]
Message-ID: <3C73E3D1.6070206@petreley.com> (raw)
>
> Since the nvidia driver is not gpl in the first place, the patch
> is most likely in violation of nvidia's license already. Maybe they
> let it go but... if they were mean and evil they could sue the guy
> who posted the patch in the first place.
> -
ROFL! Such paranoia!
I doubt NVidia would sue. It's not just a case of being nice or
mean, good or evil. They have to feel as if the company was damaged
in some way by the patch, or make a case that there was the potential
for damage. Then they'd have to see if I have enough money to make it
worth their while to sue. If I didn't have enough money (and I don't),
they'd evaluate whether I did anything that threatened their IP (such
as reverse engineering their binary to figure out how to come up with
the patch). Clearly that's not what this patch is all about.
The only thing left is a "test case" to discourage anyone from messing
with their source code. Somehow I just don't get the feeling that
they're going to pursue a test case in order to discourage people
from helping expand the number of potential customers for their
hardware. ;-)
If I'm wrong, then bring on the lawyers! That would give me LOTs of
good column material.
-Nicholas Petreley
next reply other threads:[~2002-02-20 17:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-20 17:58 Nicholas Petreley [this message]
[not found] <fa.fhm0v6v.d02k8d@ifi.uio.no>
2002-02-20 8:25 ` NVidia driver with 2.5 Giacomo Catenazzi
2002-02-20 8:34 ` Arjan van de Ven
2002-02-20 10:30 ` Dr. Keith G. Bowden
-- strict thread matches above, loose matches on Subject: below --
2002-02-19 21:51 Nicholas Petreley
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=3C73E3D1.6070206@petreley.com \
--to=nicholas@petreley.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