On Friday 29 April 2005 11:23 am, Roman Kagan wrote:
> 
> ... instead of trying to make sure the attributes are available via
> sysfs at hotplug time, we can use another means to pass them to hotplug:
> we can add a routine, which, when called from the .hotplug function
> and given pointers to struct attribute and struct device, would add
> environment variable
> 
> SYSFS_attrName=attrValue

Color me amused.  That was the original way to pass information
to hotplug agents ... back then (2.4.0.test10 or so), there was
usually no other way to export the relevant data.

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.

- Dave


-------------------------------------------------------
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

Reply via email to