Hi, Am Samstag, 4. November 2006 23:12 schrieb David Brownell: > If you associate those with e.g. interface #0 then only your kernel > driver will be able to issue those control requests though ... the > point being not to use the _unrestricted_ request types, instead > use USB_RECIP_INTERFACE in the bRequestType field. I have tried just setting the request type to include USB_RECIP_INTERFACE in both, the kernel driver and the libusb application. And i can still easily run both parts at the same time.
Is this something that has to be rejected by the device? You last remark > only your kernel driver will be able to issue those control requests made me assume that the libusb will not even be allowed to send these requests. But it just sends these. I found libusb based example drivers that claim interface 0 before doing control transfers with USB_RECIP_INTERFACE set. When i am also claiming interface 0 in my libusb client i get an error message if the kernel driver is already loaded. Great! But i am confused that my libusb based client can just omit to claim the device and then send the commands anyway ... Regards, Till ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
