On Sun, 8 Oct 2006, Christopher "Monty" Montgomery wrote: > > No way to know until the > > > microframe is finished. The only way ehci-hcd can make an accurate report > > > in this case is to _always_ report that the slot was missed -- not even > > > _try_ to add it into the hardware schedule -- even if it might have been > > > possible for the slot to be filled. > > ...or check the uframe clock when the schedule is complete and if it > still precedes the slot... > > [or are you worried about caching and propogation of changes?]
No, I'm just pointing out that it's not always possible to tell at submission time whether the submission was made early enough. > > Actually that's a good description of the case where that -EXDEV fault > > might reasonably be reported at completion. > > Yes, agreed, if we really can't reliably figure it out ahead of time. I don't like the idea of having two separate pathways for reporting the same kind of error. If one reporting technique is reliable and another isn't, why keep the unreliable one? Alan Stern ------------------------------------------------------------------------- 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
