public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Balazic <david.balazic@uni-mb.si>
To: linux-kernel@vger.kernel.org
Subject: Re: [2.4.2-ac5] X (4.0.1) crashes
Date: Fri, 02 Mar 2001 13:30:12 +0100	[thread overview]
Message-ID: <3A9F9254.DA04EBD8@uni-mb.si> (raw)

Pavel Machek wrote :

> Hi!
> 
> > > I use XFree86 4.0.1 with nvidia-drivers 0.96. 
> > 
> > Take it up with nvidia. Obfuscated effectively binary only code isnt anyone 
> > elses problem 

It is not only "effectively binary" but "actually binary".
There are no sources, only a few line of C "glue" code.

Maybe you are confusing it with the XFree86 nv drivers from xfree86.org ?
These are the nVidia drivers from nvidia.com
 
> Is it legal, BTW? Obfuscated drivers should _not_ be linked into
> kernel, because they are not "form preferable for editing".
> 
> <GPL>
> The source code for a work means the preferred form of the work for
> making modifications to it. For an executable work, complete source
> </GPL>
> 
> So nvidia drivers *are* binary only, as far as GPL is concerned. They
> should never be linked into kernel.
> 
> [Or, someone should get kernel with nvidia drivers compiled in from
> nvidia, and then ask them for sources :-)]
>                                                                    Pavel

-- 
David Balazic
--------------
"Be excellent to each other." - Bill & Ted
- - - - - - - - - - - - - - - - - - - - - -

             reply	other threads:[~2001-03-02 12:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-02 12:30 David Balazic [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-02-27 14:08 [2.4.2-ac5] X (4.0.1) crashes Manfred H. Winter
2001-02-28  0:26 ` J Sloan
2001-02-28  0:32 ` Alan Cox
2001-02-28 23:33   ` Pavel Machek
2001-02-28  5:24 ` Erik DeBill

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=3A9F9254.DA04EBD8@uni-mb.si \
    --to=david.balazic@uni-mb.si \
    --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