> > Now I know this overloads the existing DEVICE usage for USB devices, but
> > I think we can determine what do properly (basically just test for
> > DEVFS, and if it's not set, then we are looking at the driverfs entry
> > for the device.)
>
> I'd rather see these changes:
>
> - This new parameter to every (!!) hotplug event gets renamed to
> KFS_DEVICE (assuming that's the new driverfs name).
What about DEVPATH, since that's what it is, right?
> By the way, what's the cost of a driverfs attribute on a 'struct device'?
> Each USB device now has over a dozen of them.
32 bytes/attribute + size of the function. But, attributes are reused
across devices, so the total data cost is 32 x ~16 = 512.
-pat
-------------------------------------------------------
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
