Hello David, > API CHANGE #1: Let INTR completion handlers change > the transfer_buffer_length. A value of "-1" (it's not > a size_t!!) would mean "don't transfer anything". Any > other value, up to the maximum allowed by the endpoint > descriptor (which is what would control the bandwidth > allocation by the HCD), would be legal. > > Today, this would mostly be used for INTR-OUT (or > host-writes-to-device). For a device side API it > would be used regularly on INTR-IN transfers (or > device-writes-to-host). > > This could either be done (a) with a special API > function, like > > usb_modify_transfer (struct urb *urb, int size) > > or (b) by just modifying the HCDs to use the current > transfer_buffer_length when re-enabling the transfer > after a completion callback finished. > > I'd prefer (a)
I would prefer a) too. Because 1) it will give freedom for the implementation of changing sizes 2) it is not "hidden", but explicit. best regards Wolfgang _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
