Feature request: Support names from the usb.ids database.

Feature: Export vendor and product names as described in the usb.ids file. Slightly related to https://github.com/pyusb/pyusb/issues/330.

The usb.ids file is the the canonical mapping of vendor and product names to ids. It is used by almost all USB related tooling that return vendor and product names.

libusb support here is limited and inconsistent, I’m not sure what’s going on. On my Ubuntu 20.04 system it doesn’t return vendor names for ids [0bda, 8087] but it does for [1d6b, 13d3]. 13d3 is incorrect. All of these devices are included in the usb.ids file.

>>> _ds = usb.core.find(find_all=True)
>>> for d in _ds:
...    print(d)
# Partial results -
DEVICE ID 0bda:0316 on Bus 004 Address 002 =================
 ...
 iManufacturer          :    0x1 Generic    ## Missing vendor name
 iProduct               :    0x2 USB3.0-CRW  ## Incorrect product description
 iSerialNumber          :    0x3 20120501030900000
 ...
DEVICE ID 1d6b:0003 on Bus 004 Address 001 =================
 ...
 iManufacturer          :    0x3 Linux 5.3.0-7625-generic xhci-hcd
 iProduct               :    0x2 xHCI Host Controller
 iSerialNumber          :    0x1 0000:3b:00.0
 ...
DEVICE ID 13d3:56b2 on Bus 001 Address 003 =================
 ...
 iManufacturer          :    0x1 SunplusIT Inc  ## Incorrect vendor name
 iProduct               :    0x2 Integrated Camera   ## Incorrect product description
 iSerialNumber          :    0x0 
 ...
DEVICE ID 8087:0a2b on Bus 001 Address 002 =================
 ...
 iManufacturer          :    0x0   ## Missing manufacturer name
 iProduct               :    0x0  ## Missing product name
 iSerialNumber          :    0x0 
 ...

There are several implementation options. If you think this is something that belongs in pyusb let me know and we can figure something out.

[Gestas]

@jonasmalacofilho got it, I’ll work on this.

[jonasmalacofilho]

I think we can include a copy of the data, but prefer the system provided copy on Linux (on the possible paths we have collected).

---

Regarding the API, I think a mixed approach would be useful: a low level DB lookup module plus some convenience methods or properties on Device.