> Why does the keyspan driver get a new device number? Surely it would > be better to keep the old one which is a) numbered properly and b) > doesn't waste a device number (yes we did try connecting > 64 keyspans > to one PC ;-)
I suspect Greg will have more to say on this topic, but I'll point out that in 2.5 usb_make_path() lets drivers see important facts like "hey, this device appeared where we put <other device> last time", from which in some cases it'd be appropriate to conclude that it's really that <other device> instead of something that's never before seen. I'm not entirely sure such conclusions are the job of the kernel, rather than userspace tools, but most devices don't yet expose those physical paths to support such logic in userspace tools. Right now (again, 2.5) I think it's just (some) network devices through ethtool, and input devices, that expose such information. - Dave ------------------------------------------------------- Sponsored by: ThinkGeek at http://www.ThinkGeek.com/ _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
