On Fri, 24 Sep 2004, Braman, Paul wrote: > Someone here at work suggested there might be an interrupt problem. > (Seeing as how the dropped frames are occuring at regular intervals.) I > do note that /proc/interrupts reports two uhci_hcd instances in IRQ 10. > I assume there is one for each controller, but what do I know? > > CPU0 > 10: 5283 XT-PIC uhci_hcd, uhci_hcd
That's right. Each controller has its own interrupt entry. But interrupts wouldn't cause the controller to think a frame had length 0. > > Another possibility is that some other program is trying to > > query your device every 27-28 milliseconds. Something like > > that might confuse the device enough to make it send an empty frame. > > I rebooted to single-user mode (2.6.9-rc2) and made sure the usbhid > driver wasn't loaded. Same behavior (I checked the debug output and > only my URBs were present). [shrugs] At this point I'm out of guesses. Short of hooking up a USB analyzer to see what's really on the bus, there's no way to know if the problem is in the computer or in the device. And even then it wouldn't be clear what the source of the problem actually is. > I guess I'll just need to track down another capture device that does > coaxial S/PDIF and see if I have the same problem. (Note that I did try > the optical S/PDIF input on this device and had the same behavior.) Okay. Alan Stern ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
