Date: Thu, 21 Dec 2017 20:14:58 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 224454] Feature request: implement libusb_get_parent and libusb_has_capability Message-ID: <bug-224454-17-lYuy3quThu@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-224454-17@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224454 --- Comment #3 from Hans Petter Selasky <hselasky@FreeBSD.org> --- Hi, libusb is the same for -12 and -11. Just make a patch for your current system and I'll fix the rest. > I think libusb_has_capability is easier to implement. Do you think it is correct for libusb_has_capability to always return 1 for the hotplug capability? Can you check what is expected by the hotplug capability? What functions must be implemented when this capability returns 1? > I found there is another missing function today: > libusb_interrupt_event_handler. gvfs uses it in its MTP backend, > and this is the only libusb function it calls. gvfs has an > option to disable libusb support, so it doesn't cause build problems. Is this a variant of the existing "libusb_event_handler_active()"? Can you investigate a bit? --HPS -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-224454-17-lYuy3quThu>