Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 23 Apr 2001 19:05:36 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 23 Apr 2001 19:03:47 -0400 Received: from router-100M.swansea.linux.org.uk ([194.168.151.17]:2825 "EHLO the-village.bc.nu") by vger.kernel.org with ESMTP id ; Mon, 23 Apr 2001 19:03:15 -0400 Subject: Re: [RFC][PATCH] adding PCI bus information to SCSI layer To: Matt_Domsch@Dell.com Date: Tue, 24 Apr 2001 00:04:47 +0100 (BST) Cc: linux-kernel@vger.kernel.org, dougg@torque.net, alan@lxorguk.ukuu.org.uk, jlundell@pobox.com In-Reply-To: from "Matt_Domsch@Dell.com" at Apr 23, 2001 05:06:10 PM X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: From: Alan Cox Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > The i2o controller can be on any bus type (though I expect most are > PCI). The i2o_controller struct has an i2o_hrt member, which does have bus I've seen no non PCI one. > information, but the PCI struct doesn't include subsystem vendor and device > fields yet. We'd need to add an IOCTL to retrieve this information, > possibly one at a generic i2o level. The EDD 3.0 spec shows that a PCI i2o You can pull it from /proc if you know the bus info (which you can get by querying via i2o_config.o) - 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/