On Thu, Sep 26, 2002 at 09:14:48AM -0700, David Brownell wrote: > > >Yes, Pat and I have talked a lot about the need for a driver "state". I > >think the current goal was to see how far we can get without needing it. > >I was certainly cursing the lack of it today when trying to debug this > >problem, but in the end, having it would have only masked over the > >real problem that was there. > > It'd actually be a "device state", not a "driver state" ...
Doh, yes, that's what I meant, sorry. > >Well, that's a driver unload issue, which I think everyone agrees on the > >fact that it's not ok to do automatic driver unload when a device is > >removed, because of this very problem. > > I think it _could_ be fine to do such rmmods, if all the module > remove races were removed ... and (for this issue) if the primitve > were actually "remove if the driver is not (a) in active use, or > (b) bound to any device". Today we have races and (a) ... but it's > the lack of (b) that prevents hotplug from even trying to rmmod, > on the optimistic assumption there are no races. But how do we accomplish (b) for devices that we can't remove from the system? Like 99.9% of the pci systems? I agree it would be "nice", but probably never realistic :) thanks, greg k-h ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
