From: Stuart Young <sgy@amc.com.au>
To: <linux-kernel@vger.kernel.org>
Cc: Erik Elmore <lk@bigsexymo.com>
Subject: Re: NVIDIA kernel module
Date: Thu, 06 Dec 2001 10:46:20 +1100 [thread overview]
Message-ID: <5.1.0.14.0.20011206104048.0213de70@mail.amc.localnet> (raw)
In-Reply-To: <Pine.LNX.4.33.0112051719260.13083-100000@erik.bigsexymo.co m>
At 05:22 PM 5/12/01 -0600, Erik Elmore wrote:
>Have I lost my mind?
>
>I've always thought that NVIDIA's linux kernel support was incredibly
>closed source, but I swear I just saw a download link for the kernel
>module sources at http://www.nvidia.com/view.asp?PAGE=linux
>
>was I mistaken or is this something new?
The "sources" you see there are the following:
- A Makefile
- The Nvidia binary module
- Some source code that wraps around the binary module and interfaces to
the kernel functions, agp, etc.
This gives some flexibility when it comes to using it with different
kernels, The "kernel layer" compiles against and uses information from the
kernel at /usr/src/linux (or the one you specify through parameters). This
also means they don't have to release a new binary for every kernel release
(can you imagine how horrible that would be?), or track a huge number of
kernel changes.
Most of the guts are still a closed binary module (for x86 only) that
hasn't had any peer review.
Stuart Young - sgy@amc.com.au
(aka Cefiar) - cefiar1@optushome.com.au
[All opinions expressed in the above message are my]
[own and not necessarily the views of my employer..]
next parent reply other threads:[~2001-12-05 23:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.33.0112051719260.13083-100000@erik.bigsexymo.co m>
2001-12-05 23:46 ` Stuart Young [this message]
2001-12-05 23:22 Erik Elmore
2001-12-05 23:29 ` Jeffrey H. Ingber
2001-12-06 2:27 ` Erik Elmore
2001-12-05 23:38 ` Miles Lane
2001-12-05 23:39 ` Chris Wedgwood
2001-12-06 15:10 ` Stefan Smietanowski
2001-12-06 15:19 ` Michael Kummer
2001-12-06 23:57 ` Stuart Young
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=5.1.0.14.0.20011206104048.0213de70@mail.amc.localnet \
--to=sgy@amc.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=lk@bigsexymo.com \
/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®