Content-type: text/html; charset=UTF-8

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE>Man page of pcilib</TITLE>
</HEAD><BODY>
<H1>pcilib</H1>
Section: The PCI Utilities (7)<BR>Updated: 30 May 2024<BR><A HREF="#index">Index</A>
<A HREF="index.html">Return to Main Contents</A><HR>

<A NAME="lbAB">&nbsp;</A>
<H2>NAME</H2>

pcilib - a library for accessing PCI devices
<P>
<A NAME="lbAC">&nbsp;</A>
<H2>DESCRIPTION</H2>

<P>
The PCI library (also known as <I>pcilib</I> and <I>libpci</I>) is a portable library
for accessing PCI devices and their configuration space.
<P>
<A NAME="lbAD">&nbsp;</A>
<H2>ACCESS METHODS</H2>

<P>
<P>

The library supports a variety of methods to access the configuration space
on different operating systems. By default, the first matching method in this
list is used, but you can specify override the decision (see the <B>-A</B> switch
of <I>lspci</I>).
<P>
<DL COMPACT>
<DT><B>linux-sysfs</B>

<DD>
The
<B>/sys</B>

filesystem on Linux 2.6 and newer. The standard header of the config space is available
to all users, the rest only to root. Supports extended configuration space, PCI domains,
VPD (from Linux 2.6.26), physical slots (also since Linux 2.6.26) and information on attached
kernel drivers.
<DT><B>linux-proc</B>

<DD>
The
<B>/proc/bus/pci</B>

interface supported by Linux 2.1 and newer. The standard header of the config space is available
to all users, the rest only to root.
<DT><B>intel-conf1</B>

<DD>
Direct hardware access via Intel configuration mechanism 1. Available on i386 and compatibles
on Linux, Solaris/x86, GNU Hurd, Windows, BeOS and Haiku. Requires root privileges.
<DT><B>intel-conf2</B>

<DD>
Direct hardware access via Intel configuration mechanism 2. Available on i386 and compatibles
on Linux, Solaris/x86, GNU Hurd, Windows, BeOS and Haiku. Requires root privileges. Warning: This method
is able to address only the first 16 devices on any bus and it seems to be very
unreliable in many cases.
<DT><B>mmio-conf1</B>

<DD>
Direct hardware access via Intel configuration mechanism 1 via memory-mapped I/O.
Mostly used on non-i386 platforms. Requires root privileges. Warning: This method
needs to be properly configured via the
<B>mmio-conf1.addrs</B>

parameter.
<DT><B>mmio-conf1-ext</B>

<DD>
Direct hardware access via Extended PCIe Intel configuration mechanism 1 via memory-mapped I/O.
Mostly used on non-i386 platforms. Requires root privileges. Warning: This method
needs to be properly configured via the
<B>mmio-conf1-ext.addrs</B>

parameter.
<DT><B>ecam</B>

<DD>
Direct hardware access via PCIe ECAM (Enhanced Configuration Access Mechanism).
Available on all PCIe-compliant hardware. Requires root privileges and access
to physical memory (on Linux systems disabled CONFIG_STRICT_DEVMEM option). On
ACPI compatible systems is ECAM mapping read from the MCFG table specified by the
<B>ecam.acpimcfg</B>

parameter. On EFI compatible systems, ACPI MCFG table can be located in physical
memory via EFI system table specified by the
<B>ecam.efisystab</B>

parameter. On FreeBSD/NetBSD systems, physical address of ACPI MCFG table can be
located by kenv or sysctl interface when the
<B>ecam.bsd</B>

parameter is not disabled. On x86 BIOS compatible systems, ACPI MCFG table can
be located in physical memory by scanning x86 BIOS memory when the
<B>ecam.x86bios</B>

parameter is not disabled. Alternatively ECAM mappings can be specified by the
<B>ecam.addrs</B>

parameter which takes precedence over ACPI MCFG table. This option is required
on systems without ACPI and also on systems without EFI or x86 BIOS.
<DT><B>fbsd-device</B>

<DD>
The
<B>/dev/pci</B>

device on FreeBSD. Requires root privileges.
<DT><B>aix-device</B>

<DD>
Access method used on AIX. Requires root privileges.
<DT><B>nbsd-libpci</B>

<DD>
The
<B>/dev/pci0</B>

device on NetBSD accessed using the local libpci library.
<DT><B>obsd-device</B>

<DD>
The
<B>/dev/pci</B>

device on OpenBSD. Requires root privileges.
<DT><B>dump</B>

<DD>
Read the contents of configuration registers from a file specified in the
<B>dump.name</B>

parameter. The format corresponds to the output of <I>lspci</I> <B>-x</B>.
<DT><B>darwin</B>

<DD>
Access method used on Mac OS X / Darwin. Must be run as root and the system
must have been booted with debug=0x144.
<DT><B>win32-cfgmgr32</B>

