On Wed, Jul 23, 2003 at 01:58:36PM +0200, Joerg Pommnitz wrote: > --- Greg KH <[EMAIL PROTECTED]> schrieb: > > > > But if you want to patch the acm driver, you might want to do something > > like what the usb-serial core does in creating the > > /proc/tty/driver/usbserial file to show which device is attached to > > which USB device. That might solve your problem. > > > > Hope this helps, > > > > greg k-h > > Hi Greg, > thanks for your advice. I'll take a look at this. > > Please bear with me while I ask a few more questions: > > Commonly one refers to USB devices in the BUS:DEVICE scheme. My > understanding is, that a bus is equivalent to a host controller. Correct?
Yes. > If so, this is a real physical entity that wont change without somebody > modifying the hardware. > > The device number seems to be less predictable. My understanding is, that > this number refers to the device address assigned during enumeration. Is > this correct? If so, is there a way to trace this back to one particular > physical USB port either on the host controller or a hub? Take a look at the usb-serial way of doing this. It exports the physical tree location of the device, which is what it is sounding like you are looking for. Hope this helps, greg k-h ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
