Re: usb_control_msg question
"Gabriel Maganis" <[email protected]>
| Newsgroups | gmane.linux.usb.devel |
|---|---|
| Message-ID | <[email protected]> |
Hello Pete, Thanks for your help but the usbmon traces are exactly what's confusing because the only difference is that the device responds with the idle value if I do it using libusb i.e. below kernel module ded0a9c0 1879410740 S Co:002:00 s 21 0a aa00 0000 0000 0 ded0a9c0 1879413621 C Co:002:00 0 0 ded0a9c0 1879413858 S Ci:002:00 s a1 02 0000 0000 0001 1 < ded0a9c0 1879417615 C Ci:002:00 0 1 = 00 libusb ded0a8c0 1974666847 S Co:002:00 s 21 0a aa00 0000 0000 0 ded0a8c0 1974668987 C Co:002:00 0 0 ded0a8c0 1974669016 S Ci:002:00 s a1 02 0000 0000 0001 1 < ded0a8c0 1974672978 C Ci:002:00 0 1 = aa Any ideas? Btw, yes I've realized the rcvctrlpipe problem. Thanks. On 7/17/07, Pete Zaitcev <[email protected]> wrote: > On Tue, 17 Jul 2007 11:04:05 -0700, "Gabriel Maganis" <[email protected]> wrote: > > > ret = usb_control_msg(dev, > > usb_rcvctrlpipe(dev, 0), > > SET_IDLE, > > (0x01 << 5) + 0x01, > > 0xaa00, 0, data, 0, USB_CTRL_SET_TIMEOUT); > > Are you sure you want to use input pipe with SET_IDLE? > > > I've been able to do all of this using libusb in user space > > but have no success within a kernel module. > > Compare usbmon traces for two cases, the difference should be evident. > > -- Pete > ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel