From: "Boyd Stephen Smith Jr." <bss03@volumehost.net>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] kernel recompile?
Date: Tue, 31 Oct 2006 11:14:52 -0500 [thread overview]
Message-ID: <200610311014.57356.bss03@volumehost.net> (raw)
In-Reply-To: <454772F9.5030807@ilievnet.com>
[-- Attachment #1: Type: text/plain, Size: 1167 bytes --]
On Tuesday 31 October 2006 09:59, Daniel Iliev <danny@ilievnet.com> wrote
about 'Re: [gentoo-amd64] kernel recompile?':
> I think gcc version should not have impact on X because NVidia's drivers
> are binary, closed source - they don't care about the gcc used to
> compile the kernel or the X server. Actually I think the emerge only
> installs those drivers and checks for common configuration errors.
No, there's no way to make a pure binary driver that works on all systems,
because symbols in the kernel will be at different locations depending on
options it was compiled with.
Instead, nvidia distributes a mostly binary driver, with a small
source "shim" that is compiled against the kernel and passes messages
between the fixed binary interface of the binary part and the non-fixed
interface of the kernel.
The compiler you build the module with does have to match the compiler you
built the kernel with.
--
"If there's one thing we've established over the years,
it's that the vast majority of our users don't have the slightest
clue what's best for them in terms of package stability."
-- Gentoo Developer Ciaran McCreesh
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-10-31 16:18 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-31 14:10 [gentoo-amd64] kernel recompile? Sean
2006-10-31 14:16 ` Piotr Pruszczak
2006-10-31 14:25 ` Daniel Iliev
2006-10-31 14:37 ` Piotr Pruszczak
2006-10-31 15:59 ` Daniel Iliev
2006-10-31 16:14 ` Boyd Stephen Smith Jr. [this message]
2006-11-02 9:48 ` Michel Merinoff
2006-11-02 10:36 ` Neil Bothwick
2006-10-31 16:19 ` Pawel Kraszewski
2006-10-31 16:49 ` Daniel Iliev
2006-10-31 17:04 ` Sean
2006-10-31 17:18 ` Mathieu Seigneurin
2006-10-31 17:31 ` Daniel Iliev
2006-10-31 18:14 ` Sean
2006-10-31 18:21 ` Daniel Iliev
2006-10-31 18:39 ` Daniel Iliev
2006-10-31 18:48 ` Sean
2006-10-31 19:11 ` Daniel Iliev
2006-10-31 19:38 ` sean
2006-10-31 21:57 ` Daniel Iliev
2006-11-01 19:24 ` sean
2006-11-01 20:39 ` Daniel Iliev
2006-11-01 9:05 ` Pawel Kraszewski
2006-11-01 12:47 ` Daniel Iliev
2006-11-01 14:32 ` Pawel Kraszewski
2006-11-01 16:55 ` Florian D.
2006-11-01 16:37 ` Jesús Guerrero
2006-11-01 19:14 ` Pawel Kraszewski
2006-11-01 17:06 ` [gentoo-amd64] [OT] " Daniel Iliev
2006-11-01 19:01 ` [gentoo-amd64] [OOT] Apologies Pawel Kraszewski
2006-11-01 20:02 ` [gentoo-amd64] [OOT] [SOLVED] Apologies Daniel Iliev
2006-10-31 14:22 ` [gentoo-amd64] kernel recompile? Sebastian Redl
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=200610311014.57356.bss03@volumehost.net \
--to=bss03@volumehost.net \
--cc=gentoo-amd64@lists.gentoo.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