vcrhonek/hwdata

hwdata contains various hardware identification and configuration data, such as the pci.ids and usb.ids databases.

hwdata's Issues

Get pnp.ids from uefi.org?

I recently saw that the UEFI Forum (https://uefi.org) hosts its own registry of PNP IDs (and ACPI IDs, FWIW): https://www.uefi.org/PNP_ACPI_Registry
This registry seems to be actively updated, as seen by sorting the list by approval date: https://www.uefi.org/pnp_id_list?search=&order=field_pnp_approved_on_date&sort=desc
What is not clear to me is what is the relation of this registry with the Microsoft one, though.

Should hwdata switch to this registry for pnp.ids?

0.347: test suite is failing

Looks like something has been changed in 0.347 test suite and it started failing.

[tkloczko@barrel hwdata-0.347]$ make check
fatal: not a git repository (or any parent up to mount point /home/tkloczko)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
OK: /sbin/lspci -i pci.ids
OK: ./check-pci-ids.py
Listing usb devices:
sudo: podman: command not found
cat: /tmp/tmp.9gRim197YD/err.out: No such file or directory
Expected: pci.ids: UTF-8 Unicode text
 Got instead: pci.ids: ASCII text

USB 2433:b200

I wonder why
https://usb-ids.gowdy.us/read/UD/2433/b200
is know (I have this HW), but not present in usb.ids (albeit neither in gowdy.us). Can you enlight me please why it is not present in the file?

Consider moving off of GitHub

It would be great to move to a more open platform, like gitlab.freedesktop.org where other related projects are hosted.

Add a switch to disable installation of the kernel blacklist

I am not sure why a blacklist is included here. At any rate, some distributions (e.g. Arch Linux) find it undesirable to install such a blacklist in their hwdata package. Would it be reasonable to add a configure option to stop installing the blacklist file?

Test suite should not attempt to access host system PCI bus

When working on some sandboxing / permissions management in the Exherbo Linux package build system, I found that the hwdata test suite is running the command lspci -i pci.ids. This command attempts to read the list of devices from the host system PCI bus - and the sandboxing blocks that, resulting in lspci returning an error (and the test failing).

lspci supports a PCI bus access method named "dump" which reads from a text file instead of reading from the real hardware. The dump can be generated using lspci, like so:

$ lspci -x -n
00:00.0 0600: 1022:1630
00: 22 10 30 16 00 00 00 00 00 00 00 06 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 e1 87
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

(...)

And should be committed to the git repository as test data. That dump file can then be used to test that lspci is able to use the pci.ids file, with a command like the following:

$ lspci -A dump -O dump.name=lspci.dump -i pci.ids
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne Root Complex
(...)

Ship a pkg-config file

This would allow users of the library to easily check the dep and its version, and get the proper pkgdatadir.

Please add 8087:0033 AX211 Bluetooth