Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932506AbWLNLGh (ORCPT ); Thu, 14 Dec 2006 06:06:37 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932513AbWLNLGh (ORCPT ); Thu, 14 Dec 2006 06:06:37 -0500 Received: from outpipe-village-512-1.bc.nu ([81.2.110.250]:51597 "EHLO lxorguk.ukuu.org.uk" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S932506AbWLNLGh (ORCPT ); Thu, 14 Dec 2006 06:06:37 -0500 Date: Thu, 14 Dec 2006 11:14:39 +0000 From: Alan To: "Hua Zhong" Cc: "'Martin J. Bligh'" , "'Linus Torvalds'" , "'Greg KH'" , "'Jonathan Corbet'" , "'Andrew Morton'" , "'Michael K. Edwards'" , Subject: Re: GPL only modules [was Re: [GIT PATCH] more Driver core patches for 2.6.19] Message-ID: <20061214111439.11bed930@localhost.localdomain> In-Reply-To: <003801c71f45$45d722c0$6721100a@nuitysystems.com> References: <4580E37F.8000305@mbligh.org> <003801c71f45$45d722c0$6721100a@nuitysystems.com> X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1277 Lines: 31 On Wed, 13 Dec 2006 22:01:15 -0800 "Hua Zhong" wrote: > > I think allowing binary hardware drivers in userspace hurts > > our ability to leverage companies to release hardware specs. > > If filesystems can be in user space, why can't drivers be in user space? On what *technical* ground? The FUSE file system interface provides a clean disciplined interface which allows an fs to live in user space. The uio layer (if its ever fixed and cleaned up) provides some basic hooks that allow a user space program to arbitarily control hardware and make a nasty undebuggable mess. uio also doesn't handle hotplug, pci and other "small" matters. Now if you wanted to make uio useful at minimum you would need - PCI support - The ability to mark sets of I/O addresses for the card as "unmappable", "read only", "read-write", "any read/root write", "root read/write" - A proper IRQ handler - A DMA interface - The ability to describe sharing rules Which actually is a description of the core of the DRM layer. - 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/