search for: geberally

...list returned by libusb, checks each entry against the matcher, and tells libusb if it wants to claim the device described by a particular entry. I don't think it walks further entries after a successful match and claim? We can't use the matcher directly, because its fields can be a regex geberally (e.g. `vendor=A*` instead of `APC` or `Aardwark` specifically), and because libusb device descriptors are a black box for us (FD, struct, blob - whatever the token we pass to library methods is on a platform and lib version). Also matching can involve callbacks, so a driver can probe the device in...

..., checks each entry against the matcher, and tells libusb if it wants > to claim the device described by a particular entry. I don't think it walks > further entries after a successful match and claim? > > We can't use the matcher directly, because its fields can be a regex > geberally (e.g. `vendor=A*` instead of `APC` or `Aardwark` specifically), > and because libusb device descriptors are a black box for us (FD, struct, > blob - whatever the token we pass to library methods is on a platform and > lib version). > > Also matching can involve callbacks, so a driver...