Looking at ethtool GDRVINFO support in the USB network drivers, some in 2.4 use usb_make_path() for their bus_info field, and some use usb<busnum>:<devicenum>. Everything in 2.5 uses usb_make_path().
In 2.5, identifying devices with usb_make_path() is fairly simple; it's all exported via sysfs. Is there a similar function in 2.4 to, given a usb device, determine its usb_make_path() ID without walking the entire USB and PCI trees? Bill ------------------------------------------------------- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
