From: "Dan Maas" <dmaas@dcine.com>
To: "A Guy Called Tyketto" <tyketto@wizard.com>
Cc: "lee johnson" <lee@imyourhandiman.com>, <linux-kernel@vger.kernel.org>
Subject: Re: opengl-nvidia not compiling
Date: Wed, 20 Feb 2002 06:26:17 -0500 [thread overview]
Message-ID: <00ee01c1ba01$6a1c0780$1a01a8c0@allyourbase> (raw)
In-Reply-To: <fa.gr3ai1v.1p7i906@ifi.uio.no> <fa.fklcr8v.121289b@ifi.uio.no>
> > > nv.c:1438: incompatible type for argument 4 of
> > `remap_page_range_Reb32c755'
> > > nv.c:1438: too few arguments to function `remap_page_range_Reb32c755'
> Just to add something related, but unrelated to the
> NVIDIA problem above, this is the same exact error I received when
> I compiled any kernel > 2.5.2 with ALSA 0.5.* and ALSA 0.9.*.
What happened was remap_page_range sprouted a new first argument - the vma
you are mapping into. If you know even a tiny bit of C you can fix it
yourself; just look for the nearest variable of type 'struct
vm_area_struct*', and prepend it to the other args.
Not that everything is guaranteed to work even if it compiles... NVIDIA
cards do some very unusual fiddling with memory mappings and page tables, so
VM changes are just as likely to break their driver...
Regards,
Dan
next parent reply other threads:[~2002-02-20 11:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.gr3ai1v.1p7i906@ifi.uio.no>
[not found] ` <fa.fklcr8v.121289b@ifi.uio.no>
2002-02-20 11:26 ` Dan Maas [this message]
[not found] <fa.dui02sv.125uf2m@ifi.uio.no>
[not found] ` <fa.i651ekv.c3sng3@ifi.uio.no>
2002-02-20 8:24 ` Giacomo Catenazzi
[not found] <1014218667.22795.1.camel@imyourhandiman>
2002-02-20 1:53 ` Linux 2.5.4-dj3 Dave Jones
2002-02-20 5:29 ` opengl-nvidia not compiling lee johnson
[not found] ` <20020220170454.5e700732.fc@yauza.ru>
2002-02-20 16:21 ` Nikita Gergel
2002-02-20 18:12 ` Nikita Gergel
2002-02-20 18:55 ` J Sloan
2002-02-20 6:35 ` NyQuist
2002-02-20 7:55 ` A Guy Called Tyketto
2002-02-20 15:16 ` lee johnson
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='00ee01c1ba01$6a1c0780$1a01a8c0@allyourbase' \
--to=dmaas@dcine.com \
--cc=lee@imyourhandiman.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tyketto@wizard.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®