On Thu, 15 Jan 2004, David Brownell wrote:
All drivers that unblock endpoints would be by definition buggy. That API should be purely internal to usbcore anyway; that's what it is today (effectively), since drivers aren't allowed to change the endpoint maxpacket sizes.
I disagree. A driver might want to block an endpoint as an easy way to prevent automatic resubmissions, say in a release() routine.
That is, when for example a file is closed the driver needs to shut down in some of the same ways as when the device is unplugged.
That might make sense; I'd have to think about it more. I'm used to thinking that level blocking should be done inside the device driver.
But having both usbcore and the device driver use that same mechanism means they could collide with each other, so that a single bit wouldn't always work right. Once usbcore blocks an endpoint, a driver should _not_ be allowed to unblock it. Plus, I still don't think device drivers should ever change endpoint maxpacket sizes!!
- Dave
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
