[ 0.495759] pci 0000:01:00.0: [dabc:1017] type 00 class 0x020000
...
Since most people might not be intimately as familiar with PCIe terminology, allow me to quickly document what is going on here.
0000:00:00.0: is the identifier ...
[14e4:2712]: is the device’s [vendor id:device id], these vendor id identifiers are assigned by the PCI standard body to hardware vendors. Vendors are then free to define there own vendor id’s.
> Wouldn't it be really nice if dmesg had more info about devices?
No, it wouldn't, that'd just make the kernel another 1.5MB larger. It's large enough as it is. And if there is a driver for the device, the driver will print more things anyway.
Remember you're dealing with low-level system interfacing here. You're expected to bring some knowledge.
dmesg log :
[ 0.388790] pci 0000:00:00.0: [14e4:2712] type 01 class 0x060400
[ 0.388817] pci 0000:00:00.0: PME# supported from D0 D3hot
[ 0.389752] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 0.495733] brcm-pcie 1000110000.pcie: link up, 5.0 GT/s PCIe x1 (!SSC)
[ 0.495759] pci 0000:01:00.0: [dabc:1017] type 00 class 0x020000
...
Since most people might not be intimately as familiar with PCIe terminology, allow me to quickly document what is going on here.
0000:00:00.0: is the identifier ...
[14e4:2712]: is the device’s [vendor id:device id], these vendor id identifiers are assigned by the PCI standard body to hardware vendors. Vendors are then free to define there own vendor id’s.
The full list of official vendor id’s and released device id can be found : https://admin.pci-ids.ucw.cz/read/PC/14e4 or in the linux kernel code...
"""
Wouldn't it be really nice if dmesg had more info about devices?