On Wed, 20 Aug 2003, Matthias Bruestle wrote: > > > I have not log here, which shows the first and second run. It works in 2.4 > > > and the driver does stop just the Int IN URB between runs, which is the same > > > it does in 2.4 and therefore I don't think, that anything can go wrong with > > > it. > > So why isn't your host controller receiving data that was sent properly? > > I'd like to say that it must be a hardware error -- except that it works > > under 2.4. > > It works under 2.4 and on the other computer under OpenBSD, but not > anymore under 2.6. And why does this happen not inside a program run, > but only in between? I don't think the hardware does notice this, > if the UHCI driver does nothing change. It works again, if I unplug and > replug the device. So probably something has changed in the open/close > handling in UHCI, which annoys the host controller.
I'm stumped. And there is no open/close handling in UHCI. Could it be that your program does something different before the first request and between the first & second? But that wouldn't explain why the interrupt URB isn't completing. It really sounds like a hardware problem: the interrupt data is getting sent to the host but the HC doesn't update the TD in memory. Alan Stern ------------------------------------------------------- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here:http://www.vmware.com/wl/offer/358/0 _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
