[lkml]   [2001]   [Sep]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Why is Device3Dfx driver (voodoo1/2) not in the kernel?
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,
Linuxcare. Putting open source to work.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:03    [W:0.056 / U:0.204 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site