1 .TH lspci 8 "@TODAY@" "@VERSION@" "The PCI Utilities"
4 lspci \- list all PCI devices
10 is a utility for displaying information about all PCI buses in the system and
11 all devices connected to them.
13 By default, it shows a brief list of devices. Use the options described
14 below to request either a more verbose output or output intended for
15 parsing by other programs.
17 If you are going to report bugs in PCI device drivers or in
19 itself, please include output of "lspci -vvx" or even better "lspci -vvxxx"
20 (however, see below for possible caveats).
22 Some parts of the output, especially in the highly verbose modes, is probably
23 intelligible only to experienced PCI hackers. For the exact definitions of
24 the fields, please consult either the PCI specifications or the
27 .B /usr/include/linux/pci.h
30 Access to some parts of the PCI configuration space is restricted to root
31 on many operating systems, so the features of
33 available to normal users are limited. However,
35 tries its best to display as much as available and mark all other
43 Be verbose and display detailed information about all devices.
46 Be very verbose and display more details. This level includes everything deemed
50 Be even more verbose and display everything we are able to parse,
51 even if it doesn't look interesting at all (e.g., undefined memory regions).
54 Show PCI vendor and device codes as numbers instead of looking them up in the
58 Show PCI vendor and device codes as both numbers and names.
61 Show hexadecimal dump of the standard part of the configuration space (the first
62 64 bytes or 128 bytes for CardBus bridges).
65 Show hexadecimal dump of the whole PCI configuration space. It is available only to root
66 as several PCI devices
68 when you try to read some parts of the config space (this behavior probably
69 doesn't violate the PCI standard, but it's at least very stupid). However, such
70 devices are rare, so you needn't worry much.
73 Show hexadecimal dump of the extended (4096-byte) PCI configuration space available
74 on PCI-X 2.0 and PCI Express buses.
77 Bus-centric view. Show all IRQ numbers and addresses as seen by the cards on the
78 PCI bus instead of as seen by the kernel.
81 Show a tree-like diagram containing all buses, bridges, devices and connections
84 .B -s [[[[<domain>]:]<bus>]:][<slot>][.[<func>]]
85 Show only devices in the specified domain (in case your machine has several host bridges,
86 they can either share a common bus number space or each of them can address a PCI domain
87 of its own; domains are numbered from 0 to ffff), bus (0 to ff), slot (0 to 1f) and function (0 to 7).
88 Each component of the device address can be omitted or set to "*", both meaning "any value". All numbers are
89 hexadecimal. E.g., "0:" means all devices on bus 0, "0" means all functions of device 0
90 on any bus, "0.3" selects third function of device 0 on all buses and ".4" shows only
91 the fourth function of each device.
93 .B -d [<vendor>]:[<device>]
94 Show only devices with specified vendor and device ID. Both ID's are given in
95 hexadecimal and may be omitted or given as "*", both meaning "any value".
101 as the PCI ID list instead of @IDSDIR@/pci.ids.
104 Dump PCI device data in a backward-compatible machine readable form.
105 See below for details.
108 Dump PCI device data in a machine readable form for easy parsing by scripts.
109 See below for details.
112 Always show PCI domain numbers. By default, lspci suppresses them on machines which
116 Invoke bus mapping mode which performs a thorough scan of all PCI devices, including
117 those behind misconfigured bridges etc. This option is available only to root and it
118 gives meaningful results only if combined with direct hardware access mode (otherwise
119 the results are identical to normal listing modes, modulo bugs in lspci). Please note
120 that the bus mapper doesn't support PCI domains and scans only domain 0.
125 version. This option should be used stand-alone.
127 .SH PCILIB AND ITS OPTIONS
128 The PCI utilities use PCILIB (a portable library providing platform-independent
129 functions for PCI configuration space access) to talk to the PCI cards. It supports
130 the following access methods:
136 filesystem on Linux 2.6 and newer. The standard header of the config space is available
137 to all users, the rest only to root. Supports extended configuration space and PCI domains.
142 interface supported by Linux 2.1 and newer. The standard header of the config space is available
143 to all users, the rest only to root.
146 Direct hardware access via Intel configuration mechanism 1. Available on i386 and compatibles
147 on Linux, Solaris/x86, GNU Hurd and Windows. Requires root privileges.
150 Direct hardware access via Intel configuration mechanism 2. Available on i386 and compatibles
151 on Linux, Solaris/x86 and GNU Hurd. Requires root privileges. Warning: This method
152 is able to address only first 16 devices on any bus and it seems to be very
153 unreliable in many cases.
158 device on FreeBSD. Requires root privileges.
161 Access method used on AIX. Requires root privileges.
166 device on NetBSD accessed using the local libpci library.
169 By default, PCILIB uses the first available access method and displays no debugging
170 messages, but you can use the following switches to control its behavior:
174 Force use of the linux_proc access method, using
176 instead of /proc/bus/pci.
179 Use direct hardware access via Intel configuration mechanism 1.
182 Use direct hardware access via Intel configuration mechanism 2.
185 Extract all information from given file containing output of lspci -x. This is very
186 useful for analysis of user-supplied bug reports, because you can display the
187 hardware configuration in any way you want without disturbing the user with
188 requests for more dumps.
191 Increase debug level of the library.
193 .SH MACHINE READABLE OUTPUT
194 If you intend to process the output of lspci automatically, please use one of the
195 machine-readable output formats
199 described in this section. All other formats are likely to change
200 between versions of lspci.
203 All numbers are always printed in hexadecimal. If you want to process numeric ID's instead of
204 names, please add the
208 .SS Simple format (-m)
210 In the simple format, each device is described on a single line, which is
211 formatted as parameters suitable for passing to a shell script, i.e., values
212 separated by whitespaces, quoted and escaped if necessary.
213 Some of the arguments are positional: slot, class, vendor name, device name,
214 subsystem vendor name and subsystem name (the last two are empty if
215 the device has no subsystem); the remaining arguments are option-like:
223 Programming interface.
226 The relative order of positional arguments and options is undefined.
227 New options can be added in future versions, but they will always
228 have a single argument not separated from the option by any spaces,
229 so they can be easily ignored if not recognized.
231 .SS Verbose format (-vmm)
233 The verbose output is a sequence of records separated by blank lines.
234 Each record describes a single device by a sequence of lines, each line
242 are separated by a single tab character.
243 Neither the records nor the lines within a record are in any particular order.
244 Tags are case-sensitive.
247 The following tags are defined:
251 The name of the slot where the device resides
252 .RI ([ domain :] bus : device . function ).
253 This tag is always the first in a record.
269 Name of the subsystem vendor (optional).
273 Name of the subsystem (optional).
277 Revision number (optional).
281 Programming interface (optional).
284 New tags can be added in future versions, so you should silently ignore any tags you don't recognize.
286 .SS Backward-compatible verbose format (-vm)
288 In this mode, lspci tries to be perfectly compatible with its old versions.
289 It's almost the same as the regular verbose format, but the
292 tag is used for both the slot and the device name, so it occurs twice
293 in a single record. Please avoid using this format in any new code.
298 A list of all known PCI ID's (vendors, devices, classes and subclasses). Maintained
299 at http://pciids.sourceforge.net/, use the
301 utility to download the most recent version.
303 .B @IDSDIR@/pci.ids.gz
304 If lspci is compiled with support for compression, this file is tried before pci.ids.
307 An interface to PCI bus configuration space provided by the post-2.1.82 Linux
308 kernels. Contains per-bus subdirectories with per-card config space files and a
310 file containing a list of all PCI devices.
314 .BR update-pciids (8)
317 The PCI Utilities are maintained by Martin Mares <mj@ucw.cz>.