<DD>
Device listing on Windows systems using the Windows Configuration Manager
via cfgmgr32.dll system library. This method does not require any special
Administrator rights or privileges. Configuration Manager provides only basic
information about devices, assigned resources and device tree structure. There
is no access to the PCI configuration space but libpci either tries to use
other access method to access configuration space or it provides read-only
virtual emulation based on information from Configuration Manager. Other
access method can be chosen by the
<B>win32.cfgmethod</B>

parameter. By default the first working one is selected (if any). Starting
with Windows 8 (NT 6.2) it is not possible to retrieve resources from 32-bit
application or library on 64-bit system.
<DT><B>win32-sysdbg</B>

<DD>
Access to the PCI configuration space via NT SysDbg interface on Windows
systems. Process needs to have Debug privilege, which local Administrators
have by default. Not available on 64-bit systems and neither on recent 32-bit
systems. Only devices from the first domain are accessible and only first
256 bytes of the PCI configuration space is accessible via this method.
<DT><B>win32-kldbg</B>

<DD>
Access to the PCI configuration space via Kernel Local Debugging Driver
kldbgdrv.sys. This driver is not part of the Windows system but is part of
the Microsoft WinDbg tool. It is required to have kldbgdrv.sys driver installed
in the system32 directory or to have windbg.exe or kd.exe binary in PATH.
kldbgdrv.sys driver has some restrictions. Process needs to have Debug privilege
and Windows system has to be booted with Debugging option. Debugging option can
be enabled by calling (takes effect after next boot):
<B>bcdedit /debug on</B>

<DT><DD>
Download links for WinDbg 6.12.2.633 standalone installer from Microsoft Windows
SDK for Windows 7 and .NET Framework 4:
<BR>

amd64: <A HREF="https://download.microsoft.com/download/A/6/A/A6AC035D-DA3F-4F0C-ADA4-37C8E5D34E3D/setup/WinSDKDebuggingTools_amd64/dbg_amd64.msi">https://download.microsoft.com/download/A/6/A/A6AC035D-DA3F-4F0C-ADA4-37C8E5D34E3D/setup/WinSDKDebuggingTools_amd64/dbg_amd64.msi</A>
<BR>

ia64: <A HREF="https://download.microsoft.com/download/A/6/A/A6AC035D-DA3F-4F0C-ADA4-37C8E5D34E3D/setup/WinSDKDebuggingTools_ia64/dbg_ia64.msi">https://download.microsoft.com/download/A/6/A/A6AC035D-DA3F-4F0C-ADA4-37C8E5D34E3D/setup/WinSDKDebuggingTools_ia64/dbg_ia64.msi</A>
<BR>

x86: <A HREF="https://download.microsoft.com/download/A/6/A/A6AC035D-DA3F-4F0C-ADA4-37C8E5D34E3D/setup/WinSDKDebuggingTools/dbg_x86.msi">https://download.microsoft.com/download/A/6/A/A6AC035D-DA3F-4F0C-ADA4-37C8E5D34E3D/setup/WinSDKDebuggingTools/dbg_x86.msi</A>
<DT><DD>
Archived download links of previous WinDbg versions:
<BR>

<A HREF="https://web.archive.org/web/20110221133326/https://www.microsoft.com/whdc/devtools/debugging/installx86.mspx">https://web.archive.org/web/20110221133326/https://www.microsoft.com/whdc/devtools/debugging/installx86.mspx</A>
<BR>

<A HREF="https://web.archive.org/web/20110214012715/https://www.microsoft.com/whdc/devtools/debugging/install64bit.mspx">https://web.archive.org/web/20110214012715/https://www.microsoft.com/whdc/devtools/debugging/install64bit.mspx</A>
<DT><B>aos-expansion</B>

<DD>
Access method used on PowerPC Amiga running OS4+. Access is made through Expansion.library. It offers read and write access to configuration space.
<P>
</DL>
<A NAME="lbAE">&nbsp;</A>
<H2>PARAMETERS</H2>

<P>
<P>

The library is controlled by several parameters. They should have sensible default
values, but in case you want to do something unusual (or even something weird),
you can override them (see the <B>-O</B> switch of <I>lspci</I>).
<P>
<A NAME="lbAF">&nbsp;</A>
<H3>Parameters of specific access methods</H3>

<P>
<DL COMPACT>
<DT><B>dump.name</B>

<DD>
Name of the bus dump file to read from.
<DT><B>fbsd.path</B>

<DD>
Path to the FreeBSD PCI device.
<DT><B>nbsd.path</B>

<DD>
Path to the NetBSD PCI device.
<DT><B>obsd.path</B>

<DD>
Path to the OpenBSD PCI device.
<DT><B>proc.path</B>

<DD>
Path to the procfs bus tree.
<DT><B>sysfs.path</B>

