|
From: Peter S. <pe...@st...> - 2010-10-06 08:31:17
|
Xiaofan Chen wrote: > >> I do not think "usbfs" is a valid kernel driver name. > > > > It *is* the name of the kernel driver which is handling the device.. > > Okay I will take a look again. In this case, the patch is good. I'm hesitant about the patch. I see the point, but we would be changing semantics of the function, which I don't really like. usbfs is a kernel driver like any other, but I do see that apps may want a way to know if a *usable* driver is bound to the interface. > Still I am not that convinced that "usbfs" is really a kernel driver, What would convince you? > at least not in the typically meaning of "driver", rather it is > part of the USB core which is exposed to the user space. It *is* a separate driver. Sure it's not like the others in some ways, because it can be bound to any interface, and because it offers ioctls on the device files to userspace, but inside it uses exactly the same URB calls as kernel USB device drivers. It is really analogous to libusb0.sys in Windows. //Peter |