Date: Tue, 22 Nov 2005 09:36:10 -0500
From: Jeff Garzik <jgarzik@pobox.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
       Greg KH <greg@kroah.com>, linux-kernel@vger.kernel.org
Subject: Re: [RFC] Small PCI core patch
Message-ID: <20051122143610.GD24997@havoc.gtf.org>
References: <20051121225303.GA19212@kroah.com> <20051121230136.GB19212@kroah.com> <1132616132.26560.62.camel@gaston> <1132638652.2789.4.camel@laptopd505.fenrus.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1132638652.2789.4.camel@laptopd505.fenrus.org>
User-Agent: Mutt/1.4.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 974
Lines: 23

On Tue, Nov 22, 2005 at 06:50:52AM +0100, Arjan van de Ven wrote:
> [1] Both nvidia and ati have a way out: they can do the IP side
> (translating 3D stuff into card specific commands) in userspace and just
> pass the data to the hardware via a thin driver that just drives and
> controls the hardware. Sure it may be 5% slower, but it's a lot cleaner
> IP wise. X after all is MIT (bsd like without nasty clauses) licensed
> and allows binary components.

100% agreed...  IMO this is the best way to get open source 3D stuff.

One sticking point is validation:  ensuring userspace cannot cause
invalid GPU microcode to be generated.  [I can just hear Al Viro
swearing, just thinking about creating secure compilers...]

	Jeff


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/