--- 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?
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?
Thanks in advance
Joerg
=====
--
Regards
Joerg
__________________________________________________________________
Gesendet von Yahoo! Mail - http://mail.yahoo.de
Logos und Klingelt�ne f�rs Handy bei http://sms.yahoo.de
-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
same time. Free trial click here: http://www.vmware.com/wl/offer/345/0
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users
