Greg KH wrote: > On Wed, Jul 24, 2002 at 01:55:58PM -0700, David Brownell wrote: > >>... it'd be better if it included usb_bus->bus_name too, as done >>in usb_make_path(), since two different busses can easily have >>similar hub trees. "%s-%s:%d" then, since this format string >>can't use "/" like hid-core (effectively "%s-%s/input%d"). > > > Doesn't dev->devpath have the bus id? Looks that way to me on my > machines...
Not unless someone changed it. usb_bus->bus_name ... "00:0b.2" (usually a PCI slot_name) usb_dev->devpath ... "4.3" (port 3 of the hub on roothub port 4) Certainly usb_make_path() catenates the two values, as does a bunch of other code. - Dave ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
