Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 3 Sep 2002 19:22:30 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 3 Sep 2002 19:22:29 -0400 Received: from dsl-213-023-043-116.arcor-ip.net ([213.23.43.116]:34456 "EHLO starship") by vger.kernel.org with ESMTP id ; Tue, 3 Sep 2002 19:22:28 -0400 Content-Type: text/plain; charset=US-ASCII From: Daniel Phillips To: Matt Domsch , linux-kernel@vger.kernel.org Subject: Re: [RFC][PATCH] x86 BIOS Enhanced Disk Device (EDD) polling Date: Wed, 4 Sep 2002 01:29:37 +0200 X-Mailer: KMail [version 1.3.2] References: In-Reply-To: MIME-Version: 1.0 Content-Transfer-Encoding: 7BIT Message-Id: Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1105 Lines: 29 On Wednesday 04 September 2002 00:05, Matt Domsch wrote: > > [...] > > EDD works by providing the bus (PCI, PCI-X, ISA, InfiniBand, PCI > Express, or HyperTransport) location (e.g. PCI 02:01.0) and interface > (ATAPI, ATA, SCSI, USB, 1394, FibreChannel, I2O, RAID, SATA) location > (e.g. SCSI ID 5 LUN 0) information for each BIOS int13 device. The > patch below creates CONFIG_EDD, that when defined, makes the calls to > retrieve and store this information. It then exports it (yes, another > /proc, glad to change it to driverfs or whatever else when that makes > sense) in /proc/edd/{bios-device-number}, as such: > > [...] > > > Feedback appreciated. How about providing an example of how you'd export the root via driverfs, with a view to educating those of us who are still don't have much of a clue how driverfs fits in with big picture? -- Daniel - 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/