Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750968AbWLMVIM (ORCPT ); Wed, 13 Dec 2006 16:08:12 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750986AbWLMVIL (ORCPT ); Wed, 13 Dec 2006 16:08:11 -0500 Received: from smtp.osdl.org ([65.172.181.25]:41981 "EHLO smtp.osdl.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750968AbWLMVIK (ORCPT ); Wed, 13 Dec 2006 16:08:10 -0500 Date: Wed, 13 Dec 2006 13:08:03 -0800 (PST) From: Linus Torvalds To: Greg KH cc: Andrew Morton , linux-kernel@vger.kernel.org, tglx@linutronix.de Subject: Re: [GIT PATCH] more Driver core patches for 2.6.19 In-Reply-To: Message-ID: References: <20061213195226.GA6736@kroah.com> <20061213203113.GA9026@suse.de> 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 Content-Length: 933 Lines: 21 On Wed, 13 Dec 2006, Linus Torvalds wrote: > > Btw: there's one driver we _know_ we want to support in user space, and > that's the X kind of direct-rendering thing. So if you can show that this > driver infrastructure actually makes sense as a replacement for the DRI > layer, then _that_ would be a hell of a convincing argument. Btw, the other side of this argument is that if a user-space driver infrastructure can _not_ help the DRI kind of situation, then it's largely by definition not interesting. Merging something like that would just mean that we end up with multiple _different_ user-space helper infrastructure shells, which sounds distinctly unpalatable. Linus - 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/