On 12/19/06, Jon Smirl <[EMAIL PROTECTED]> wrote: > That's a pretty bad scheduler if it can't schedule a single 12Mb > device on a 480Mb hub. > It's only sharing the hub with a USB keyboard. The audio being sent to > it is less than 1Mb.
That's not the problem; it has trouble scheduling the bandwidth on the FS side, and it's even worse when shared with LS devices (keyboard) which are only 1mbps and incur substantial timing penalties switching back and forth from one mode to the other. A USB 2.0 hub is not a fully autonomous unit, it has to be driven, in software, by the host controller. It does not make scheduling/budgeting decisions for itself. That's the portion of the mainline ehci driver that's lacking. In any case, this is fully fixed in the mm kernels, there are unrelated integration issues to be finished before it makes it into mainline. > I will look for this. Meanwhile I plugged my audio device into a USB > port directly on the PC and it works fine. Yes, because that is skipping EHCI entirely and forcing the port to use a 1.1 companion controller (UHCI or OHCI). Your problems were occurring because of an FS device on a 2.0 hub on an EHCI controller. Monty ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
