[quoted lines by Alan Stern on 2005/07/12 at 10:37 -0400] >You could try using the USBDEVFS_RESET ioctl before claiming the >interface. That ought to clear the data toggle.
That indeed does appear to work. It does cause the device at the far end of an FTDI serial adapter to report one framing error, but I guess that's its problem and I should just expect it. >Or you could always >unplug & replug the device just before running your program. It's the code for USB-connected braille displays, and I wouldn't want our users having to do that. >Alternatively, you could change your program so that it repeats the first >bulk write when necessary. The write which gets lost reports success, i.e. the ioctl() returns the number of bytes which were written even though they never get where they're supposed to go. Detecting that it didn't work isn't an option either because, on some models, the presence or absence of the response is part of the probing to determine what's there. -- Dave Mielke | 2213 Fox Crescent | I believe that the Bible is the Phone: 1-613-726-0014 | Ottawa, Ontario | Word of God. Please contact me EMail: [EMAIL PROTECTED] | Canada K2A 1H7 | if you're concerned about Hell. http://FamilyRadio.com/ | http://Mielke.cc/bible/ ------------------------------------------------------- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
