From: Igor M Podlesny <for.poige+linux@gmail.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: > best asked at one of the nvidia forums, not on lkml...
Date: Tue, 05 Feb 2008 13:44:19 +0700 [thread overview]
Message-ID: <47A805C3.9050303@gmail.com> (raw)
In-Reply-To: <20080204223430.415161e9@laptopd505.fenrus.org>
On 2008-02-05 13:34, Arjan van de Ven wrote:
[...]
>> 1) To have compiled it I had to replace global_flush_tlb()
>> call with __flush_tlb_all() and still guessing was it(?) a correct
>> replacment at all :-)
>
> it is not;
I see, thanks. What would be the correct one? ;-)
>>
>> 2) When loading it emits such messages:
>>
>> nvidia: Unknown symbol change_page_attr
>> nvidia: Unknown symbol init_mm
>>
>> Can it be quick and easy solved?
>
> best asked at one of the nvidia forums, not on lkml...
> they need to adjust a few API calls, it's not hard work but they need
> to do that (their driver isn't open source)
You're right.
--
next prev parent reply other threads:[~2008-02-05 6:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <43d009740802022335y21c3f93ep4e444bef71338045@mail.gmail.com>
[not found] ` <20080202235103.20dd9768.akpm@linux-foundation.org>
2008-02-04 13:16 ` Both 2.6.24-mm1 and 2.6.24-git11 do NOT "see" any of mine LVM-2 disks Igor M Podlesny
2008-02-04 13:27 ` Andrew Morton
2008-02-05 5:32 ` > You may find that you need to update your lvm userspace tools Igor M Podlesny
2008-02-05 5:53 ` Andrew Morton
2008-02-05 12:11 ` Alasdair G Kergon
2008-02-05 6:28 ` NVIDIA's Linux x86 Display Driver fresh driver isn't compatible anymore Igor M Podlesny
2008-02-05 6:34 ` Arjan van de Ven
2008-02-05 6:44 ` Igor M Podlesny [this message]
2008-02-05 6:53 ` > best asked at one of the nvidia forums, not on lkml Zachary Amsden
2008-02-05 6:56 ` > global_flush_tlb() would be the correct one Igor M Podlesny
2008-02-05 7:22 ` > best asked at one of the nvidia forums, not on lkml Arjan van de Ven
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=47A805C3.9050303@gmail.com \
--to=for.poige+linux@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox