1 .TH lspci 8 "@TODAY@" "@VERSION@" "The PCI Utilities"
3 lspci \- list all PCI devices
9 is a utility for displaying information about PCI buses in the system and
10 devices connected to them.
12 By default, it shows a brief list of devices. Use the options described
13 below to request either a more verbose output or output intended for
14 parsing by other programs.
16 If you are going to report bugs in PCI device drivers or in
18 itself, please include output of "lspci -vvx" or even better "lspci -vvxxx"
19 (however, see below for possible caveats).
21 Some parts of the output, especially in the highly verbose modes, are probably
22 intelligible only to experienced PCI hackers. For exact definitions of
23 the fields, please consult either the PCI specifications or the
26 .B /usr/include/linux/pci.h
29 Access to some parts of the PCI configuration space is restricted to root
30 on many operating systems, so the features of
32 available to normal users are limited. However,
34 tries its best to display as much as available and mark all other
41 .SS Basic display modes
44 Dump PCI device data in a backward-compatible machine readable form.
45 See below for details.
48 Dump PCI device data in a machine readable form for easy parsing by scripts.
49 See below for details.
52 Show a tree-like diagram containing all buses, bridges, devices and connections
58 Be verbose and display detailed information about all devices.
61 Be very verbose and display more details. This level includes everything deemed
65 Be even more verbose and display everything we are able to parse,
66 even if it doesn't look interesting at all (e.g., undefined memory regions).
69 Show kernel drivers handling each device and also kernel modules capable of handling it.
70 Turned on by default when
72 is given in the normal mode of output.
73 (Currently works only on Linux with kernel 2.6 or newer.)
76 Show hexadecimal dump of the standard part of the configuration space (the first
77 64 bytes or 128 bytes for CardBus bridges).
80 Show hexadecimal dump of the whole PCI configuration space. It is available only to root
81 as several PCI devices
83 when you try to read some parts of the config space (this behavior probably
84 doesn't violate the PCI standard, but it's at least very stupid). However, such
85 devices are rare, so you needn't worry much.
88 Show hexadecimal dump of the extended (4096-byte) PCI configuration space available
89 on PCI-X 2.0 and PCI Express buses.
92 Bus-centric view. Show all IRQ numbers and addresses as seen by the cards on the
93 PCI bus instead of as seen by the kernel.
96 Always show PCI domain numbers. By default, lspci suppresses them on machines which
100 Identify PCI devices by path through each bridge, instead of by bus number.
103 Identify PCI devices by path through each bridge, showing the bus number as
104 well as the device number.
106 .SS Options to control resolving ID's to names
109 Show PCI vendor and device codes as numbers instead of looking them up in the
113 Show PCI vendor and device codes as both numbers and names.
116 Use DNS to query the central PCI ID database if a device is not found in the local
118 file. If the DNS query succeeds, the result is cached in
120 and it is recognized in subsequent runs even if
122 is not given any more. Please use this switch inside automated scripts only
123 with caution to avoid overloading the database servers.
128 but the local cache is reset.
131 Query the central database even for entries which are recognized locally.
132 Use this if you suspect that the displayed entry is wrong.
134 .SS Options for selection of devices
136 .B -s [[[[<domain>]:]<bus>]:][<device>][.[<func>]]
137 Show only devices in the specified domain (in case your machine has several host bridges,
138 they can either share a common bus number space or each of them can address a PCI domain
139 of its own; domains are numbered from 0 to ffff), bus (0 to ff), device (0 to 1f) and function (0 to 7).
140 Each component of the device address can be omitted or set to "*", both meaning "any value". All numbers are
141 hexadecimal. E.g., "0:" means all devices on bus 0, "0" means all functions of device 0
142 on any bus, "0.3" selects third function of device 0 on all buses and ".4" shows only
143 the fourth function of each device.
145 .B -d [<vendor>]:[<device>][:<class>]
146 Show only devices with specified vendor, device and class ID. The ID's are
147 given in hexadecimal and may be omitted or given as "*", both meaning
156 as the PCI ID list instead of @IDSDIR@/pci.ids.
162 as the map of PCI ID's handled by kernel modules. By default, lspci uses
163 .RI /lib/modules/ kernel_version /modules.pcimap.
164 Applies only to Linux systems with recent enough module tools.
167 Invoke bus mapping mode which performs a thorough scan of all PCI devices, including
168 those behind misconfigured bridges, etc. This option gives meaningful results only
169 with a direct hardware access mode, which usually requires root privileges.
170 Please note that the bus mapper only scans PCI domain 0.
175 version. This option should be used stand-alone.
177 .SS PCI access options
179 The PCI utilities use the PCI library to talk to PCI devices (see
180 \fBpcilib\fP(7) for details). You can use the following options to
181 influence its behavior:
184 The library supports a variety of methods to access the PCI hardware.
185 By default, it uses the first access method available, but you can use
186 this option to override this decision. See \fB-A help\fP for a list of
187 available methods and their descriptions.
189 .B -O <param>=<value>
190 The behavior of the library is controlled by several named parameters.
191 This option allows to set the value of any of the parameters. Use \fB-O help\fP
192 for a list of known parameters and their default values.
195 Use direct hardware access via Intel configuration mechanism 1.
196 (This is a shorthand for \fB-A intel-conf1\fP.)
199 Use direct hardware access via Intel configuration mechanism 2.
200 (This is a shorthand for \fB-A intel-conf2\fP.)
203 Instead of accessing real hardware, read the list of devices and values of their
204 configuration registers from the given file produced by an earlier run of lspci -x.
205 This is very useful for analysis of user-supplied bug reports, because you can display
206 the hardware configuration in any way you want without disturbing the user with
207 requests for more dumps.
210 Increase debug level of the library.
212 .SH MACHINE READABLE OUTPUT
213 If you intend to process the output of lspci automatically, please use one of the
214 machine-readable output formats
218 described in this section. All other formats are likely to change
219 between versions of lspci.
222 All numbers are always printed in hexadecimal. If you want to process numeric ID's instead of
223 names, please add the
227 .SS Simple format (-m)
229 In the simple format, each device is described on a single line, which is
230 formatted as parameters suitable for passing to a shell script, i.e., values
231 separated by whitespaces, quoted and escaped if necessary.
232 Some of the arguments are positional: slot, class, vendor name, device name,
233 subsystem vendor name and subsystem name (the last two are empty if
234 the device has no subsystem); the remaining arguments are option-like:
242 Programming interface.
245 The relative order of positional arguments and options is undefined.
246 New options can be added in future versions, but they will always
247 have a single argument not separated from the option by any spaces,
248 so they can be easily ignored if not recognized.
250 .SS Verbose format (-vmm)
252 The verbose output is a sequence of records separated by blank lines.
253 Each record describes a single device by a sequence of lines, each line
261 are separated by a single tab character.
262 Neither the records nor the lines within a record are in any particular order.
263 Tags are case-sensitive.
266 The following tags are defined:
270 The name of the slot where the device resides
271 .RI ([ domain :] bus : device . function ).
272 This tag is always the first in a record.
288 Name of the subsystem vendor (optional).
292 Name of the subsystem (optional).
296 The physical slot where the device resides (optional, Linux only).
300 Revision number (optional).
304 Programming interface (optional).
308 Kernel driver currently handling the device (optional, Linux only).
312 Kernel module reporting that it is capable of handling the device
313 (optional, Linux only).
317 NUMA node this device is connected to (optional, Linux only).
320 New tags can be added in future versions, so you should silently ignore any tags you don't recognize.
322 .SS Backward-compatible verbose format (-vm)
324 In this mode, lspci tries to be perfectly compatible with its old versions.
325 It's almost the same as the regular verbose format, but the
328 tag is used for both the slot and the device name, so it occurs twice
329 in a single record. Please avoid using this format in any new code.
334 A list of all known PCI ID's (vendors, devices, classes and subclasses). Maintained
335 at https://pci-ids.ucw.cz/, use the
337 utility to download the most recent version.
339 .B @IDSDIR@/pci.ids.gz
340 If lspci is compiled with support for compression, this file is tried before pci.ids.
343 All ID's found in the DNS query mode are cached in this file.
347 Sometimes, lspci is not able to decode the configuration registers completely.
348 This usually happens when not enough documentation was available to the authors.
349 In such cases, it at least prints the
351 mark to signal that there is potentially something more to say. If you know
352 the details, patches will be of course welcome.
354 Access to the extended configuration space is currently supported only by the
360 .BR update-pciids (8),
364 The PCI Utilities are maintained by Martin Mares <mj@ucw.cz>.
projects / pciutils.git / blob