On Sun, 21 Jan 2007, David Brownell wrote: > But that does raise the question of what to do with state management. > There are at least two types of state management on the host side: > > * Config change (SET_CONFIGURATION, SET_INTERFACE) ... which should > maybe not be permitted using the generic control endpoint support; > > * Connect, disconnect, reset, suspend, resume, wakeup ... which > I'm grouping together here more out of laziness than correctness, > since it's possible they each need distinct approaches. And at > least some of those kinds of state management might be best as > event notifications to the driver. > > Also, as I noted separately, I suspect that endpoint halt management > might likewise be best handled outside of a generic "control endpoint" > mechanism (as with config changes).
Another thing to consider is access management. With usbfs, users are not allowed to access endpoints belonging to an interface that is already bound to some other driver. Nor are they allowed to send control messages whose recipients are such endpoints or such interfaces. Alan Stern ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
