I'm currently working on a special signal collector.
The first problem is that it doesn't seem to comply with USB standards, since standard device requests like usb_get_status() don't work well (for example usb_get_status() requires a bitmap data buffer larger than 2 bytes to complete).
Moreover, as far as I have not the peripheral detailed specification, I'm trying to merely reproduce the behaviour it has under Windows. Then, I used many sniffers (USB Monitor, WDM Sniff, Snoopy Pro) and I found that the activation protocol foresees for "abort pipe" and "reset pipe" requests. These latter are implemented by Windows DDK with URB_FUNCTION_ABORT_PIPE and URB_FUNCTION_RESET_PIPE (see http://www.osronline.com/ddkx/buses/usbstrct_1e0i.htm ).
How can they be reproduced with a Linux system call, like usb_control_msg() or some other? Please consider that, following someone's tip, I already tried usb_clear_halt() but it didn't work (returns -75, EOVERFLOW)..
Could someone give suggestions?
Thank you, Michele
-- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.298 / Virus Database: 265.6.5 - Release Date: 12/26/2004
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users
