All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Chatman <anthony@edge.net>
To: linux-kernel@vger.kernel.org
Subject: Nvidia GeForce2 kernel driver - kernel 2.4.0 test-10
Date: Wed, 08 Nov 2000 09:52:41 +0000	[thread overview]
Message-ID: <3A092269.9020501@edge.net> (raw)
In-Reply-To: <3A08F5E9.61F424A0@ihug.co.nz>

Speaking of Nvidia, I have a Nvidia GeForce2, and had problems loading 
the NV kernel module with a patched test10 kernel (i was running test9 
before).  I took a look at the test10 patch, and noticed the following 2 
lines were taken out of  <linux_dir>/include/linux/wrapper.h:

#define mem_map_inc_count(p) atomic_inc(&(p->count))
#define mem_map_dec_count(p) atomic_dec(&(p->count))

I added those two defines back into wrapper.h and then was able to load 
the NVdriver successfully, with no problems. This doesn't appear to 
break compiliation of the test10 kernel either. I thought I'd let 
everyone know if anyone was having problems with the NV kernel driver. 
Please note, I am not a C programmer, but more of a C hacker, and this 
worked for me on my Slackware 7.1 machine. I have no idea what this may 
have broken in the kernel or whatnot. I only know that this fixed the 
problem on this particular box with the NV kernel driver, so proceed at 
your own risk ;-)





david wrote:

> hi i am writing a video kernel driver for linux lexos and have got stuck
> 
> this is how NVIDIA do their regs
> 

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-11-08 14:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-08  6:42 off topic a bit but i realy need help c++ and kernel david
2000-11-08  9:52 ` Anthony Chatman [this message]
2000-11-09  0:08   ` Nvidia GeForce2 kernel driver - kernel 2.4.0 test-10 J . A . Magallon
     [not found]     ` <20001109075436.U17457@miggy.org>
2000-11-09 10:09       ` J . A . Magallon

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=3A092269.9020501@edge.net \
    --to=anthony@edge.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.