g...@novadsp.com wrote: > > No good since there can be no data from device until you initiate a > > transfer. > > ? err, no. My device might well start to write back down the pipe as > soon as it has been configured.
That would be a violation of the USB protocol. What device controller are you using? Most of them interrupt when they are asked by the host to transfer data, and then your main firmware hands over whatever data is ready to be transmitted to the (internal or external) USB device controller. The device controller is not allowed to transmit on the wire until the host controller instructs it to. The misunderstanding is common. Bus communication is explained in chapters 5 and 8 of the USB 2.0 spec, they are really readable and I recommend reading through them. //Peter ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel