> Thanx to the help of gregkh I've figured out that the feature reports
> I tried to generate are generating an EPIPE, which is a babble, which
> means that I'm babbeling. Which is true.
It'd be really nice if babbling were consistently EOVERFLOW,
with EPIPE reserved exclusively for stall. OHCI and EHCI do
it that way; both UHCIs seem to overload EPIPE. Stalls are
often something drivers can/should recover from; babble isn't,
so this doesn't seem like a case where overloading can be good.
Does anyone have a good reason why the UHCIs shouldn't change?
- Dave
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
http://lists.sourceforge.net/lists/listinfo/linux-usb-devel
