- 1..N TDs ... dependant on the specific buffer passed later,
   except (usually) for ISO (where i == n)
What prevents you from allocating a reasonable number in the general case
and as many as you may need in the iso case?
What, and have _two_ code paths to debug/stabilize in the
hairy hardware-specific logic ... one where you guessed
right, and one where you guessed wrong?


It's a case of memory vs. speed and should be benchmarked, probably.
And stability too. Do you have the statistics Greg was asking
about, which would show there's even a problem here?



-------------------------------------------------------
This SF.NET email is sponsored by: A Thawte Code Signing Certificate is essential in establishing user confidence by providing assurance of authenticity and code integrity. Download our Free Code Signing guide:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0028en
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to