From: Jason McMullan <jmcmullan@linuxcare.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Jason McMullan <jmcmullan@linuxcare.com>, linux-kernel@vger.kernel.org
Subject: Re: Why is Device3Dfx driver (voodoo1/2) not in the kernel?
Date: Thu, 27 Sep 2001 11:57:10 -0400 [thread overview]
Message-ID: <20010927115710.A23248@jmcmullan.evillabs.net> (raw)
In-Reply-To: <9ou9u4$ee6$1@localhost.localdomain> <E15mZqU-0003kx-00@the-village.bc.nu>
In-Reply-To: <E15mZqU-0003kx-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Thu, Sep 27, 2001 at 01:00:50PM +0100
On Thu, Sep 27, 2001 at 01:00:50PM +0100, Alan Cox wrote:
> There are actually distinct similarities between some DRI drivers and what
> Linus suggested the KGI people needed to be doing. Certain hardware isnt
> totally user safe (not on the extremes of the voodoo1 here) and the drivers
> do small amounts of work to stop abuse. All mode changes, rendering
> primitives and the like are however in userspace.
Rendering - definitely agree. Userspace.
Mode changing - Now there I can get into an argument. I
still (after all these years) feel that the Kernel is the best
place to put video mode control. That way 'killall -9 X' isn't
nearly as nasty... The kernel could at least get you back to
a text console.
And now that XFree86 4 has a vm86 system to 'run the
Video BIOS' for certain cards, it shouldn't be to hard to
emulate the old OS/2 system - in a vm86 session, use the BIOS
to switch to all the supported modes, and record (via vm86
io traps) everything the BIOS does. Then, in the driver,
just 'play back' the scripts... Worked beatifully for OS/2
back in the day for 2D framebuffers...
Anyway, I'll just let sleeping dogs lie and leave it
at that.
> I firmly believe you can do X11 with 3D in windows, including partial
> occlusion of 3d windows on a 3dfx voodoo1 or voodoo2 card.
As do I, but I lack three things: The time, The Specs, and
The Hardware. :(
--
Jason McMullan, Senior Linux Consultant
Linuxcare, Inc. 412.432.6457 tel, 412.656.3519 cell
jmcmullan@linuxcare.com, http://www.linuxcare.com/
Linuxcare. Putting open source to work.
next prev parent reply other threads:[~2001-09-27 15:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-19 12:44 Steven Griffiths
2001-09-19 19:24 ` Alan Cox
2001-09-27 4:28 ` Jason McMullan
2001-09-27 12:00 ` Alan Cox
2001-09-27 15:57 ` Jason McMullan [this message]
2001-09-27 17:56 ` James Simmons
2001-09-27 22:49 ` Alan Cox
2001-09-27 23:26 ` James Simmons
2001-09-27 17:36 ` James Simmons
2001-09-28 0:24 Grover, Andrew
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=20010927115710.A23248@jmcmullan.evillabs.net \
--to=jmcmullan@linuxcare.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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
all inboxes | Powered by JetHome®