On Fri, 8 May 2009, Sarah Sharp wrote: > > A better way to do this would be to add a new core routine for setting > > an endpoint's interval. This routine would be callable only in process > > context and only while there are no URBs queued for the endpoint. The > > new value could be stored in the usb_host_endpoint structure instead of > > messing up the descriptor. Then urb->interval could safely become an > > output-only field. This would apply to Isochronous as well as to > > Interrupt endpoints. > > This sounds reasonable. Should submit URB fail if the interval > specified by the driver in the URB doesn't match the interval in the > usb_host_endpoint structure? It would allow users to quickly catch any > drivers that are missed by the conversion, but it's kind of mean to > break user's devices. It would be better just to print a warning in the system log. Give things a few kernel releases to settle down, and then change all the HCDs to look only at the new field. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
