G;day all, Having finished off my paper (available RSN :), I started to work on the CDCEther and kaweth drivers again.
A common issue for them is the availablility of a version of usb_control_msg that is asynchronous (or at least, can be called in interrupt context). I know I could allocate a devrequest (or I could, until recently), and a control urb, and assign fields, and then usb_submit_urb(), and have a nothing completion routine, but it all seems like too much hassle to do a lot of times. Especially for most of the calls, where they are only OUT, and have either no or small data phase. catc.c has an interesting model that basically queues messages. Maybe something along those lines could be added to the usb core code as either a macro or a helper routine. The semantics I'm looking for are basically the same as usb_control_msg(), where the requests to each device are delivered in order (except for the maybe for a failure case, which needs some more though), but no waiting for a completion routine, and available to be called at any time. I think I could probably come up with something that mostly works, but I'd probably miss a whole stack of key locking issues, so it would probably be better done by someone who knows this stuff. I am about to disappear into no-net land for about two weeks (for a real holiday :), so if anyone feels the need to code something like that, I'll look forward to seeing it (and the other 1e3 emails that will probably be waiting) when I get back. _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
