Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 5 Jan 2002 02:04:20 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 5 Jan 2002 02:04:00 -0500 Received: from neon-gw-l3.transmeta.com ([63.209.4.196]:7174 "EHLO neon-gw.transmeta.com") by vger.kernel.org with ESMTP id ; Sat, 5 Jan 2002 02:03:56 -0500 To: linux-kernel@vger.kernel.org From: "H. Peter Anvin" Subject: Re: ISA slot detection on PCI systems? Date: 4 Jan 2002 23:03:24 -0800 Organization: Transmeta Corporation, Santa Clara CA Message-ID: In-Reply-To: <20020103144904.A644@zapff.research.canon.com.au> <20020103133912.B17280@suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Disclaimer: Not speaking for Transmeta in any way, shape, or form. Copyright: Copyright 2002 H. Peter Anvin - All Rights Reserved Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Followup to: <20020103133912.B17280@suse.cz> By author: Vojtech Pavlik In newsgroup: linux.dev.kernel > > It's still not very nice for userspace apps to touch hardware directly, > even if it's just BIOS memory ... > Red herring. It's not very nice for *applications* to not indirect through a driver, but if that driver is in userspace or kernel space is irrelevant. Incidentally, "applications" here include a lot of the parsers that produce /proc output. /proc/pci is occationally handy, but it is also an example on why you shouldn't do data reduction in kernel space unless you can avoid it. Now /proc/bus/pci is available and contains all the data, however. -hpa -- at work, in private! "Unix gives you enough rope to shoot yourself in the foot." http://www.zytor.com/~hpa/puzzle.txt - 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/