Ticket #67 (new enhancement)

Opened 6 years ago

Last modified 5 years ago

To be able to report the name of the current driver

Reported by: xiaofan Owned by:
Milestone: Component: libusb-1.0
Keywords: kernel Cc:
Blocked By: Blocks:

Description

Please refer to this thread.
http://marc.info/?l=libusb-devel&m=128655552910330&w=2

"I agree that it makes sense for libusb to be aware of a device's current driver before trying to detach it. It might also be desirable to avoid ever detaching the usbfs driver -- however this is a matter to be settled by the designers and users of libusb. It should not be enforced by the kernel.

Certainly libusb-0.1's ability to report the name of the current driver shouldn't be given up in libusb-1.0. That's a backward step.

Alan Stern"

Change History

comment:1 Changed 6 years ago by pbatard

I'm not sure if the name of the driver is really necessary, as this information would only have a specific application usage and may be subject to change. Still, I think returning the name of the driver is probably something we want to be able to return, but I believe what we want to provide first and foremost is a driver status for each libusb device we list, with something like:
o full libusb compatibility
o partial libusb compatibility (if possible, switching to a better driver is recommended)
o no libusb compatibility (if possible, switching to a libusb compatible driver is recommended)

Having such a feature would also enhance the Windows and OSX backends, as this level of information can be provided to end users.

comment:2 Changed 5 years ago by stuge

  • Keywords driver, usbfs removed
Note: See TracTickets for help on using tickets.