On Wed, 6 May 2009, Oliver Neukum wrote: > If you just want to support exotic modes of configuration, that's > enough. If you really want to operate the device (or devices, what happens > if you plug in a hub?) you'll need fuller support. It seems to that if you > wish to use this for the purpose of virtualisation, you need fuller support. Clearly we aren't going to virtualize hubs. The amount of effort required would be ridiculously large. (In fact, programs can claim a hub's interface even today. They can't do much with it, since usbfs offers no way to register or unregister USB devices.) However we ought to add reset_resume, pre_reset, and post_reset methods to usbfs_driver. Even if they don't do anything -- after all, there's no way to inform a user program that its device has been reset or suspended. Resets shouldn't be a problem, though, since the only entity capable of resetting a device that is owned by some program is the program itself. 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
