Oliver Neukum wrote:
    * updated <linux/usb_gadget.h> ... per-frame irqs gone, status
      and feature flags allow hardware handling (as required by
      cpus like pxa250), usb suspend/resume aren't exposed, and
      "usb_request" did need to have some flag bits declared.

How does the gadget driver learn of of a stalled endpoint being cleared?
Unfortunately they don't.  Call it a hardware compromise ... not
all hardware seems to let software see such things.  And if it's
possible to write correct gadget code on such hardware, then
it's clearly not "necessary" to get such notifications.

I kind of wish it were otherwise, but on the other hand that
approach does make for simpler drivers!

- Dave





-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to