One new question, hopefully this one is just rote arcana to one of you....
The current scheduler strategy always tries to place a given periodic request (be it iso or intr) into the same uFrame slot in all scheduled HFrames. Is this a requirement of the spec (I don't recall seeing such a restriction) or merely convenient to the current code? In some ways it's easier to just stack requests into the full-speed frame and then plop the splits into whatever uFrame that happens to work out to, even if that means that, eg, an interval 1 iso request might be serviced in substantially different portions of the actual full-speed frame. Perhaps the latest iteration of rereading the specs again will yield yet another new layer of understanding ;-) The corner cases are looking less and less scary with each pass; the logic all feels intuitive at this point. Monty ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642 _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
