On Saturday 04 November 2006 1:23 pm, Till Harbaum wrote: > Hi, > > Am Samstag, 4. November 2006 21:38 schrieb David Brownell: > > If you've designed it so that the unrestricted requests can change > > device state, that's the design problem. Classic examples include > > I am doing exactly that ... ok, bad idea.
Then make the requests fall into the category that usbfs restricts ... > > And if you're using _only_ control requests it should be easy to > > do this right. You'll only get one control request at a time, > > Yes, i will. But they are related to each other. E.g. a i2c read-after-write > transfer will be done using two consecutive control transfers (a write > and a read request). If someone sends e.g. another write command > inbetween things will go wrong. 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. - Dave ------------------------------------------------------------------------- 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
