Closed mvp closed 6 years ago
This is definitely a libusb issue. Filed a bug against libusb https://github.com/libusb/libusb/issues/303
This is fixed in libusb tree https://github.com/libusb/libusb/commit/871eb299b989bc0714391804a9d2fdb145a32ff5, but it is not yet released as official libusb version.
Until it is released, workaround to get uhubctl properly working is to install libusb
from head revision:
brew uninstall libusb
brew install libusb --HEAD
cd uhubctl
make
libusb-1.0.22-rc1 is out, which means that final release for libusb-1.0.22 is imminent, and it contains a fix for this problem.
Once libusb-1.0.22 is released and finds its way into Homebrew updates, this issue can be closed - hopefully very soon.
Finally, libusb-1.0.22 is in homebrew, so this can be closed. It only took 10 months...
On MacOS Sierra 10.12.4 (16E195), uhubctl prints identical hub id
64-1
for 2 different hubs:This must be an issue with libusb, need to investigate.