Dave,
is it right that I can only submit one int urb just now? I mean, period is one frame. After I've changed the (status && --frame) to
(status && frame--) in order to prevent the endless loop I get the following result (added some debugging msgs):
I submit one IRQ in urb (works fine) and one IRQ out urb (doesn't work):
... Jul 30 16:52:32 sauerkraut kernel: ehci->pshadow [frame].ptr!=NULL
It's expected, and that's how it's worked for quite a while now, but it's not "right". 2.6.0-final shouldn't act that way.
That's the consequence of a particular implementation shortcut I took ages ago. To get past that you'd want me to dig up that patch I mentioned earlier -- giving EHCI a sparse tree for the interrupt schedule.
- Dave
------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
