Hi Alan >Another possibility is to have the first byte of the data buffer contain an >indicator for which endpoint to use. Agreed, this could work to.
>But maybe the real problem is that your implementation is using the wrong >user interface. Presenting a single-device read/write API usually isn't >appropriate for a device that can control multiple I/O streams. In this case, what are the alternatives? I'm not committed to using the read/write API, but do not know of any other better way of user/kernel space interaction, seeing as I want to use the existing USB framework under Linux? Thanks again Flavio Pereira ------------------------------------------------------- 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://ads.osdn.com/?ad_ide95&alloc_id396&op=click _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
