On 10/9/06, Alan Stern <[EMAIL PROTECTED]> wrote: > > Don't much like that one. Requires HCDs to record history that would > > otherwise not be needed, and interrogate it. > > I don't like it either; even less than #1. However Monty seemed to > mention it, so I brought it up for discussion.
If it turned out to be the right answer to making things consistent and easy for higher level drivers, I don't care if it caused alot more work in the low level driver. But mostly it was just a suggestion to consider. > Auditing isn't enough; the drivers have to be fixed up to handle these > faults in a reasonable way. Unless ignoring them _is_ reasonable -- in > which case why bother to report them? Not reasonable, just not a regression. > The issue then becomes, what if all the slots in the URB have been missed > (or might be missed, since the HCD can't tell in cases where there's a > close call)? Okay, I admit, in this situation it makes sense to reject > the submission entirely. Maybe also set urb->start_frame to the next > available slot. Essentially what MacOS does. Not exactly, but close to it. Despite originally suggesting it, I'm not convinced #1 is a great idea unless it could be made a reliable single-source for XRUN information. Like Alan, I'd rather have one way of getting the data unless only one way represents a substantial compromise in what informational data can make it back to the higher level drivers. Reporting at completion eliminates timliness of the report, but that seems to be the only problem. (Here's one reason why I'd like to know where and how big the xrun is: if an xrun happens, I'm going to have to fix up the data by hand in an app. Having bracketing information reported/recorded by the app would be invaluable in saving time when doing so. Often, you can't afford to just throw lightly flawed data away and try again. You have to recover and make do with what you got. If that means a full-time week of piecing it back together by hand, so be it.) 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 _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
