bose output or output intended for parsing by other programs.
-vvx” or even better “lspci -vvxxx” (however, see below for possible caveats).
enced PCI hackers. For exact definitions of the fields, please consult either the PCI specifications or the
header.h and /usr/include/linux/pci.h include files.
features of lspci available to normal users are limited. However, lspci tries its best to display as much as
available and mark all other information with <access denied> text.
Basic display modes
violate the PCI standard, but it’s at least very stupid). However, such devices are rare, so you
needn’t worry much.
Options to control resolving ID’s to names
runs even if -q is not given any more. Please use this switch inside automated scripts only with cau‐
tion to avoid overloading the database servers.
Options for selection of devices
Show only devices in the specified domain (in case your machine has several host bridges, they can
either share a common bus number space or each of them can address a PCI domain of its own; domains
are numbered from 0 to ffff), bus (0 to ff), slot (0 to 1f) and function (0 to 7). Each component of
the device address can be omitted or set to “*”, both meaning “any value”. All numbers are hexadeci‐
mal. E.g., “0:” means all devices on bus 0, “0” means all functions of device 0 on any bus, “0.3”
selects third function of device 0 on all buses and “.4” shows only the fourth function of each
may be omitted or given as “*”, both meaning “any value”.
nel_version/modules.pcimap. Applies only to Linux systems with recent enough module tools.
which usually requires root privileges. Please note that the bus mapper only scans PCI domain 0.
PCI access options
following options to influence its behavior:
access method available, but you can use this option to override this decision. See -A help for a list
of available methods and their descriptions.
value of any of the parameters. Use -O help for a list of known parameters and their default values.
ters from the given file produced by an earlier run of lspci -x. This is very useful for analysis of
user-supplied bug reports, because you can display the hardware configuration in any way you want
without disturbing the user with requests for more dumps.
机器可读的输出（MACHINE READABLE OUTPUT）
formats (-m, -vm, -vmm) described in this section. All other formats are likely to change between versions of
add the -n switch.
Simple format (-m)
for passing to a shell script, i.e., values separated by whitespaces, quoted and escaped if necessary. Some
of the arguments are positional: slot, class, vendor name, device name, subsystem vendor name and subsystem
name (the last two are empty if the device has no subsystem); the remaining arguments are option-like:
sions, but they will always have a single argument not separated from the option by any spaces, so they can
be easily ignored if not recognized.
Verbose format (-vmm)
by a sequence of lines, each line containing a single `tag: value’ pair. The tag and the value are separated
by a single tab character. Neither the records nor the lines within a record are in any particular order.
Tags are case-sensitive.
Backward-compatible verbose format (-vm)
ular verbose format, but the Device tag is used for both the slot and the device name, so it occurs twice in
a single record. Please avoid using this format in any new code.
ids.sourceforge.net/, use the update-pciids utility to download the most recent version.
enough documentation was available to the authors. In such cases, it at least prints the <?> mark to signal
that there is potentially something more to say. If you know the details, patches will be of course welcome.
setpci(8), update-pciids(8), pcilib(7)
- man 8 lspci, version pciutils-3.3.1