Date: Wed, 17 Dec 1997 09:24:41 -0800 From: Amancio Hasty <hasty@rah.star-gate.com> To: gjp@erols.net (Gary Palmer) Cc: cvs-all@freebsd.org, cvs-sys@freebsd.org Subject: Re: cvs commit: src/sys/i386/linux linux.h linux_ioctl.c Message-ID: <199712171724.JAA01982@rah.star-gate.com> In-Reply-To: Your message of "Wed, 17 Dec 1997 09:46:12 EST." <199712171446.JAA12759@mutara.noc.erols.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> In article <199712151301.XAA00302@word.smith.net.au>, > mike@smith.net.au (Mike Smith) writes: > >> How close does this bring us to being able to run SVGAlib binaries > >> in general? Thanks also to Amancio for doign this! > > > > Amancio has a modified SVGAlib which when built linux-mode allows Linux > > SVGALlib-using-binaries to run on FreeBSD. It's not unreasonable to > > suggest that these changes might make it into the "mainstream" SVGAlib > > at some stage; until then we can just include it as part of the > > linux_lib port I guess. > > There are 3 remaining problems: > > - Linux's ioperm() isn't implimented, but I can fix that We don't need ioperm. > - normal svgalib checks the major number of the device to see if it is > a known console, there is a hack in linux_newfstat that can fix that. It also checks the owner . The best thing to do is to read svgalib or or one of the versions and examine how it handles virtual terminals is not that much code. > - quake has a rather unusual ``bug'' in dealing with the console file > descriptors. It opens /dev/console twice (from memory). It then > proceeds to set one non-blocking, and then promply reads from the > *other*, expecting it to be non-blocking *also*. This, of course, > *fails* (surprise surprise). An oddity to note is that this works > on NetBSD as Linux expects. I have not noticed any problems with quake, quake II or quake server. > I've gotten SVGALib Quake to run in the past by a *gross* hack, which > re-mapped the FD that the ioctl was done on so that it did the > non-blocking options on the one it actually reads from. This is, > of course, not the Correct Solution (TM). I am not sure what is > Amancio
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199712171724.JAA01982>