<DD>
Path to the sysfs device tree.
<DT><B>devmem.path</B>

<DD>
Path to the /dev/mem device.
<DT><B>mmio-conf1.addrs</B>

<DD>
Physical addresses of memory-mapped I/O ports for Intel configuration mechanism 1.
CF8 (address) and CFC (data) I/O port addresses are separated by slash and
multiple addresses for different PCI domains are separated by commas.
Format: 0xaddr1/0xdata1,0xaddr2/0xdata2,...
<DT><B>mmio-conf1-ext.addrs</B>

<DD>
Physical addresses of memory-mapped I/O ports for Extended PCIe Intel configuration mechanism 1.
It has same format as
<B>mmio-conf1.addrs</B>

parameter.
<DT><B>ecam.addrs</B>

<DD>
Physical addresses of PCIe ECAM mappings. Each mapping must contains first PCI
bus number and physical address where mapping starts. And then it may contain
the length of the mapping, the last PCI bus number and PCI domain number. When
the last PCI bus number is not provided then it is calculated from the length
of the mapping or it is assumed 0xff. When length of the mapping is provided
then it is calculated from the last PCI bus number. And when PCI domain is not
provided then 0x0 is assumed. All numbers must be supplied in hexadecimal form
(leading prefix 0x is not required). Multiple mappings are separated by commas.
Format: [domain:]start_bus[-end_bus]:start_addr[+length],...
<DT><B>ecam.acpimcfg</B>

<DD>
Path to the ACPI MCFG table. Processed by the
<B><A HREF="glob.3.html">glob</A></B>(3)

function, so it may contain wildcards (*).
<DT><B>ecam.efisystab</B>

<DD>
Path to the EFI system table.
<DT><B>ecam.bsd</B>

<DD>
When not set to 0 then use BSD kenv or sysctl to find ACPI MCFG table. Default
value is 1 on BSD systems.
<DT><B>ecam.x86bios</B>

<DD>
When not set to 0 then scan x86 BIOS memory for ACPI MCFG table. Default value
is 1 on x86 systems.
<DT><B>win32.cfgmethod</B>

<DD>
Config space access method to use with win32-cfgmgr32 on Windows systems. Value
<I>auto</I>

or an empty string selects the first access method which supports access
to the config space on Windows. Value
<I>win32-cfgmgr32</I>

or
<I>none</I>

only builds a read-only virtual emulated config space with information from the
Configuration Manager.
<P>
</DL>
<A NAME="lbAG">&nbsp;</A>
<H3>Parameters for resolving of ID's via DNS</H3>

<DL COMPACT>
<DT><B>net.domain</B>

<DD>
DNS domain containing the ID database.
<DT><B>net.cache_name</B>

<DD>
Name of the file used for caching of resolved ID's. An initial
<B>~/</B>

is expanded to the user's home directory.
<P>
</DL>
<A NAME="lbAH">&nbsp;</A>
<H3>Parameters for resolving of ID's via UDEV's HWDB</H3>

<DL COMPACT>
<DT><B>hwdb.disable</B>

<DD>
Disable use of HWDB if set to a non-zero value.
<P>
</DL>
<A NAME="lbAI">&nbsp;</A>
<H2>SEE ALSO</H2>

<P>
<B><A HREF="lspci.8.html">lspci</A></B>(8),

<B><A HREF="setpci.8.html">setpci</A></B>(8),

<B><A HREF="pci.ids.5.html">pci.ids</A></B>(5),

<B><A HREF="update-pciids.8.html">update-pciids</A></B>(8)

<P>
<A NAME="lbAJ">&nbsp;</A>
<H2>AUTHOR</H2>

The PCI Utilities are maintained by Martin Mares &lt;<A HREF="mailto:mj@ucw.cz">mj@ucw.cz</A>&gt;.
<P>

<HR>
<A NAME="index">&nbsp;</A><H2>Index</H2>
<DL>
<DT><A HREF="#lbAB">NAME</A><DD>
<DT><A HREF="#lbAC">DESCRIPTION</A><DD>
<DT><A HREF="#lbAD">ACCESS METHODS</A><DD>
<DT><A HREF="#lbAE">PARAMETERS</A><DD>
<DL>
<DT><A HREF="#lbAF">Parameters of specific access methods</A><DD>
<DT><A HREF="#lbAG">Parameters for resolving of ID's via DNS</A><DD>
<DT><A HREF="#lbAH">Parameters for resolving of ID's via UDEV's HWDB</A><DD>
</DL>
<DT><A HREF="#lbAI">SEE ALSO</A><DD>
<DT><A HREF="#lbAJ">AUTHOR</A><DD>
</DL>
<HR>
This document was created by
<A HREF="index.html">man2html</A>,
using the manual pages.<BR>
Time: 11:48:50 GMT, September 14, 2026
</BODY>
</HTML>