From owner-freebsd-questions Mon Nov 5 17: 0: 7 2001 Delivered-To: freebsd-questions@freebsd.org Received: from mail.monochrome.org (b4.ebbed1.client.atlantech.net [209.190.235.180]) by hub.freebsd.org (Postfix) with ESMTP id EBDD637B416 for ; Mon, 5 Nov 2001 17:00:02 -0800 (PST) Received: from localhost (faro [192.168.1.7]) by mail.monochrome.org (8.9.3/8.9.3) with SMTP id TAA93655; Mon, 5 Nov 2001 19:59:40 -0500 (EST) (envelope-from chris@monochrome.org) Date: Mon, 5 Nov 2001 19:59:40 -0500 (EST) From: Chris Hill X-Sender: chris@localhost To: Rob B Cc: questions@FreeBSD.ORG Subject: Re: /proc/pci equivalent? In-Reply-To: <5.1.0.14.2.20011106114638.020d9d90@pop.ozemail.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 6 Nov 2001, Rob B wrote: > Is there a way to see what is on the PCI bus of a system? Under Linux, I > could do : > > cat /proc/pci > > and get a dump of everything on the bus. Is there a command like it in > FreeBSD? You could try scanpci - it tells you stuff like pci bus 0x0 cardnum 0x12 function 0x0000: vendor 0x1000 device 0x000f NCR 53C875 STATUS 0x0210 COMMAND 0x0007 CLASS 0x01 0x00 0x00 REVISION 0x26 BIST 0x00 HEADER 0x00 LATENCY 0x40 CACHE 0x08 ...etc., blah bla HTH. -- Chris Hill chris@monochrome.org ** [ Busy Expunging <\> ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message