From owner-freebsd-scsi Mon Nov 8 14:30:19 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from front1m.grolier.fr (front1m.grolier.fr [195.36.216.51]) by hub.freebsd.org (Postfix) with ESMTP id 00E6F15245 for ; Mon, 8 Nov 1999 14:29:48 -0800 (PST) (envelope-from groudier@club-internet.fr) Received: from localhost (ppp-164-34.villette.club-internet.fr [195.36.164.34]) by front1m.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with SMTP id XAA20100 for ; Mon, 8 Nov 1999 23:29:43 +0100 (MET) Date: Tue, 9 Nov 1999 00:53:17 +0100 (MET) From: Gerard Roudier X-Sender: groudier@localhost To: scsi@FreeBSD.org Subject: Q: pci #bus #dev #func from device_t Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I need to know about the actual bus number, device number and function number of a PCI device from some driver that attached this device. Is there some method to get this information from device_t? For now I just fell back on the old pci bus methods that are #ifdefed in the driver source against the new bus methods. The corresponding informations seem to be stored in the device.ivars field that points to a structure that is private to the pci.c driver. Sorry if I missed something important. G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message