On Fri, 2005-04-29 at 22:16 +0200, Oliver Neukum wrote: > Am Freitag, 29. April 2005 22:01 schrieb Greg KH: > > > > I'd rather just guarantee that the sysfs device were fully > > > > constructed (attributes and all) before the driver binding and > > > > hotplug stages of enumeration started. That's been a problem > > > > all along, and that's what those recent changes were supposed > > > > to be addressing. > > > > > > Even if you can make sure they had been set up before the script > > > started, how do you make sure they are still around? > > > > You can't guarantee that they will not have been removed, but by at > > least saying that "the attributes will be created before you will be > > called", you let userspace go a lot faster :) > > That is true, but it doesn't explain what a layer of indirection will buy > you. If you have all the data ready by the time you send a message, > you might as well send a message that includes all data available. >
But it's already in sysfs since that information is needed for coldplug scenarios. By extension, the hotplug environment should be minimal and only contain ACTION, DEVPATH, PHYSDEVPATH etc. David ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. Get your fingers limbered up and give it your best shot. 4 great events, 4 opportunities to win big! Highest score wins.NEC IT Guy Games. Play to win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20 _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
