Am Dienstag, 5. Mai 2009 17:56:04 schrieb Pantelis Koukousoulas: > > Either way, it seems clear that we need a way to give programs full > > control over specific devices. And we need a way to do it before the > > device is plugged in, which does seem to imply that the program should > > specify a particular port rather than a particular device. > > Well, the fact that this is clear for at least the 3 of us (you, Greg and > me) and perhaps Oliver too is a very good start. It means we can move > beyond the overview now :) This is not quite so simple. If you hand over a port, you cause problems. That doesn't mean you shouldn't do it, but you have to solve the problems. Immediately I can think of: - overcurrent events - the power budget - how to reset a hub - how to suspend/resume a hub - how to react to the hub whose port you've claimed being unplugged Note that these problems (except for the power budget) must be handled in kernel space or we can deadlock due to the storage driver. Thus you must write a real "device level" usb driver and implement the necessary methods. Or possibly even several "device level" drivers. Regards Oliver -- 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
