In message <[EMAIL PROTECTED]>,Duncan Sands writes : >In the short term we can work around using a clever USB hotplug script. But y >es, it would >be better if the ATM layer was fully integrated into the driver model. Maybe >Chas can tell >us more about that. Also, I'm wondering if the driver model has any special s >tuff for >drivers belong to more than one subsystem (ATM, USB).
the plan is to eventually do away with struct atmdev in favor of struct netdevice. this would handle the /sys problem. in the short term, we could probably try something else. ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
