On Wed, Mar 01, 2006 at 05:53:14PM -0800, Pete Zaitcev wrote: > On Wed, 1 Mar 2006 17:36:17 -0800, Marc Singer <[EMAIL PROTECTED]> wrote: > > > Its response to #11 is what is > > broken. It may be getting confused by the second status request *or* > > it may have sent the STALL (is that the -32?) before it received the > > second GET_STATUS. > > If queueing in HCD works well, the device would be presented with the > second control request before the first one completed, and so the second > scenario should have played. This is my understanding of it, but I may > be wrong.
This scenario is coming from the USBTEST driver. It may be more demanding that the usual bear. > Why don't you enable tracing in UDC or whatever that thing is? > I gather that you are hacking on the device, so what does it see? Enabling DEBUG in the UDC driver makes it break even worse. Alan Stern recommended that I use USBMON to get a look at the exchanges. I'm trying to revive an existing UDC driver that doesn't work properly. David Brownell suggested that I start with the USB testing framework which has led me to this place. My suspicion is that this driver has never worked properly. I am probably going to have to reinstrument the driver for debug so that it isn't so invasive. The original debug code emits far more than I need for the task at hand. ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
