public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paradise <paradyse@gmail.com>
To: "Valdis.Kletnieks@vt.edu" <Valdis.Kletnieks@vt.edu>
Cc: linux-kernel@vger.kernel.org,
	Debian Users List <debian-user@lists.debian.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: 2.6.12-mm1 cannot build nvidia driver?
Date: Tue, 21 Jun 2005 03:00:12 +0800	[thread overview]
Message-ID: <f2176eb805062012003b068199@mail.gmail.com> (raw)
In-Reply-To: <200506201639.j5KGdoNO016276@turing-police.cc.vt.edu>

this is the version of !defined(HAVE_COMPAT_IOCTL) from debian
.....there is no "!defined(HAVE_COMPAT_IOCTL)" that you said..

void NV_API_CALL os_register_ioctl32_conversion(U032 cmd, U032 size)
{
#if defined(NVCPU_X86_64) && defined(CONFIG_IA32_EMULATION)
    unsigned int request = _IOWR(NV_IOCTL_MAGIC, cmd, char[size]);
    register_ioctl32_conversion(request, (void *)sys_ioctl);
#endif /* NVCPU_X86_64 */
}

void NV_API_CALL os_unregister_ioctl32_conversion(U032 cmd, U032 size)
{
#if defined(NVCPU_X86_64) && defined(CONFIG_IA32_EMULATION)
    unsigned int request = _IOWR(NV_IOCTL_MAGIC, cmd, char[size]);
    unregister_ioctl32_conversion(request);
#endif /* NVCPU_X86_64 */
}


On 6/21/05, Valdis.Kletnieks@vt.edu <Valdis.Kletnieks@vt.edu> wrote:
> On Mon, 20 Jun 2005 20:20:06 +0800, Paradise said:
> > seems un/register_ioctl32_conversion is removed from 2.6.12-mm1..
> > any patch for nvidia kernel driver?
> 
> No patch, but some hints - I suspect the problem is a local build config error...
> 
> 1) The exact patch causing your problem in -mm1 is:
> remove-register_ioctl32_conversion-and-unregister_ioctl32_conversion.patch
> 
> Building with this one patch -R'ed out should help, but it's the wrong thing
> to do, as it only papers over the real problem, which is:
> 
> 2) Your failing code is in os-interface.c:
> 
> void NV_API_CALL os_unregister_ioctl32_conversion(U032 cmd, U032 size)
> {
> #if defined(NVCPU_X86_64) && defined(CONFIG_IA32_EMULATION) && !defined(HAVE_COMPAT_IOCTL)
>     unsigned int request = _IOWR(NV_IOCTL_MAGIC, cmd, char[size]);
>     unregister_ioctl32_conversion(request);
> #endif
> }
> 
> Might want to figure out why HAVE_COMPAT_IOCTL isn't defined - there's at least
> 3 other places where it matters (in nv.c).  It's #defined in the include/linux/fs.h
> header in 2.6.12-rc6-mm1, so you probably want to figure out why your build isn't
> picking up on it.  Are your #include directories screwed up?
> 
> Sorry I can't provide more help, this looks like an X86-64 only issue.  If this
> isnt enough, take it up on the NVidia forums:
> 
> http://www.nvnews.net/vbulletin/forumdisplay.php?s=&forumid=14
> 
> 
> 
> 
> 


-- 
Regards,
Paradise

  reply	other threads:[~2005-06-20 19:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-20 11:55 2.6.12-mm1 cannot build nvidia driver? Paradise
2005-06-20 12:20 ` Paradise
2005-06-20 16:39   ` Valdis.Kletnieks
2005-06-20 19:00     ` Paradise [this message]
2005-06-20 19:00       ` Paradise
2005-06-20 19:18         ` Paradise
2005-06-20 19:41           ` Valdis.Kletnieks
2005-06-20 19:38         ` Valdis.Kletnieks

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=f2176eb805062012003b068199@mail.gmail.com \
    --to=paradyse@gmail.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=akpm@osdl.org \
    --cc=debian-user@lists.debian.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