Theo,

Though doug didn't say so, I think the equivalent code in freeBSD is 

if ((fd = open("/dev/io",O_RDWR,0)) == -1) {
        ERROR...
}

you are asking for permission to do direct IO to IO ports from userland.

man 4 io

julian
On Thu, 23 Dec 1999, Doug Rabson wrote:

> On Wed, 22 Dec 1999, Theo van Klaveren wrote:
> 
> > Hello,
> > 
> > I am in the process of porting the GLIDE library to FreeBSD/i386
> > which is making good progress so far. My worst enemy has been the
> > build system itself and the huge amount if `#ifdef __linux__' in
> > the code. 
> > 
> > I am doing this in the light of the Quake source code
> > release, which I'd like to play natively with 3dFX hardware... :)
> > (for the interested: I have already gotten the server and X11 
> > client to build, but I haven't tested them yet.)
> > 
> > My question is about this particular piece of code in
> > swlibs/fxpci/pcilib/fxlinux.c, around line 70:
> > 
> >     if (iopl(3)<0) {
> >       pciErrorCode = PCI_ERR_NO_IO_PERM;
> >       return FXFALSE;
> >     }
> > 
> > Does anyone know what 'iopl(3)' is supposed to do,
> > and what it's equivalent on FreeBSD is (if at
> > all available)? 
> > 
> > The code this is in is about opening the /dev/3dfx device
> > (which is not available for FreeBSD so it'll fail anyway),
> > so I _could_ just remove it, but I'm not so certain...
> > 
> > Also, IANAL, so could anyone tell me if the 3DFX license
> > permits me to publish my patches under a BSD-style license?
> 
> I already ported the voodoo2 sources for Glide 2.x and Glide 3.x. You can
> find patches at:
> 
>       http://www.freebsd.org/~dfr/Glide-V2-2.53.diff
>       http://www.freebsd.org/~dfr/Glide-V2-3.01.diff
> 
> --
> Doug Rabson                           Mail:  [EMAIL PROTECTED]
> Nonlinear Systems Ltd.                        Phone: +44 181 442 9037
> 
> 
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message
> 



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Reply via email to