All of lore.kernel.org
 help / color / mirror / Atom feed
From: mdew <mdew@orcon.net.nz>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: rmap and nvidia?
Date: 14 Dec 2002 22:36:10 +1300	[thread overview]
Message-ID: <1039858571.559.15.camel@nirvana> (raw)

is there a nvidia patch available to make it work with rmap?

nirvana:~/NVIDIA_kernel-1.0-3123# make
echo \#define NV_COMPILER \"`cc -v 2>&1 | tail -1`\" > nv_compiler.h
cc -c -Wall -Wimplicit -Wreturn-type -Wswitch -Wformat -Wchar-subscripts
-Wparentheses -Wpointer-arith -Wcast-qual -Wno-multichar  -O -MD
-D__KERNEL__ -DMODULE -D_LOOSE_KERNEL_NAMES -DNTRM -D_GNU_SOURCE
-DRM_HEAPMGR -D_LOOSE_KERNEL_NAMES -D__KERNEL__ -DMODULE 
-DNV_MAJOR_VERSION=1 -DNV_MINOR_VERSION=0 -DNV_PATCHLEVEL=3123 
-DNV_UNIX   -DNV_LINUX   -DNVCPU_X86       -I.
-I/lib/modules/2.4.20-xfs-rmap15b/build/include -Wno-cast-qual nv.c
nv.c: In function `nv_get_phys_address':
nv.c:2182: warning: implicit declaration of function `pte_offset'
nv.c:2182: invalid type argument of `unary *'
make: *** [nv.o] Error 1




             reply	other threads:[~2002-12-14  9:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-14  9:36 mdew [this message]
2002-12-14  9:38 ` rmap and nvidia? William Lee Irwin III
2002-12-14  9:46   ` mdew
2002-12-14 14:26     ` Rik van Riel
2002-12-15  1:23       ` Eyal Lebedinsky
2002-12-15  1:28         ` Philip Dodd
2002-12-15  1:40           ` Eyal Lebedinsky
2002-12-16 13:32             ` Ducrot Bruno
2002-12-16 18:42               ` Andrew McGregor
  -- strict thread matches above, loose matches on Subject: below --
2002-12-16 14:25 O.Sezer
2002-12-16 15:42 ` William Lee Irwin III
2002-12-16 22:22 O.Sezer
2002-12-16 23:17 ` Eyal Lebedinsky
2002-12-17  9:58 ` Andrew McGregor
2002-12-17 19:35 ` Andrew McGregor
2002-12-17 20:14   ` O.Sezer

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=1039858571.559.15.camel@nirvana \
    --to=mdew@orcon.net.nz \
    --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.