search..
No manual entry for -- in section 5
pci.ids(5)		       The PCI Utilities		     pci.ids(5)

NAME
       pci.ids - list of known identifiers related to PCI devices

INTRODUCTION
       Devices	on  the	 PCI bus are identified by a combination of a vendor ID
       (assigned by the PCI SIG) and device ID (assigned by the	 vendor).  Both
       IDs are 16-bit integers and the device itself provides no translation to
       a human-readable string.

       In  addition to the vendor and device, devices also report several other
       identifiers:

       o  Device class and subclass (two 8-bit numbers)

       o  Programming interface (8-bit number, meaning specific	 for  the  sub-
	  class)

       o  Subsystem,  which identifies the assembly in which the device is con-
	  tained.  A typical example is an Ethernet add-in card: the device  is
	  the  Ethernet	 controller  chip, while the card plays the role of the
	  subsystem. Subsystems have their vendor ID (from the	same  namespace
	  as  device  vendors)	and subsystem ID. Generally, the meaning of the
	  subsystem ID depends on the device, but there are cases  in  which  a
	  single  subsystem  ID is used for many devices - e.g., laptop mother-
	  boards.

	  The PCI utilities use the pci.ids file to translate all these numeric
	  IDs to strings.

KEEPING THE LIST UP-TO-DATE
       The pci.ids file is generated from the PCI ID database, which  is  main-
       tained at https://pci-ids.ucw.cz/.  If you find any IDs missing from the
       list, please contribute them to the database.

       You can use the update-pciids command to download the current version of
       the list.

       Alternatively, you can use lspci -q to query the database online.

FILE FORMAT
       The  pci.ids  file  is  a  text file in plain ASCII, interpreted line by
       line.  Lines starting with the hash sign are treated as comments are ig-
       nored.  Comments regarding a specific entry are written immediately  be-
       fore the entry.

       Vendor  entries	start with a 4-digit hexadecimal vendor ID, followed by
       one or more spaces, and the name of the vendor extending to the	end  of
       the line.

       Device entries are placed below the vendor entry. Each device entry con-
       sists  of  a single TAB character, a 4-digit hexadecimal device ID, fol-
       lowed by one or more spaces, and the name of the device extending to the
       end of the line.

       Subsystem entries are placed below the device entry. They start with two
       TAB characters, a 4-digit hexadecimal vendor ID (which must  be	defined
       elsewhere  in the list), a single space, a 4-digit hexadecimal subsystem
       ID, one or more spaces, and the name of the subsystem extending	to  the
       end of the line.

       Class  entries  consist of "C", one space, 2-digit hexadecimal class ID,
       one or more spaces, and the name of the class. Subclasses are placed be-
       low the corresponding class, indented by a single  TAB,	followed  by  a
       2-digit hexadecimal subclass ID, one or more spaces, and the name of the
       subclass.   Programming	interfaces  are below the subclass, indented by
       two TABs, followed by a 2-digit hexadecimal  prog-if  ID,  one  or  more
       spaces, and the name.

       There  can  be device-independent subsystem IDs, although the web inter-
       face of the database does not support them yet. They start with	a  sub-
       system vendor line consisting of "S", one space, and a 4-digit hexadeci-
       mal  vendor ID (which must correspond to an already listed vendor). Sub-
       systems follow on subsequent lines, each indented by one	 TAB,  followed
       by  a 4-digit hexadecimal subsystem ID, one or more spaces, and the name
       of the subsystem.

       To ensure extensibility of the format, lines starting with  an  unrecog-
       nized  letter followed by a single space are ignored and so are all fol-
       lowing TAB-indented lines.

FILES
       /usr/share/misc/pci.ids
	      Location of the list.

SEE ALSO
       lspci(8), update-pciids(8), pcilib(7)

AUTHOR
       The PCI Utilities are maintained by Martin Mares <mj@ucw.cz>.

pciutils-3.13.0			  30 May 2024			     pci.ids(5)