Date: Tue, 6 Aug 2002 04:49:32 -0700 From: Bill Huey (Hui) <billh@gnuppy.monkey.org> To: Pierre Beyssac <beyssac@enst.fr> Cc: Frank Mayhar <frank@exit.com>, Alp ATICI <atici@cpw.math.columbia.edu>, Ed Yu <edlyu@yahoo.com>, freebsd-current@FreeBSD.ORG, "Bill Huey (Hui)" <billh@gnuppy.monkey.org> Subject: Re: About 5.0 and Nvidia drivers Message-ID: <20020806114932.GA20382@gnuppy.monkey.org> In-Reply-To: <20020806134404.A87813@bofh.enst.fr> References: <Pine.LNX.4.44.0208050157420.15528-100000@cpw.math.columbia.edu> <200208051636.g75GaamW000669@realtime.exit.com> <20020806040903.GA4316@gnuppy.monkey.org> <20020806115753.A85868@bofh.enst.fr> <20020806103047.GA19825@gnuppy.monkey.org> <20020806134404.A87813@bofh.enst.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Aug 06, 2002 at 01:44:04PM +0200, Pierre Beyssac wrote: > It doesn't have to show up as a link symbol since it's a syscall. > It can also be invoked using a i386 interrupt instruction. But I > can't find any in nvidia_drv.o, so either there are none or I'm not > looking the right way or at the right place. ... > Interesting... So the ioctl() stuff I heard about was probably > referring to code in the Linux XFree server. It was just explained to me that there's a kind of copy in/out (userspace to kernel) that's automatically done in FreeBSD and that they screwed up on their declaration of ioctl supporting functions, so yes, you're partially right about ioctl stuff being screwed. It's got to be pseudo-marshalled between both systems or something like that. What other stuff goes on where I don't know, it's not my focus at this time (relief). ;) bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020806114932.GA20382>