PCICFG - Show configuration space for PCI devices
	   =================================================

			    Version 1.19
		  Copyright 1997,1998,1998,1999 Ralf Brown

PCICFG is a small utility to tell you more than you ever wanted to
know about the PCI devices in your computer.  To install it, you can
simply extract all of the files in the distribution archive into a
directory on your hard disk.  A minimal installation consists of
PCICFG.EXE and PCICFG.DAT; to enable the Verbose option, you will also
need the *.PCI files.

<<UPDATES>> The newest version of the PCICFG.DAT file (as well as the
full distribution archive) is always available at
     http://www.pobox.com/~ralf/files.html#RBpci


			  Running PCICFG
			  ==============

There are two ways to run PCICFG in normal use:
	PCICFG [flag(s)] bus device function
	PCICFG [flag(s)] *		       (to scan all devices)

PCI devices have an address which is broken down into a PCI-bus number
(usually 0), a device number within that bus (0-31), and a function
number within the device (0-7).  The majority of devices have only a
single function (0); multi-function devices are those which incorporate
very different functionalities within a single chip, i.e.  a chip which
is both a SCSI and an EIDE controller might present separate function
numbers for each.  If you use the first form of the commandline, PCICFG
will display information on only the specified device (or function for
a multi-function device).

Since you will probably not know the addresses of the devices in your
computer, the second form of the commandline tells PCICFG to scan all
possible PCI addresses for active devices.  You will generally want to
run this with the -t flag (see below) the very first time you use
PCICFG in order to find out which devices are installed.

The three optional flags which PCICFG supports are:
        -t      terse -- output only device type and ID
        -v      verbose output for known devices
	-b[N]	bypass BIOS and talk directly to PCI ports

Use -v for more verbose output on devices specifically recognized by
PCICFG (these are described by the *.PCI files, where the first four
characters of the filename are the vendor ID and the next four the
device ID).  Output is generally quite lengthy even without -v, so you
should redirect output into a file or pipe it to MORE or LIST.

On most systems, the default of using the BIOS calls should be OK.  If
you encounter a problem (such as on some older [1996] Award BIOSes),
you can try the -b option, which tells PCICFG to access the PCI
configuration ports directly.  If a digit follows the -b, then the
automatic determination of the appropriate access method will be
overridden and the specified method will be used regardless of what the
BIOS reports.  There are two incompatible methods for accessing the
ports; on most chipsets, -b1 is the proper method ("PCI Configuration
Space Access Mechanism #1").  On some chipsets (mostly the earliest
ones supporting PCI), you will need to use -b2 ("PCI Configuration
Space Access Mechanism #2").  USING THE INCORRECT METHOD CAN HANG OR
RESET YOUR COMPUTER!  Intel's Saturn and Neptune chipsets require -b2,
and will reset when attempting to access certain PCI addresses with -b1
because the latter can set the chipset's "reboot" bit....

For system maintenance, a third method of running PCICFG is available:
	PCICFG -m filename [filename ...]
which will merge the vendor/device IDs contained in the specified files
into PCICFG.DAT if they are not already present.


				Examples
				========

Example 1: PCICFG -t *

PCICFG v1.10 (c) Copyright 1997,1998 Ralf Brown
PCI bus 00 device 00 function 00:  Header Type 'non-bridge' (single-func)
Intel Corporation