On Fri, May 8, 2009 at 00:47, Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> wrote: >> Or is that a specific requirement where things would go wrong when the >> kernel binds to a device first? > > You've got it. Sometimes devices are in a very precarious state (such > as during a firmware update) and they need to go into a particular > configuration. Letting the kernel install some random configuration at > such times doesn't work. I see. You mentioned earlier, that you would need to match the holder of the "lock" and the one that accesses the device? Wouldn't it be sufficient already, if you can take a "lock" at the specific port, that prevents the kernel to access the device when it shows up? You thought of supporting a number of different users, with different uids, or would that be a root-only action? Thanks, Kay -- 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
