On Tue, 5 Feb 2008 [EMAIL PROTECTED] wrote: > Gotcha, thanks for replying Alan > > So is that the final word, you can't bind devices to drivers via the shell > ? You have to compile a program in order to bind a device to a driver ?
No, your original understanding was correct, but usbfs is a special case. It isn't a real driver at all -- it's merely a conduit allowing user programs to act as drivers. > Does this conflict with http://lwn.net/Articles/143397/ ? > > It's just that I am OK with bash but haven't done much C/C++ > > For the device I am using I already have the binary that talks to libusb. > And I already have a running implementation of libusb. I thought that all I > was missing was having the device tied to usbfs so that libusb could use it > ( am I right in the asumption that libusb needs to work through usbfs > rather than the other drivers ? ) All devices are automatically tied to usbfs when they are detected. You don't have to do anything special to use them with libusb (and yes, libusb uses usbfs internally). > "Device tied to USBFS" (missing) ----> "Libusb in place" (got it) ----> > "Binary which talks to libusb" (got it) What happens if you simply run the program without trying to do anything fancy? Alan Stern - To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
