From: <Hell.Surfers@cwctv.net>
To: andre@linux-ide.org, info@nvidia.com, linux-kernel@vger.kernel.org
Subject: RE:Re: Re: Why is Nvidia given GPL'd code to use in closed source drivers?
Date: Wed, 1 Jan 2003 18:33:35 +0000 [thread overview]
Message-ID: <0cc9b1031180113DTVMAIL9@smtp.cwctv.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 274 bytes --]
the eula is irrelevent, it should be GPL, oh and I read the drivers on a computer with an geforce card. which i now own;)
Dean. Three ways to kill yourself, and ive been drove in one...
On Tue, 31 Dec 2002 23:38:58 -0800 (PST) Andre Hedrick <andre@linux-ide.org> wrote:
[-- Attachment #2: Type: message/rfc822, Size: 2791 bytes --]
From: Andre Hedrick <andre@linux-ide.org>
To: Hell.Surfers@cwctv.net, info@nvidia.com
Cc: linux-kernel@vger.kernel.org
Subject: RE:Re: Re: Why is Nvidia given GPL'd code to use in closed source drivers?
Date: Tue, 31 Dec 2002 23:38:58 -0800 (PST)
Message-ID: <Pine.LNX.4.10.10212312322560.421-100000@master.linux-ide.org>
On Wed, 1 Jan 2003 Hell.Surfers@cwctv.net wrote:
> They are stealing by changing GPL files, and not giving the source, its
Before you call Nvidia a "THEIF", look in the mirror and read the legal
license associated with the drivers you have, and you do not have
hardware.
http://www.nvidia.com/view.asp?IO=legal_info
The attached EULA is what you forgot to read, or maybe forgot understand.
International Offices
England:
Theale Court, 11-13 High Street
Theale, Reading, Berkshire, RG7
5AH
England
Tel: +44 (118) 903 3000
Fax: +44 (118) 930 5691
> not for personal use so they are DISTRIBUTING it, and INCLUDING IT. BUT
> they dont give out their DERIVED source. I work with C everyday and when
> you put in a header file you are including it, all kernel headers are
Well recall you said it was time for you to consult your
"lawyer"/"solicitor", well lets see if I can help you do it faster.
I am tired of your rants about NVIDIA and the commerial viability of
binary library objects with public source wrappers.
With any luck you can be the person to win or loose the case and make GPL
viable or not.
Are you willing to take the risk?
Regards,
Andre Hedrick
LAD Storage Consulting Group
-
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 reply other threads:[~2003-01-01 18:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-01 18:33 Hell.Surfers [this message]
2003-01-01 20:46 ` Andre Hedrick
-- strict thread matches above, loose matches on Subject: below --
2003-01-01 5:59 RE:Re: " Hell.Surfers
2003-01-01 6:14 ` A Guy Called Tyketto
2003-01-01 5:45 Hell.Surfers
2003-01-01 5:30 Hell.Surfers
2003-01-01 7:38 ` Andre Hedrick
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=0cc9b1031180113DTVMAIL9@smtp.cwctv.net \
--to=hell.surfers@cwctv.net \
--cc=andre@linux-ide.org \
--cc=info@nvidia.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
all inboxes | Powered by JetHome®