> > > > Not true at all. If a driver knows where a device is, it can do more > > > > things. Currently no Linux driver cares about topology, but that might > > > > change in 2.5. > > > > In part because the topology info is not really available ... :)
(As in, drivers are given "devnum" pre-digested, but not the topology info ... few do the extra work to make it available.) > static int usb_make_path(struct usb_device *dev, char *buf, int maxlen) > [deleted] > ... could be added somewhere. Looks like what the hub driver does, and discards. I'd like to see exactly one solution for that in the USB subsystem, so there aren't a variety of conventions for such names. > For USB it really should look like pci00:07.2/usb0:2.2/input0, but that's > yet to implement. > > I hope this will integrate nicely with Mochel's work. Likewise, but in that case I think the power management is going to make it show up through "driverfs" with hubs as explicit nodes in the fs tree. My current thought there is that USB through "driverfs" will likely be different from USB through "usbfs". - Dave > > I've got some hub patches pending; should I add some code > > to have the hub driver save that topology info in usb_device? > > Right now it calculates it for a diagnostic, but discards it after > > printing it. > > > > - Dave > > -- > Vojtech Pavlik _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
