Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 5 Jan 2002 12:15:13 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 5 Jan 2002 12:14:53 -0500 Received: from ns.suse.de ([213.95.15.193]:44549 "HELO Cantor.suse.de") by vger.kernel.org with SMTP id ; Sat, 5 Jan 2002 12:14:43 -0500 Date: Sat, 5 Jan 2002 18:14:42 +0100 (CET) From: Dave Jones To: Paul Jakma Cc: , Subject: Re: Hardware Inventory [was: Re: ISA slot detection on PCI systems?] In-Reply-To: Message-ID: 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 On Sat, 5 Jan 2002, Paul Jakma wrote: > how does devicefs differ from devfs? eg, on some of my systems i mount > devfs on /devfs and an ls -l of it shows all the devices that > currently have drivers that registered them. different goals. One of the reasons this has come about is for power management, we need a tree like structure so that we for eg, power down a network card before powering down the pci bridge it sits on. (The idea being to power down from the leaves, and work your way back up to the root of the tree) devicefs is just a means of exporting this to userspace, be that for usage with the userspace acpi tools, or for hinv like programs. As I mentioned earlier, ACPI enumerates pretty much everything in the system, even if theres no driver for it. If there is a driver for it, it can register things like "I support these power saving states" with driverfs for additional functionality. It would be nice at some point to get some of the other (pre-ACPI) busses registering stuff there too, for completeness. -- | Dave Jones. http://www.codemonkey.org.uk | SuSE Labs - 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/