David Brownell ([EMAIL PROTECTED]) said: > Bill Nottingham wrote: > > 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(). > > It'd be worth IMO making all 2.4 drivers use usb_make_path(), > since those IDs are stable.
Maybe, but in 2.4 they're not really useful from userspace, without a lot of legwork, AFAICT. > > 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? > > Actually, I'd say the usb_make_path() physical IDs are not really > available through sysfs. I distinctly recall them being in sysfs *somewhere*; since I'm not booted into 2.5 at the moment, I don't remember the exact location. > How exactly would you be "given a USB device"? Given: - set of USB network interfaces eth0-eth10 - set of ten USB network devices in /proc/bus/usb Cross reference them. This requires using what's returned by GDRVINFO, and if they're all using usb_make_path() in 2.4, this appears to be pretty messy. Bill ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
