From: Giacomo Catenazzi <cate@debian.org>
To: nicholas@petreley.com
Cc: Dave Jones <davej@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: NVidia driver with 2.5
Date: Wed, 20 Feb 2002 09:25:59 +0100 [thread overview]
Message-ID: <3C735D97.70809@debian.org> (raw)
In-Reply-To: <fa.fhm0v6v.d02k8d@ifi.uio.no>
Nicholas Petreley wrote:
> I haven't tried the NVidia driver with the latest 2.5 kernels but I had
> no problem modifying nv.c and making the driver work with earlier diffs.
> The trick is to just fudge the code in os-interface.c to make it
> compile, and then configure XF86Config-4 not to use the NVidia agp
> driver (use the kernel agpgart instead). That way the fudged
> os-interface.c code doesn't even get called, as far as I know. It worked
> for me (at least, as I said, as of a few diffs ago).
>
> Don't even try to use the bogus os-interface.c changes by activating
> NV's agp or it will bomb, and I take no responsibility for the damage.
> In fact, I take no responsibility for the damage no matter what you do
> with this info. ;-)
>
> Having said all that, I use 2.4.18-rc2-ac1, which only requires a few
> modifications (IIRC, just the minor() stuff). But here are some diffs
> against NVidia drivers 2314 for those who are suicidal or just curious.
>
>
> --- nv.c.original Wed Jan 16 09:47:27 2002
> +++ nv.c.vma Mon Jan 28 17:05:26 2002
>
> --- os-interface.c.original Mon Feb 4 22:42:44 2002
> +++ os-interface.c.vma Thu Jan 31 23:35:59 2002
Put explicity that your code is GPL, so that we can use it
(private use we can link with all code), but nvidia cannot
use your work unless they release the source.
giacomo
next parent reply other threads:[~2002-02-20 8:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.fhm0v6v.d02k8d@ifi.uio.no>
2002-02-20 8:25 ` Giacomo Catenazzi [this message]
2002-02-20 8:34 ` NVidia driver with 2.5 Arjan van de Ven
2002-02-20 10:30 ` Dr. Keith G. Bowden
2002-02-20 17:58 Nicholas Petreley
-- 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=3C735D97.70809@debian.org \
--to=cate@debian.org \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nicholas@petreley.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