The "devpath" field in "struct usb_device" lists the physical topology, but so far there's nothing it hooks up to except diagnostics. Much like the "slot_name" field in "struct pci_dev".
It'd make sense to me that these values be exposed by drivers so that userspace names could be assigned in a more consistent manner. I'm not sure how that would work, but maybe the network interface renaming stuff would be a good model to start with. I look forward to having "driverfs" support working so those names can be exposed more consistently in userland. Even if it doesn't necessarily cover the harder problem of binding stable physical level device names (based on topology) to stable logical level device names (using naming-convention-du-jour). - Dave ----- Original Message ----- From: "Tyson D Sawyer" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, January 20, 2002 5:29 PM Subject: Re: [linux-usb-devel] 2.5 TODO list > Greg KH wrote: > > > > With the recent lists of what people are going to be wanting to do in > > the 2.5 kernel happening right now on the linux-kernel mailing list, I > > remembered that I had wanted to summarise our own thread on the same > > topic: > > http://marc.theaimsgroup.com/?t=100656721000001 > > > > So I knocked together a small 2.5 todo list, and placed it here: > > http://www.linux-usb.org/2.5_todo.html > > > Am Samstag 24 November 2001 04:00 schrieb David Brownell: > [...] > > does the new kernel build toolset kick in, for example? And I > > was rather intrigued by some of those notions of cleaning up the > > device tree for power management... some of that should fit into > > the hub work, and give us a physical device naming system that's > > "stable" unless the USB tree is recabled. (Unlike the device > > address scheme, which changes all the time.) > > Physical device naming was in the original thread (see above) but not > explicitly in the todo list. This is a pretty important feature for > embedded apps, esp. those that can be reconfigured. Among other things, > we use USB serial chips (FTDI) for a couple of projects. Not having a > consistent ttyS to connect to is a problem. For now we are ignoring the > problem. Eventually I will have to do some sort of a hack with devfs > (or something like that) so that each node has a consistant name. > > Cheers! > Ty > > -- > Tyson D Sawyer iRobot Corporation > Senior Systems Engineer Military Systems Division > [EMAIL PROTECTED] Robots for the Real World > 603-532-6900 ext 206 http://www.irobot.com > > _______________________________________________ > [EMAIL PROTECTED] > To unsubscribe, use the last form field at: > https://lists.sourceforge.net/lists/listinfo/linux-usb-devel _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
