> So, if you really want to give an interface to another driver, we need > to just unregister it and create a new one. That way it will all "just > work" properly. > > The reason I created those functions is we never completed the usb > device -> usb interface conversion fully during 2.5. Drivers should not > care at all about struct usb_device, which is not quite true today (we > still need it for initializing urbs, but that's it.) Also, with your > upcoming changes for making the interfaces individual structures, > drivers can grab a reference to the interface instead of grabbing the > reference to the device (like they do today.)
This is all sounding more and more like a filesystem: endpoints are files inside directories (interfaces) inside a device (partition). The above discussion on interfaces is analogous to the question of what happens when someone is rummaging around inside a directory when it is deleted, and maybe a new directory created of the same name. I must confess that I have a selfish reason for wanting things to go this way: it will make writing usbfs2 almost trivial! All the best, Duncan. ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
