From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S273729AbRI0RhD>; Thu, 27 Sep 2001 13:37:03 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S273734AbRI0Rgx>; Thu, 27 Sep 2001 13:36:53 -0400
Received: from www.transvirtual.com ([206.14.214.140]:53007 "EHLO
	www.transvirtual.com") by vger.kernel.org with ESMTP
	id <S273729AbRI0Rgl>; Thu, 27 Sep 2001 13:36:41 -0400
Date: Thu, 27 Sep 2001 10:36:53 -0700 (PDT)
From: James Simmons <jsimmons@transvirtual.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?
In-Reply-To: <E15mZqU-0003kx-00@the-village.bc.nu>
Message-ID: <Pine.LNX.4.10.10109271035400.20787-100000@transvirtual.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org


> 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. 

The voodoo1 is really dangerous. I have locked my system many times.

> I firmly believe you can do X11 with 3D in windows, including partial 
> occlusion of 3d windows on a 3dfx voodoo1 or voodoo2 card. 

SGI has been doing it for a long long time.