Hi Duncan, On Sat, 2005-01-15 at 13:37 +0100, Duncan Sands wrote: > I agree that it makes more sense to only create the ATM device when the modem > is fully > initialised.
Great. This should simplify the initialisation stuff dramatically, making the complicated interaction between usb_atm and cxacru / speedtch unnecessary. > But yes, it would > be better if the ATM layer was fully integrated into the driver model. Maybe > Chas can tell > us more about that. On a brief look I've got the impression that adding a very basic driver model support, with hotplug and device names only in /sys/class/atm, shouldn't be too hard. If ATM folks are planning the full-fledged driver model support, that'd be even better of course. > Also, I'm wondering if the driver model has any special stuff for > drivers belong to more than one subsystem (ATM, USB). Umm, I wouldn't go for it. The USB device is created upon successful enumeration by the USB subsystem; it may _provide_ an ATM device later on when and if the firmware is loaded. That's more like a "has a" relationship, rather than an "is a" one. Cheers, Roman. ------------------------------------------------------- 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
