On Wed, Nov 13, 2002 at 11:29:25AM -0800, David Brownell wrote: > >>>>>>As well as updating some internal docs so they're current, > >>>>>>this patch adds the physical path to the data available > >>>>>>through hotplugging. This feature was requested at the > >>>>>>LinuxKongress hotplug BOF, and was also on my 2.5 list. > >>>>> > >>>>>And is already present with the DEVPATH environment variable, right? > >>>> > >>>>No, DEVPATH isn't as stable as the physical path. .... > > > >Ok, I'm probably confused here, what exactly is the problem that this is > >trying to solve? > > Providing physical IDs that are, in common usage, stable: "minor" > config changes don't break the IDs ... like adding and removing other > USB controllers, enabling or disabling their drivers, reboooting, > and so on.
But, as you state, even your definition of USB_PATH is not guaranteed to be stable. So, let us not start to depend on something that is "almost stable" for most people. If we go down that path, we will end up implementing two different solutions, the "easy" one, and then eventually, the "correct" one. I'd rather just implement the "correct" one now, which can be done with DEVPATH and the files located in that directory. > (*) Except for rare configurations with hardware that > most people don't have, PCI "bus numbers" won't change > except for major config changes. Like enabling ACPI or > switching to an OS that assigns them differently. > People already expect such changes to break a lot! No they don't. The kernel and userspace handles changing PCI "bus numbers" quite well right now. thanks, greg k-h ------------------------------------------------------- This sf.net email is sponsored by: Are you worried about your web server security? Click here for a FREE Thawte Apache SSL Guide and answer your Apache SSL security needs: http://www.gothawte.com/rd523.html _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
